What is Mandrill Inbound?
Mandrill is the transactional email API from Mailchimp, targeting developers who use the Mailchimp ecosystem. Mandrill Inbound allows you to receive emails at a Mandrill subdomain address and have them delivered to a webhook endpoint. It is used by teams that are already embedded in the Mailchimp/Mandrill ecosystem for outbound sending.
Mandrill Inbound is offered by Mailchimp / Intuit and is a popular choice for teams that need to process inbound email at scale. It integrates into existing workflows through routing rules, filters, and forwarding options that make it flexible for many use cases.
However, as teams grow and requirements evolve, many developers find that Mandrill Inbound introduces complexity, cost, or integration overhead that does not match what they actually need. JsonHook was designed to address these gaps by delivering every inbound email as a clean, structured JSON webhook with zero configuration required.
Pricing: Mandrill requires a paid Mailchimp plan ($13+/mo); add-on blocks of 25,000 emails start at $20/mo on top of the Mailchimp subscription
- No ecosystem lock-in: JsonHook is a standalone service — no Mailchimp subscription required
- Modern REST API with standard Bearer token authentication
- Per-address webhook routing: Each address independently routes to its own endpoint
- Automatic retries and delivery logs included in all plans
- HMAC-SHA256 signatures on every webhook delivery
Limitations of Mandrill Inbound
Before committing to Mandrill Inbound for your inbound email pipeline, it is important to understand where it falls short. Development teams frequently encounter the following pain points:
- Requires a paid Mailchimp subscription: Mandrill is an add-on to Mailchimp — you cannot use it without a Mailchimp paid plan, making it expensive for teams that only need inbound email processing
- Outdated API design: Mandrill's API uses an older design pattern with API key passed in the request body rather than standard Authorization headers, creating integration friction
- No per-address webhook routing: Inbound webhook routes are defined at the routing rule level, not per email address — managing many addresses requires complex rule maintenance
- No automatic retries: Failed webhook deliveries are not automatically retried
- Mandrill subdomains only (unless on higher plans): Basic inbound routing uses Mandrill-provided subdomains; custom domain inbound requires additional configuration
These limitations become particularly painful at scale or when building applications that require low-latency, reliable delivery of email data as structured JSON. JsonHook solves each of these issues out of the box.
Switch from Mandrill Inbound to JsonHook
Free tier: 100 emails/month. Migrate in minutes.
Get Free API KeyMandrill Inbound vs JsonHook
The following table provides a direct, feature-by-feature comparison between Mandrill Inbound and JsonHook. Both tools handle inbound email processing, but they differ significantly in approach, pricing, and developer experience.
| Feature | Mandrill Inbound | JsonHook |
|---|---|---|
| Structured JSON output | ✓ JSON via webhook | ✓ JSON payload |
| HMAC-SHA256 signatures | Basic signature check only | ✓ Standard HMAC-SHA256 |
| Automatic retries | ✗ No retry | ✓ With backoff |
| Requires parent subscription | Mailchimp paid plan required | ✓ Standalone service |
| Per-address routing | Rule-based only | ✓ Per address |
| Free tier | ✗ None | 100 emails/mo free |
| Pricing (5K emails/mo) | $13 Mailchimp + $20 Mandrill block | $12/mo |
| API authentication | API key in request body | Standard Bearer token |
| Attachment handling | ✓ Included | ✓ Included |
| Setup complexity | High (Mailchimp + Mandrill config) | Low (API call + URL) |
JsonHook is purpose-built for developers who want inbound email delivered as a JSON webhook endpoint call — nothing more, nothing less. There is no dashboard complexity to navigate for basic delivery, no per-message parsing fees, and no lock-in to a specific email provider SDK.
How to Migrate from Mandrill Inbound to JsonHook
Migrating from Mandrill Inbound to JsonHook is straightforward. Most teams complete the switch in under 30 minutes. Follow the steps below to move your inbound email pipeline without downtime:
- Register for JsonHook and create inbound addresses via the API, specifying the webhook URL for each address
- Forward emails from your Mandrill inbound addresses to your new JsonHook addresses, or update your domain routing to point directly to JsonHook
- Update your webhook handler code: replace Mandrill's webhook payload structure with JsonHook's JSON schema
- Verify successful delivery in JsonHook's delivery log and then remove Mandrill inbound routing rules
Because JsonHook delivers a consistent JSON payload for every inbound email — including parsed headers, text body, HTML body, and attachment metadata — you typically need fewer lines of application code after the migration than before.
Pricing Comparison
Mandrill Inbound pricing: Mandrill requires a paid Mailchimp plan ($13+/mo); add-on blocks of 25,000 emails start at $20/mo on top of the Mailchimp subscription. Costs can escalate quickly as email volume grows, and many plans gate key features like webhook retries or attachment handling behind higher tiers.
JsonHook offers transparent, volume-based pricing with a generous free tier that is suitable for side projects, staging environments, and low-volume production use:
| Plan | Price | Emails / Month | Features |
|---|---|---|---|
| Free | $0 | 100 | All core features, 1 address, HMAC signatures |
| Starter | $12/mo | 5,000 | 5 addresses, retries, attachment parsing |
| Pro | $39/mo | 50,000 | Unlimited addresses, priority delivery, logs |
Compared to Mandrill Inbound, JsonHook's Starter plan ($12/mo) covers the majority of small-to-medium use cases at a fraction of the cost, with no per-email parsing fees and no credit card required for the free tier.