Niches · Email delivery APIs

Receive replies or forwarded mail into the application

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
14companies, fit with a limit
31companies carry the tag
10share of the category's work
4first-hand accounts

What counts as done

A webhook carrying sender, recipients, subject, reply text with quoted history stripped and attachments (or one fetch to get them), signed or verifiable.

Measured, for our own tests: the webhook arrives within 30 seconds. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: let users reply to notifications, parse forwarded invoices, route support@ to my app, attach forwarded mail to the order

Does the job, with a limit 14

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
AhaSend API + MCP BB
AhaSend B.V.
Routes post parsed JSON with optional base64 attachments, a Strip Replies option and an HMAC signature, on every plan. No delivery latency is stated, and retries stretch over 11 hours with a 5-second endpoint timeout. source
Amazon SES BB
Amazon Web Services, Inc.
Receipt rules publish full MIME to SNS up to 150 KB (larger mail bounces) or store it in S3 for a Lambda; SNS messages are signed. No reply-text stripping, so the app parses quoted history itself. source
Brevo API + MCP E
Sendinblue SAS
Inbound parsing posts JSON with ExtractedMarkdownMessage (signature and quoted history removed), InReplyTo and attachment download tokens fetched by one call each. A separate receiving subdomain is required; latency and signing aren't stated. source
Cloudflare Email Service B
Cloudflare, Inc.
Inbound routing hands a ForwardableEmailMessage (headers and raw stream) to a Worker email() handler, free and unmetered. There is no parsed webhook payload or reply stripping, so the app writes its own MIME parsing. source
Groundmail API + MCP B
Power Only Transit Inc. dba Groundmail
email.received webhooks carry sender, subject, threading headers and attachment metadata only; the body and base64 attachments take one GET /received-emails/{id}. No stripped reply text field, and inbound needs its own subdomain. source
MailerSend BB
MailerSend, Inc.
Inbound routes forward to up to five webhooks or addresses with include_attachments, managed by API. The routing page doesn't document a stripped reply field, signing or delivery time. source
Mailgun API + MCP BB
Mailgun Technologies, Inc.
Route forward() posts parsed fields with stripped-text and stripped-signature, attachments as multipart, and an HMAC signature. Free allows one route, and no delivery latency is stated. source
Mailjet API + MCP C
Mailjet SAS
The Parse API posts JSON with headers, Text-part, Html-part and parts, and attachments are fetched through the Parse API. There is no stripped reply text, signing isn't shown, and latency isn't stated. source
MailPace C
OhMySMTP Ltd
Inbound posts every email on a subdomain to a webhook with headers, raw RFC 822, inReplyTo and base64 attachments, on an active plan with DKIM verified. No stripped reply text, and no delivery latency stated. source
Mailtrap Email API + MCP B
Railsware Products Studio LLC
Inbound inboxes are created by API, mail is parsed to JSON, and webhooks are HMAC-signed with retries. The webhook carries an event and message reference, the body comes from the API, and no stripped reply field is documented. source
Mailchimp Transactional (Mandrill) B
The Rocket Science Group LLC d/b/a Mailchimp
Inbound domains and routes are managed by API and post a msg object with text, html, raw_msg and attachments. No stripped reply text, and no latency stated. source
Postmark API + MCP B
AC PM, LLC
The inbound webhook posts parsed JSON with StrippedTextReply, headers and base64 attachments. Inbound is on Pro and above, webhooks aren't HMAC-signed (Basic Auth or IP checks instead), and no latency is stated. source
Resend API + MCP A
Plus Five Five, Inc.
Receiving webhooks carry metadata only; body, headers and attachments take one call each to the received-email and attachments APIs (e01), received mail counts against the sending quota, and no stripped reply text is offered. source
Twilio SendGrid BB
Twilio Inc.
Inbound Parse posts multipart form data with text, html, headers and attachments up to 30 MB, configured by API. No stripped reply text, and signing is a separate security policy setting. source

Doesn't do this job 4

Listings in the category that do something else, with the reason.

ListingWhy
Loops API + MCP B
Astrodon Corporation
Loops has no inbound email; the docs index lists incoming webhooks for data from other platforms only. source
SendLayer D
SendLayer, LLC
SendLayer has no inbound email; the API reference covers sending, events and webhooks only. source
SMTP2GO API + MCP B
Sand Dune Mail Ltd
SMTP2GO has no inbound email; the API index covers sending, activity, archives, domains and webhooks for outbound events. source
Zoho CPaaS (formerly ZeptoMail) C
Zoho Corporation
No inbound email: the API index covers email sending, domains, agents, logs, templates and suppression only. source

What stops agents finishing

  • inbound not offered (Loops, SMTP2GO, SendLayer, Zoho)
  • inbound only on higher plans (Postmark Pro, Mailgun one free route)

Around it

Before: email.transactional-send. After: document-extraction.parse-invoice, support.create-ticket-from-system, agent-inboxes.inbound-forward-processing.

Where this comes from

Weight 10 of 100 in Email delivery APIs: 4 of 32 accounts: Resend inbound (e01), Rails Action Mailbox on forwarded POs (e29), Cloudflare routing plus Mailgun (e28), and the inbox comparison in e31; weight raised to 10 because it is a buyer check

The same as data: /api/v1/use-cases/email.inbound-to-app.json, or the MCP tool get_use_case with id email.inbound-to-app. Other jobs in this category: /api/v1/niches?category=email.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.