
Processing bounce and complaint webhooks end to end
Turn bounce and complaint events into suppressions, user-facing flags and alerts. A worked pipeline from webhook receipt to updated account state.
5 min read
Blog · Email API · page 4 of 5
Transactional email engineering: sending APIs, SMTP relays, webhooks, retries, idempotency, templates and testing.

Turn bounce and complaint events into suppressions, user-facing flags and alerts. A worked pipeline from webhook receipt to updated account state.
5 min read

SaaS platforms that send as their customers need domain verification, per-tenant DKIM and isolated reputation. The architecture and the onboarding flow.
5 min read

Sending email inside a web request couples your latency to someone else's SMTP server. A queue-based design with workers, retries and dead letters.
4 min read

Decisions that make an email-sending API pleasant for years: async acceptance, idempotency, explicit errors, stable fields and a clean event model.
4 min read

Trace a message from API call to SMTP response. What to log, which metrics to emit and how to correlate IDs so 'did it send?' takes seconds.
4 min read

A 5xx is not always permanent and a 4xx is not always harmless. Build bounce classification on reply codes and enhanced status codes, with exceptions.
4 min read

Gmail, Outlook and Yahoo each defer differently when you send too fast. Build per-destination queues and adaptive concurrency that respond to 4xx replies.
4 min read

The text/plain alternative helps accessibility, privacy-minded readers, smartwatches and some filters. How to generate a good one rather than a strip.
5 min read

Email clients support a narrow, quirky slice of HTML and CSS. The constraints that matter for receipts and alerts, and a structure that survives them.
4 min read

Mailbox providers report spam complaints as ARF messages. Parse them, map them back to the recipient and suppress automatically within minutes.
4 min read

Keep templates in the repo, review them like code, render them in tests and roll changes out safely so a typo never reaches a million inboxes.
4 min read

A client retry after a timeout should never email a customer twice. How idempotency keys work, the race people miss and how to pick key values.
4 min read