SMTP relay status

SuperSend TX is optimized around the HTTP API:

• POST /emails
• webhook callbacks
• dashboard activity and deliverability views

That gives the safest account scoping today because the API key model is already implemented end to end.

Current state

SuperSend TX does not currently issue account-scoped SMTP credentials from the product.

If you are migrating a legacy app that still expects SMTP:

• prefer switching it to the HTTP API where possible
• treat SMTP as unavailable until SuperSend TX ships account-scoped SMTP credentials

Recommended path

For new integrations, use:

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>Hi</p>"}'

This preserves:

• account scoping
• domain verification checks
• sandbox self-test flow
• deliverability/activity tracking in the dashboard

Future-friendly credential shape

If/when SuperSend TX adds SMTP, the expected customer-facing shape should look more like:

• host: shared SuperSend TX SMTP hostname
• username: account-scoped identity
• password: revocable secret managed in the dashboard
• from-domain checks: same rules as the HTTP API

Until then, there is no supported /smtp credentials endpoint.