Transactional email API

Transactional email that can prove what happened.

Send password resets, receipts, invites and product notifications through an API that commits before it returns 202, retries idempotently, and reports the remote MX response instead of a vague “sent.”

The contract

A 202 should mean committed, not queued.

Transmitly writes the message, one delivery row per recipient, the idempotency key, usage accounting and the outbox event in one Postgres transaction. Only after that commit does the API return 202.

  • Idempotent retries with 409 on conflicting bodies.
  • Per-recipient state: queued, sending, delivered, deferred, bounced, complained, suppressed.
  • Durable retries across deploys and worker restarts.
  • Signed webhooks with replay and dead-letter tooling.
  • SMTP code, enhanced code and MX host recorded for every attempt.
POST /v1/emails
curl https://transmitly.io/v1/emails \
  -H "Authorization: Bearer $TRANSMITLY_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: reset-8f2c" \
  -d '{
    "from": "Acme <[email protected]>",
    "to": ["[email protected]"],
    "subject": "Reset your password",
    "html": "<p>Use the link below.</p>",
    "stream": "transactional",
    "tags": { "flow": "password_reset" }
  }'

# 202 Accepted after the transaction commits
{ "id": "msg_2f9c…", "status": "accepted" }

Built for production

The details that matter at 2am.

Durable acceptance

One transaction commits message, deliveries, idempotency and event.

Honest semantics

Accepted, delivered to MX and inbox placement are never conflated.

Stream isolation

Marketing traffic cannot consume transactional capacity.

Provider awareness

Per-provider budgets, pause controls and deferral pressure.

Questions

Transactional API FAQ

+What makes a transactional email API different from an SMTP relay?

A transactional email API gives you structured acceptance, idempotency, per-recipient delivery state, retries and event webhooks. An SMTP relay only accepts a message for relay. Transmitly exposes both the API path and an owned SMTP path, with the same durable delivery records.

+Does 202 Accepted mean the email was delivered?

No. 202 means Transmitly committed the message, its recipient deliveries, idempotency key and outbox event to durable storage. Delivery to MX is reported separately when a remote mail exchanger returns a 2xx response. Inbox placement is never inferred from SMTP.

+Is the API idempotent?

Yes. Send an Idempotency-Key with each request. A retry with the same key and body returns the original message ID; the same key with a different body returns a conflict.

+Can I keep marketing and transactional email separate?

Yes. Transactional and marketing streams have separate pools, budgets, priorities and blast-radius boundaries so a marketing surge cannot consume product-mail capacity.

+Do you support webhooks for delivery events?

Yes. Events are signed with HMAC-SHA256 over the timestamp and raw body, retried with backoff, dead-lettered, scoped per domain and replayable.

Want the deeper explanation? Read what 202 Accepted actually means.

Send your first transactional message.

Verify a domain, create a send-scoped key, and see the actual MX response. Start free and upgrade when you need more.