MailParse
mailparse.dev
- Free plan
- Web
- API
What MailParse is
MailParse receives inbound email, converts MIME messages into structured JSON, and delivers the results through webhooks or a REST polling API. It extracts text and HTML bodies, inline images, attachments, headers, and routing information, including from nested and multipart messages. Webhook delivery uses exponential-backoff retries and HMAC signature verification; the polling API supports filters for sender, date range, subject, or attachment type, plus cursor-based pagination. MailParse validates SPF, DKIM, and DMARC, adds spam scoring, and lets users set per-address rules to reject, quarantine, or pass messages. Attachments are available through signed download URLs and retained for 72 hours by default, with retention configurable by plan. Users can bring a domain by adding an MX record to MailParse’s servers and verifying ownership. If a webhook is down, delivery retries for up to 24 hours, and messages can be replayed or retrieved through polling. The Free plan costs nothing and includes 100 emails/month. Pro costs $29 a month; Scale costs $99 a month.
Who it suits
MailParse suits teams that need to extract email content and attachments into structured data for their systems. Its webhook and polling options support different delivery workflows, while plan limits and retention terms matter when choosing a tier.
Good to know, and what to watch
- Extracts content and metadata from nested and multipart email
- Supports webhook delivery and REST polling
- Validates SPF, DKIM, and DMARC
- Allows manual replay or polling retrieval after webhook downtime
- Offers a free plan with 100 emails/month
- Attachments are retained for 72 hours by default
- Custom retention is listed on the Scale plan
- Free plan includes one inbound address
Plans
Every plan and priceFree
Pro
Scale
Free plan
The verdict
MailParse offers email parsing, filtering, and recovery paths for webhook delivery problems, with both webhook and polling access. Choose a plan based on message volume, address and domain needs, support level, and attachment retention.
What the maker publishes
- Attachment retention
- Attachments are available through signed download URLs and are retained for 72 hours by default, with retention configurable by plan. source
- Custom domains
- Users can bring their own domain by adding an MX record to MailParse’s servers and verifying domain ownership in the dashboard. source
- Delivery recovery
- If a webhook endpoint is down, MailParse retries for up to 24 hours, and users can manually replay emails or retrieve them through polling. source
- Integrations
- The maker describes webhook and REST API delivery, but the opened product page does not name specific third-party integrations. source
- MIME parsing
- It extracts text and HTML bodies, inline images, attachments, headers, and routing information, including from nested and multipart messages. source
- Privacy
- MailParse says it does not sell personal information and may share it with service providers, when legally required, to protect users, in business transfers, or with consent. source
- Purpose
- MailParse receives inbound emails, parses MIME into structured JSON, and delivers the results through webhooks or a REST polling API. source
- REST API
- The REST polling API supports filtering by sender, date range, subject, or attachment type, with cursor-based pagination. source
- Security statement
- The privacy policy says MailParse uses appropriate technical and organizational safeguards, while noting that internet transmission and electronic storage cannot be guaranteed completely secure. source
- Spam and authentication
- MailParse validates SPF, DKIM, and DMARC and includes spam scoring and per-address rules to reject, quarantine, or pass messages. source
- Support
- The Free plan lists community support, Pro lists priority support, and Scale lists dedicated support. source
- Support contact
- The contact page lists [email protected] as a direct support email address. source
- Webhook delivery
- Parsed emails are POSTed to a configured webhook, with exponential-backoff retries and HMAC signature verification. source
Checked against the maker's pages on 4 Oct 2026.