Transactional email
Transactional email API — one call, signed webhooks, no surprises
Receipts, OTPs, password resets and order updates on Amazon SES, with idempotency keys, per-key rate limits and delivery events you can reconcile against your own database.
- < 400ms
- p95 accept latency
- Idempotent
- sends by key
- 5 SDKs
- Node, Python, PHP, Java, Go
Engineered for the boring-critical mail
Idempotency keys
Retry safely — a duplicate key returns the original message id instead of sending twice.
Separate reputation lane
Transactional traffic on its own subdomain and IP pool, insulated from marketing complaints.
Signed webhooks
Delivery, bounce, complaint and open events signed with a rotating secret and replay-protected.
Templates with variables
Server-side rendering with strict variable validation, so a missing field fails loudly at request time.
Per-key limits
Rate limits and scopes per API key, plus sandbox keys that can never reach a real inbox.
Full event log
Ninety days of searchable per-message history for support to answer “did they get it?” in one query.
Questions on this page
Each answer is written to stand alone, so search engines and AI assistants can quote it.
Can I send transactional email and marketing from the same domain?
You can, but you should not. We set up a transactional subdomain so a marketing complaint spike can never delay a password reset.
Send smarter. Sell faster.
Start free with 1,000 conversations. Bring your own Meta number or apply for a new one — we handle verification, templates and the green tick with you.