The best inbound email APIs, ranked by application shape.

How this inbound shortlist was evaluated

Each option must document a production-shaped way to receive email programmatically. The review then asks what the service returns, how domains and addresses are configured, how attachments are handled, whether events retry, where data is stored, what state the customer must build, and who operates the runtime.

The list avoids ranking by advertised deliverability because inbound and outbound behavior differ and independent comparable evidence is not available here. It also avoids static price comparisons. Provider plans, limits, regions, and beta features can change, so the official source links and verification date are part of the decision record.

Postmark, Mailgun, Resend, and SendGrid reduce transport work

A managed parse or route product turns SMTP-facing complexity into an HTTP-facing event. This is a good boundary when the application already has users, cases, conversations, authorization, storage, and queues. The provider handles receiving infrastructure, while the application validates and processes the resulting payload.

The differences appear in routing flexibility, payload shape, domain configuration, integration with sending, account model, retries, attachment behavior, and operational support. Test the exact message variants your product receives. Forwarded mail, multiple recipients, nested MIME, large attachments, and provider-specific headers can expose assumptions that a basic text message does not.

• Use a unique event identifier or payload hash for idempotency.
• Acknowledge quickly and process heavy work asynchronously.
• Keep raw payload access restricted and retention explicit.
• Treat validly transported content as untrusted input.

Amazon SES gives AWS teams components rather than a mailbox product

SES receiving is regional and rule-driven. Receipt rules can place messages in S3, publish to SNS, invoke Lambda, or integrate with WorkMail according to current AWS documentation. That composability is useful when the surrounding application already lives in AWS and the team wants infrastructure-level control.

The cost is assembly. The team owns the data model, retries across services, parser behavior, search, thread reconstruction, tenant authorization, secrets, observability, retention, and agent tool contract. For a platform team, that may be appropriate. For a small product team seeking an inbox API, it may delay the product workflow.

mails0 continues after parsing into identity and task operations

mails0 is useful when multiple callers need a consistent mailbox contract rather than a provider-specific event. It stores messages under an identity, exposes scoped credentials, reconstructs threads, supports search and labels, returns verification codes, and offers query and event interfaces for applications and agents.

That abstraction can reduce repeated application work, but self-hosting does not eliminate operations. Cloudflare routing, Worker deployment, D1 migrations, R2 retention, limits, secrets, sender integration, and abuse response become the operator's responsibility. Start with the hosted receive-only path if the team first needs to validate product fit.

Run a payload and failure bake-off before changing DNS

Replay representative synthetic messages through each candidate: plain text, HTML, multiple recipients, reply headers, forwarded content, Unicode subject, large body, several attachments, and malformed MIME. Compare parsed fields, files, timestamps, event ordering, retries, and final application state.

Then test an unavailable destination, slow acknowledgement, duplicate event, invalid signature or source, storage failure, and a message that violates content policy. DNS cutovers can be difficult to reverse quickly, so keep a rollback route and verify each layer before declaring migration complete.

Sources and product scope

Product behavior is verified against the mails0 source and documentation. External comparisons link to official vendor documentation checked on 2026-08-15.

Related implementation paths