SuperSend TXDocs

SuperSend TX + Base44

Base44 apps can send email through built-in platform features. Use SuperSend TX when you need your own domain, higher control over deliverability, or the same transactional stack as the rest of your product.

When Base44 built-in email is enough

  • Early prototypes and internal tools
  • Low volume without a custom domain requirement
  • Flows where Base44’s default sender is acceptable

When to add SuperSend TX

  • Branded mail from @yourdomain.com after DNS verify
  • Password reset / auth mail you want on owned transactional infrastructure
  • Webhooks and delivery visibility via SuperSend TX dashboard
  • Consistent API across non-Base44 services (same POST /emails everywhere)

1. Add your API key

  1. Create stx_… at app.supersendtx.com.
  2. In Base44, add a project secret or environment variable (exact UI varies by Base44 project type):
SUPERSENDTX_API_KEY=stx_your_key_here

Wire server-side code or automation steps to read that variable — never expose it in client-visible config.

2. Paste this prompt in Base44

Add SuperSend TX for transactional email in this Base44 app (instead of or alongside built-in email).

Docs:
- https://docs.supersendtx.com/ai/agent-skill
- https://docs.supersendtx.com/openapi.yaml
- https://docs.supersendtx.com/builders/base44

Rules:
1. Use SUPERSENDTX_API_KEY from project secrets — server-side only.
2. POST https://api.supersendtx.com/emails with Bearer auth for transactional sends (reset, verify, receipts).
3. Sandbox until domain verify: from "noreply@mail.supersendtx.com", to SuperSend TX account email only.
4. Explain when built-in Base44 email is still fine vs when SuperSend TX is required (custom domain, production volume).
5. Use html/text; verify domain in SuperSend TX before production from addresses.

Link users to https://app.supersendtx.com for domain setup.

3. HTTP send

POST https://api.supersendtx.com/emails
Authorization: Bearer stx_…
Content-Type: application/json

{
  "from": "noreply@yourdomain.com",
  "to": "user@example.com",
  "subject": "Your receipt",
  "html": "<p>Thanks for your order.</p>"
}

Production checklist

  • Domain added and verified in SuperSend TX
  • from uses verified domain
  • API key only in secrets, not in frontend
  • Bounce/complaint handling via webhooks if needed