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.

TypeScript and Node.js

4 picks

Most providers ship a first-class Node.js SDK. The decision usually comes down to type quality, edge-runtime compatibility, and idempotency exposure.

Python

4 picks

Python coverage is broad, but quality varies. Async support is the most common gap.

Go

4 picks

Go is a strong story for transactional email at scale. Most major providers ship official packages with idiomatic interfaces.

Ruby

4 picks

Ruby support is concentrated around the established providers. Rails integrations through Action Mailer are the dominant pattern.

PHP

4 picks

PHP support is dominated by Laravel-friendly SDKs. Symfony Mailer transports are the second pattern.

Rust

2 picks

Rust coverage is sparse. Resend ships an official crate; everyone else expects raw HTTP via reqwest.

Java and JVM

3 picks

Enterprise-friendly. Most major providers ship Java SDKs; Spring and Micronaut integrations vary.

Elixir

3 picks

The Phoenix ecosystem leans on Swoosh adapters. Native SDKs are less common.

.NET and C#

3 picks

The major providers ship NuGet packages. Choice often comes down to existing Azure or AWS commitments.

CLI tooling

2 picks

A growing number of providers ship a CLI for local sending, tail-style log inspection, and template management.

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

reading this as SaaS product teams

A SaaS product sends on behalf of its customers, so the deciding factors are tenant isolation, whether suppressions can be scoped rather than global, and whether support can answer why one specific account did not receive one specific email. Lifecycle automation and transactional sending usually need to coexist.

Applied to email API SDKs, that means weighing multi-tenant support, event stream, the suppressions API, and operating track record ahead of the rest, against trial expiry notices, dunning, onboarding sequences, and per-tenant transactional mail.