Mail API
Mail API is a vendor-neutral API specification for sending and receiving email. It defines an HTTP boundary so applications are not tied directly to a mail provider.
The current outbound endpoint is:
POST /v1/messagesConcepts
Section titled “Concepts”- Scope and capabilities — what
v1supports, deliberately omits, or reserves for a future capability. - Authentication — the bearer token a request carries.
- Submission responses — every status code and its retry guidance.
- Idempotency — how
Idempotency-Keymakes a retry safe. - Versioning policy — what may change without a new major version.
- Design rationale — why the contract is shaped this way.
Examples
Section titled “Examples”Implementations
Section titled “Implementations”Crosswalks
Section titled “Crosswalks”Email provider APIs
Section titled “Email provider APIs”Standards
Section titled “Standards”The caller-side crosswalks are grouped by the layer an adapter attaches to, from the language upward.
Languages
Section titled “Languages”Mail facilities that ship with the language, with no added dependency.
Libraries
Section titled “Libraries”Framework-agnostic libraries added as a dependency to compose or send mail.
Frameworks
Section titled “Frameworks”Application frameworks that own mail configuration and expose a swappable transport or sender.
Applications
Section titled “Applications”Deployed products with a mail hook an extension can replace.
