Email parser schemas
A library of ready-to-use email parser schemas. Choose one, POST raw MIME or
plain-text email to /v1/parse,
and get typed, schema-validated JSON back — no regex, no fragile screen-scraping.
New to MailFrame? Start with the
email to JSON API guide,
skim the API docs, or
try the free in-browser parser.
How to use these schemas
- 1
Pick a schema (or define your own)
Browse the library below and choose the schema that matches the sender you're parsing — Stripe, Shopify, PayPal, GitHub, and more. Nothing matches? Supply your own inline JSON Schema describing the fields you want.
- 2
Reference it in your request
Pass the schema's name — the JSON Schema title shown on its page, like stripe_receipt — as the request's schema_id field, or paste an inline JSON Schema itself, alongside the raw email. MailFrame extracts against that shape and validates the result before returning it.
- 3
POST raw MIME to /v1/parse
Send the raw RFC 822 MIME (or plain-text) email with a bearer token to POST /v1/parse. No regex, no scraping, no template-specific rules to maintain.
- 4
Read typed JSON back
MailFrame returns typed, schema-validated JSON synchronously in the HTTP response — or via signed webhook delivery with retries, attempt history, dead-letter, and replay if you prefer async.
Which schema should I use?
- Match the sender. If you're parsing receipts, orders, or notifications from a vendor in the list below, start with that schema — it already maps the fields those emails contain.
- No exact match? Bring your own. Supply an inline JSON Schema on the request describing the fields you want. The same extract-and-validate contract applies to any email.
- Tiers are a guide, not a limit. Each schema is tagged with a tier that helps prioritize the most common parser templates — every published schema works the same way through
/v1/parse. - Check the cost. Each call is one parse operation — see pricing for the free tier and limits.
Browse the schema library
Parse Stripe Receipts
Turn Stripe payment receipts and invoices into typed JSON — receipt ID, amount, currency, card brand, last four, customer email, and payment status.
Parse Shopify Orders
Extract Shopify order confirmations into typed JSON — order number, line items, totals, fulfillment status, and customer details from every store email.
Parse Amazon Order Emails
Turn Amazon order confirmations and shipping alerts into typed JSON — order ID, line items, totals, delivery estimate, and seller, ready for your database.
Parse PayPal Receipts
Convert PayPal payment receipt emails into typed JSON — transaction ID, amount, currency, fees, net proceeds, payer, recipient, and payment status.
Parse Apple App Store Receipts
Parse Apple App Store receipt emails into typed JSON — order ID, Apple ID, purchased items, subscription type, tax, totals, and renewal status.
Parse Google Play Receipts
Extract Google Play order receipt emails into typed JSON — order ID, item title, tax, totals, currency, and auto-renewal status for each transaction.
Parse GitHub Notification Emails
Turn GitHub notification emails into typed JSON — repository, thread type, thread number, actor, action, and the canonical URL. Schema-first.
Parse Invoice & Payment-Due Emails
Turn invoice and payment-due emails into typed JSON — invoice number, vendor, amount due, currency, issue and due dates, PO number, and payment status.
Parse Travel Booking Confirmation Emails
Turn flight, hotel, and rental-car confirmation emails into typed JSON — confirmation code, provider, traveler, dates, locations, price, and per-segment legs.
Parse Shipping & Delivery Notification Emails
Turn FedEx, UPS, USPS, and DHL shipment and delivery notifications into typed JSON — carrier, tracking number, status, origin, destination, and ETA.
Parse Calendar Meeting Invite Emails
Turn Google Calendar, Outlook, and iCloud meeting invite emails into typed JSON — event title, organizer, attendees, start and end times, location, and response.
Parse Subscription Renewal Emails
Turn SaaS billing renewal emails from Vercel, Netlify, OpenAI, Notion, Linear, Figma, and others into typed JSON — subscription ID, product, plan, next renewal date, amount, payment method, and renewal status.
Parse Linear Notification Emails
Turn Linear issue, project, cycle, and @-mention notification emails into typed JSON — workspace, project, issue ID, issue title, actor, action, due date, and canonical URL. Schema-first.
Parse Job Application Emails
Turn Greenhouse, Lever, Workday, and Ashby candidate-status emails into typed JSON — application status, role, company, recruiter, posting ID, dates, and offer details. Schema-first.
Parse Bank & Card Transaction Emails
Turn Chase, Bank of America, Wells Fargo, Capital One, Citi, USAA, PNC, Revolut, Monzo, and Starling transaction alerts into typed JSON — transaction type, amount, balance, merchant, posted date, and account mask. Schema-first.
Parse Rideshare & Delivery Receipt Emails
Turn Uber, Lyft, DoorDash, and Grubhub receipts into typed JSON — service, trip/delivery ID, fare, subtotal, tax, tip, currency, pickup/dropoff or merchant, driver/courier, timestamp. Schema-first.
Parse Domain & Hosting Renewal Emails
Turn GoDaddy, Namecheap, Cloudflare, Squarespace, and AWS domain/hosting renewal emails into typed JSON — registrar, domain, registration period, amount, currency, expiration date, auto-renew status, and renewal status.
Frequently asked questions
What is an email parser schema?
An email parser schema is a JSON Schema document that describes the exact fields you want extracted from an email — their names, types, and constraints (required/optional, patterns, enums). You hand it to MailFrame, MailFrame extracts against it and validates the result, and you get back typed JSON that matches the shape you defined.
How do I use a schema from this library?
Open the schema's page to see its fields, example output, and the exact JSON Schema. Pass its name — the JSON Schema title shown on the page, like stripe_receipt — as the schema_id field of a POST /v1/parse request along with the raw MIME email and a bearer token, or send an inline JSON Schema instead. MailFrame returns the validated JSON in the same HTTP response. The email-to-JSON API guide walks through a full request and response.
Do I have to use a pre-built schema?
No. Every schema here is a starting point. You can supply your own inline JSON Schema on any POST /v1/parse request when the sender you need isn't in the library yet — the extraction is validated against whatever schema you send.
How are parse results delivered?
Synchronously, in the HTTP response to your POST /v1/parse request — the body contains the typed data payload, the parse status, and any schema validation_errors. Signed webhook delivery (HMAC-signed, with retries, attempt history, a dead-letter queue, and replay) is available for teams that prefer asynchronous delivery. Inbox forwarding and PDF/image input are on the roadmap.
What email formats can I send?
Raw RFC 822 MIME — the wire format of every email — or plain-text email-like input. Multipart messages, nested MIME parts, and common transfer encodings (base64, quoted-printable) are handled. PDF and image input are planned, not yet shipped.
Is it free to try?
Yes. The Free tier includes 100 parse operations per month with no credit card required. You can also try the in-browser Stripe receipt parser tool without signing up at all.
Need a schema we don't have?
We add new schemas based on developer demand. Request one during early access and we'll prioritise the most-requested senders.
Request early access