Inbound (inbound.new)
Email-to-webhook with TypeScript-first DX.
Inbound converts any address into a webhook endpoint with structured JSON, automatic retries, and exponential backoff. Webhook delivery typically under 2 seconds. TypeScript types for the payload.
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, Inbound (inbound.new) covers idempotency keys, webhook coverage, event stream, and SDK breadth, and does not cover the suppressions API and batch sending. Whether that gap matters depends on how central those are to the build.
- Idempotency keys: Yes
- 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: node
- Deliverability: Not applicable; receive-only.
Not applicable; receive-only.
Modern stacks that need email-to-webhook with TypeScript.
- › Typed payloads
- › Fast delivery
- › Good free tier
- › Newer entrant
- › Node-only SDK
Features at a glance
| API | Yes |
| SMTP | No |
| SDKs | node |
| 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 | Yes |
| Dedicated IP | No |