MailFrame is an API for developers who need to turn inbound email into typed JSON validated against a schema. A request can contain raw RFC 822 MIME or plain-text email-like input alongside a JSON Schema, and the API returns validated JSON synchronously. Developers can provide an inline schema without registering or use prebuilt schemas for receipts and orders from services including Stripe, Shopify, PayPal, Amazon, Apple App Store, and Google Play, as well as invoices, travel bookings, GitHub notifications, and shipping notices. Signed HMAC-SHA256 webhooks support retries, attempt history, a dead-letter queue, and replay for downstream systems that accept webhooks. The current API accepts raw MIME and plain text; PDF and image parsing are planned, not available now. MailFrame says it retains raw email only as long as needed for delivery and debugging and does not sell or share customer data. It stores API keys hashed. The service is in limited early access, onboarding developers in weekly batches. Free includes 100 parse operations per month with no credit card required. Paid plans start at 19.00 USD per month. SOC 2 Type II is on the roadmap, and MailFrame says it is not yet HIPAA-eligible as a Business Associate.
Who it is for
MailFrame is aimed at app developers integrating inbound document email into their own service. It suits workflows that can send raw email content and receive structured JSON or webhook delivery.
What is good
- Accepts inline JSON Schemas without registration.
- Prebuilt schemas cover receipts, invoices, and notifications.
- Webhook delivery includes retries and replay.
- Free plan includes 100 parse operations per month.
What to know first
- PDF and image input are planned, not currently available.
- Limited early access onboards developers in weekly batches.
- Not yet HIPAA-eligible as a Business Associate.
- SOC 2 Type II remains on the roadmap.
Freedom251 review
MailFrame: the full review
MailFrame offers schema-based email parsing and webhook delivery for developer-built workflows. Its current input is limited to raw MIME and plain text, and availability remains limited early access.
Overview
MailFrame is an email-parsing API aimed at developers building inbound-email processing into their own services. It will suit teams that need structured fields from email bodies and want to define the output schema themselves. Its webhook controls and inline schemas make it flexible, but its email-only input and limited early access narrow its fit.
Key features
Schema-based parsing
A request pairs raw RFC 822 MIME or plain-text email-like input with a JSON Schema, and MailFrame returns validated JSON synchronously. Inline schemas work without registration, which is useful when an application needs a precise output shape without a separate schema setup step. A library of ready-made schemas covers Stripe and Shopify receipts or orders, PayPal and Amazon receipts, Apple App Store and Google Play receipts, GitHub notifications, invoices, travel bookings, and shipping notifications.
Webhook delivery
MailFrame can deliver results through signed HMAC-SHA256 webhooks, with retries, attempt history, a dead-letter queue, and replay. These safeguards are useful when a failed delivery needs investigation or another attempt. The API-first model suits downstream systems that accept webhooks; it is less compelling for teams seeking a standalone inbox or visual document-processing workflow.
Input, security, and compliance
The current API accepts email content, not PDF or image input. Attachment parsing and OCR extraction are unavailable, and PDF and image input remain planned, so teams whose documents arrive as attachments should choose another tool for that work. MailFrame says it keeps raw email content only as long as needed to deliver responses and support debugging, and does not sell or share customer data. API keys are stored hashed, so MailFrame cannot recover the raw key from its records. SOC 2 Type II is on the roadmap, and MailFrame is not yet HIPAA-eligible as a Business Associate; regulated workloads requiring HIPAA eligibility should look elsewhere.
Pricing
The Free plan costs $0 /mo and includes 100 parse operations per month, one active schema, webhook delivery, and community support, with no credit card required. It is a useful way to validate a workflow, but the monthly quota and single schema limit ongoing or multi-format use.
Indie costs $19 /mo for 500 parse operations per month, five active schemas, signed webhook delivery, email support, and schema versioning. It fits a small integration that has outgrown the Free cap, though the quota and schema ceiling remain modest. Additional documents cost $0.038 per doc after the allowance.
Startup costs $49 /mo for 5,000 parse operations per month, unlimited schemas, API key scoping, and priority support. It is the more suitable tier for a growing service with multiple formats or access boundaries. PDF and image input and confidence scoring are planned, not current benefits. Extra documents cost $0.0098 per doc after the allowance.
Scale costs $149 /mo and raises the quota to 50,000 parse operations per month, with unlimited schemas, cache hits included, custom webhook rate limits, and an uptime target post-GA. Async and batch API access are planned. Its lower overage rate of $0.003 per doc suits higher-volume use, but the uptime target applies only post-GA.
Enterprise has custom pricing and starts at 100k+ parse operations per month, with custom volume pricing, dedicated infrastructure, custom SLAs, an account manager, and SSO / SAML. SOC 2 remains on the roadmap; the listed overage rate is <$0.003 per doc. MailFrame also describes its Free tier as a way to validate the product before upgrading; the plan details make the monthly 100-operation allowance the practical starting point. MailFrame is in limited early access and onboards developers in weekly batches, which may delay access.
Platforms
MailFrame is available through an API and on the web. Its API orientation favors developers integrating parsing into a service rather than users looking for a ready-made end-user workflow.
Who it's for
MailFrame is best for developers who need typed, schema-validated data from inbound email and can route results into webhook-compatible systems. It is a poor fit for attachment-heavy workflows, OCR needs, or systems that require HIPAA eligibility now.
Pros and cons
Pros
- Inline JSON Schemas work without registration, giving developers control over the returned data shape.
- Webhook retries, delivery history, a dead-letter queue, and replay help teams manage delivery failures.
- The Free plan provides 100 parse operations per month without a credit card, enough to evaluate a basic integration.
Cons
- No PDF or image input, attachment parsing, or OCR is available now, excluding common document-email workflows.
- MailFrame is not HIPAA-eligible as a Business Associate, and SOC 2 Type II is still on the roadmap.
- Limited early access with weekly onboarding batches makes immediate availability uncertain.
Alternatives
Email Parsing Software is the broader category for comparing tools. Choose DigiParser if payslip processing is the priority: its paid plan starts at $14/month for 100 payslips, with enterprise pricing for 1,000+ documents per month. MailParse is another API and web option; its Free plan includes 100 emails per month, webhook delivery, REST polling, and one inbound address, making it worth comparing for workflows that need polling or a dedicated inbound address.
noima offers a one-time Free allowance of 10 documents with 30 days of retention, while its Starter plan costs €12 per month for 150 documents per month and 60 days of retention. Parserr has a Free plan with 15 emails and 10 documents per month, one inbox, unlimited parsing rules and integrations, plus Zapier and Microsoft Flow; it may suit a small integration centered on those services. Parseur offers a Free plan with up to 20 pages per month, one user, 90-day document retention, and unlimited mailboxes and extracted fields, which is a different fit for page-based document processing.
Parsio Receipt OCR is worth considering when receipt OCR is central: its Free plan includes 30 credits per month, 30-day retention, and one user. Parsli provides 10 free pages on signup, unlimited parsers, API access, and all integrations; compare it if those are the relevant starting needs. Dewmail is a free, self-hosted alternative.
Verdict
Choose MailFrame if you are building an inbound-email pipeline and need schema-controlled JSON with resilient webhook delivery. Its strongest case is developer control over both output shape and delivery; look elsewhere if you need attachments, OCR, HIPAA eligibility, or access outside its limited early-access onboarding.
MailFrame plans and pricing
All plansCompared on email parsing software
- Free plan
- Yes
- Paid from
- $19/mo
- Attachment parsing
- No
- OCR extraction
- No
- Webhook delivery
- Yes
- API access
- Yes
- Custom extraction fields
- Yes
- Monthly email limit
- 500 emails/mo



