inbound
inbound.new
- Web
- API
What inbound is
Inbound is a web and API service that parses received email for developer workflows. It converts messages into JSON containing addresses, headers, text and HTML bodies, raw MIME, thread details, and attachment metadata with download links. Parsed mail can be delivered to webhook endpoints, with failed deliveries retryable through the dashboard or API. Thread identifiers and reply headers help responses remain in their existing conversations. Users can route selected addresses to separate endpoints or use catch-all routing. A TypeScript SDK and REST API support programmatic workflows. Incoming mail passes through spam detection, with settings to reject, flag, or accept spam. Listed protections include API keys, HMAC signatures, and rate limits. Data is encrypted in transit and at rest, with access controls and AWS infrastructure. Email is typically retained for 30 days unless settings change, and deletion can be requested. Inbound does not remove quoted reply history or extract business fields from attachments with OCR or AI. Plans start at $9 a month; no free plan is listed despite the freemium label.
Who it suits
Inbound suits developers building transactional email, inbound webhook processing, and AI-assisted workflows. It is useful when applications need parsed messages, routing, threading, and webhook delivery.
Good to know, and what to watch
- Parses email content and attachment metadata into JSON
- Webhook failures can be retried
- Supports address routing and catch-all routing
- Includes TypeScript SDK and REST API
- Spam handling offers reject, flag, or accept options
- No free plan listed
- Does not remove quoted reply history
- No OCR or AI business-field extraction
- Large payloads can reduce attachment or header data
Plans
Every plan and priceDefault
Pro
Growth
Scale
Free plan
The verdict
Inbound provides structured email parsing, routing, threading, and webhook delivery for application workflows. Review its payload limits, retention settings, and plan terms before choosing it.
What the maker publishes
- Attachment limits
- When a payload exceeds 1 MB, attachment bodies in raw MIME are replaced with a placeholder; if it remains too large, parsed headers are emptied. source
- Data protection
- The privacy policy says data is encrypted in transit and at rest, with access controls, authentication, security monitoring, and AWS infrastructure. source
- Email parsing
- Inbound parses received email into JSON containing addresses, headers, text and HTML bodies, raw MIME, thread information, and attachment metadata with download links. source
- Integrations
- The features page names dub.co for open and click tracking and lists configurable endpoints, routing, and a TypeScript SDK. source
- Intended users
- Inbound describes itself as an email platform for developers building transactional email, inbound webhook processing, and AI-assisted workflows. source
- Parsing limits
- Inbound parses message structure but does not remove quoted reply history or extract business fields from attachments using OCR or AI. source
- Retention
- Email data is typically retained for 30 days unless the user configures different retention settings, and users may request deletion. source
- Routing
- Users can route specific addresses to separate endpoints or enable catch-all routing for other addresses on the domain. source
- SDK and API
- Inbound provides a TypeScript SDK and REST API for programmatic email workflows. source
- Security controls
- The features page lists API keys, HMAC signatures, and rate limits as integration protections. source
- Spam handling
- Inbound runs incoming email through spam detection, and mailbox settings let users reject, flag, or accept spam. source
- Support
- The Default plan includes basic support, and the terms say support availability and response times vary by plan. source
- Threading
- Inbound includes thread identifiers and sets In-Reply-To and References when replying so responses stay in the existing email thread. source
- Webhook delivery
- Inbound delivers parsed email to webhook endpoints after receipt and parsing, and failed deliveries can be retried from the dashboard or API. source
Checked against the maker's pages on 4 Oct 2026.