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": "[email protected]",
    "to": "[email protected]",
    "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: '[email protected]',
  to: '[email protected]',
  subject: 'Hello',
  html: '<p>It works.</p>',
})

Migration checklist

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

Sandbox vs production

Sandbox: send from [email protected] to your account email only while integrating
Free production: verified domain and a payment method on file (no charge until you upgrade) — 3,000 emails/mo · 100/day · 1 domain on the shared transactional network (Pool)
Pro (from $20/mo): from 50,000 emails/mo · up to 10 domains · declining overage by tier
Scale: higher 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 can move to SuperSend TX SMTP relay: host smtp.supersendtx.com, port 587 (STARTTLS), username supersendtx, password from a dashboard SMTP credential (stxsmtp_…). Same verified domains, plan limits, and suppressions as the HTTP API. Prefer POST /emails for new app code; use SMTP when the integration only exposes an SMTP form. Details: SMTP.