$/transactional-email-api providers ↗
hub · sdks

Email SDKs, by language.

Most email decisions come down to which SDK fits the language and runtime. This hub catalogs the SDK story per language, with editorial picks tied to the shared provider database. Type quality, edge-runtime support, idempotency-key exposure, and runtime ergonomics are the lenses that matter.

Looking for a framework integration instead? See the frameworks hub.

reading this as teams choosing a transactional API

Judged purely as an API. What the request contract guarantees on retry, how complete the webhook event coverage is, whether suppressions are readable and writable programmatically, and how much the message log retains when something needs debugging in production.

Applied to email API SDKs, that means weighing idempotency keys, webhook coverage, event stream, and operating track record ahead of the rest, against high-frequency programmatic sends where a missed delivery is a product failure.