$/transactional-email-api providers ↗
← all providers
Inbound

CloudMailin

Long-running inbound email to HTTP service.

overview

CloudMailin has been doing inbound email to HTTP since 2010. Reliable, no-frills, JSON or raw MIME delivery.

for 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.

Against high-frequency programmatic sends where a missed delivery is a product failure, CloudMailin covers webhook coverage and event stream, and does not cover idempotency keys, the suppressions API, batch sending, and SDK breadth. Whether that gap matters depends on how central those are to the build.

  • Idempotency keys: No
  • Webhooks: Yes
  • Event stream: Yes
  • Operating since: Not published
  • Suppressions API: No
  • Best published rate per 1,000: Tiers not published in comparable form
  • Batch sending: No
  • SDKs: None
  • Deliverability: Not applicable.
deliverability

Not applicable.

best for

Established workloads that depend on a long-running provider.

pros
  • Mature product
  • Multiple payload formats
cons
  • No free tier
  • Older UI

Features at a glance

API Yes
SMTP No
SDKs None
Webhooks Yes
Templates none
React Email No
Batch send No
Scheduled send No
Suppressions No
Multi-tenant Yes
Inbound parsing Yes
Event stream Yes
Idempotency keys No
Dedicated IP No

Appears in rankings