Migration from Amazon SES

If you send transactional mail through Amazon SES (SDK, SMTP, or a thin API on top of SES), you can move the application-facing send path to SuperSend TX while keeping the same jobs: auth mail, receipts, alerts, and notifications.


What changes

SES-oriented setup SuperSend TX
AWS credentials / IAM stx_... API key
Regional SES endpoint https://api.supersendtx.com
SendEmail / SendRawEmail POST /emails
SES-verified identity SuperSend TX verified domain
Configuration sets / event destinations Webhooks + dashboard activity
Shared SES IP pools (typical) Pool (owned transactional network) or Dedicated (managed servers + IPs)

SuperSend TX runs on owned mail infrastructure, not as a reseller of SES. That matters when you care who else shares the pipe — and when you later need Dedicated isolation.


Minimal send

curl -X POST https://api.supersendtx.com/emails \
  -H "Authorization: Bearer $SUPERSENDTX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "you@yourdomain.com",
    "to": "user@example.com",
    "subject": "Hello",
    "html": "<p>It works.</p>"
  }'
import { SuperSendTX } from 'supersendtx'

const client = new SuperSendTX(process.env.SUPERSENDTX_API_KEY)
await client.emails.send({
  from: 'you@yourdomain.com',
  to: 'user@example.com',
  subject: 'Hello',
  html: '<p>It works.</p>',
})

Migration checklist

  1. Sign up at app.supersendtx.com and create an API key
  2. Verify your sending domain (Domains) — SPF, DKIM, return path
  3. Replace SES SDK calls with SuperSend TX HTTP or the supersendtx npm package
  4. Map bodies: HTML → html, text → text, reply addresses → reply_to
  5. Point bounce/complaint/delivery handling at SuperSend TX webhooks
  6. Run parallel canary sends, then shift production traffic

Sandbox vs production

  • Sandbox: send from noreply@mail.supersendtx.com to your account email only while integrating
  • Pro (from $20/mo): production on the shared transactional network (10 domains)
  • Scale: volume tiers with declining overage (up to 1,000 domains)
  • Dedicated (from $299/mo): managed server and IPs when you need isolation

See Pricing and Quickstart.


SMTP

SES SMTP users: SuperSend TX does not currently issue account-scoped SMTP credentials. Prefer the HTTP API. Status: SMTP.