iemails
Pricing
Log inGet started
Get started
Inbound emailWebhook on every message

Let your app
read its email

Receive email at your own domain and get each message as clean, structured data. We tell your app the moment something arrives, so replies, support requests and orders can flow straight into your product.

Start sending free Read the guide
Any address on your domainSPF, DKIM and DMARC resultsSigned webhooks
From
To[email protected]
Subject
ReceivedWebhook sentFetched
1{
2 "type": "email.received",
3 "created_at": "2026-11-11T15:42:08.117Z",
4 "data": {
5 "id": "rcv_3Nx8Pq2Lm",
6 "from": "[email protected]",
7 "to": ["[email protected]"],
8 "subject": "Re: Your invoice for October",
9 "received_at": "2026-11-11T15:42:07.902Z"
10 }
11}
Edit the email on the left, then send it to see what your app gets.
Clean data, not raw MIMESender, subject, text, HTML and headers, already pulled apart.
A webhook for every emailYour app hears about new mail within seconds of it arriving.
Know if it’s genuineSPF, DKIM and DMARC results and a spam score come with each message.
Never stored twiceIf the same message is delivered again, we recognise it and keep one copy.
Email as an input

Give people an address,
let your product answer

Some things are easiest to do by email. Inbound lets your app take part in those conversations instead of sending people to a no-reply address.

Replies
1const email = await mail.inbound.get(event.data.id);
2
3// Which of our emails are they answering?
4const ticket = await db.tickets.findBy({
5 messageId: email.in_reply_to,
6});
7
8await db.messages.create({
9 ticketId: ticket.id,
10 from: email.from,
11 body: email.text,
12});
Developer friendly

A webhook to tell you,
an API to read it

We send a small, signed event when mail arrives. Fetch the full message when you need it, or page through everything you have received.

API reference How webhooks work
route.tsNew mail webhook
1export async function POST(req: Request) {
2 const event = await verifyWebhook(req);
3
4 if (event.type === 'email.received') {
5 // { id, from, to, subject, received_at }
6 await queue.add('inbound', event.data);
7 }
8
9 return new Response(null, { status: 204 });
10}
The event is signed like every other iemails webhook. Check the signature before you trust it.
Getting started

Ready to receive
in three steps.

No mail server to run and no mailboxes to create. Once your domain points to us, every address on it can receive mail.

  • A message delivered twice is stored once, matched by its Message-ID.
  • If your endpoint is down, the message waits with us and the webhook is retried.
  • Senders who are already contacts are linked to their contact record.
Get startedAbout domains
1Add a domain for receivingA subdomain like reply.acme.com is a good choice, so your normal inbox is left alone. Verify it the same way as a sending domain.
2Point its MX record at iemailsMail for that domain now comes to us. Any address works, so support@, replies@ and orders@ all arrive.
3Add a webhook for email.receivedTell us where to send new mail, and your app starts receiving it straight away.
# reply.acme.com
MX 10 <host shown in your dashboard>
FAQ

Questions
about inbound email

Planning a support inbox or reply handling? Tell us what you’re building and an engineer will help.

Talk to an engineer

It lets your app receive email, not just send it. Mail sent to an address on your domain comes to us, we read it and turn it into clean data, and we tell your app about it with a webhook.

Not if you use a subdomain. Point the MX record for something like reply.acme.com at iemails and keep your main domain’s MX records as they are, so your everyday email keeps going to Google Workspace, Microsoft 365 or wherever it goes today.

Any address on a verified domain that points to us. You don’t need to create mailboxes first. Look at the to field to decide what to do with each message.

The sender and their name, the recipients, subject, plain text and HTML body, all headers, the Message-ID and In-Reply-To, the SPF, DKIM and DMARC results, a spam score and the size of the message.

Each received email includes in_reply_to, the Message-ID of the email it answers. Save the Message-ID when you send, and you can match every reply back to its conversation.

The message is still stored with us and the webhook is retried. You can also list received mail through the API at any time to catch up on anything you missed.

Not yet. Today we keep the text, HTML and headers of each message. If you need attachments, let us know. It helps us decide what to build next.

Your app has an inbox.
Start reading it.

Point a domain at us, add a webhook and receive your first email in minutes. Your first 3,000 emails each month are free.

Sign up for free See pricing
iemails

Email infrastructure for teams who would rather read a trace than a support ticket.

Keizersgracht 241
1016 EA Amsterdam, NL

All systems operational·Status
Features
Email APISMTP relayAutomationsAudiencesBroadcastsInboundTemplatesWebhooksDedicated IPs
Resources
ChangelogPricingEnterpriseSecuritySOC 2GDPRBrand
Company
AboutBlogCareersCustomersPhilosophy
Help
SupportStatusMigrateKnowledge baseLegal
Community
EventsOpen sourceInsidersWallpapers
SOC 2 Type IIGDPR readyISO 2700199.99% uptime SLA
© 2026 iemails, Inc. Built in Amsterdam and Bengaluru.
PrivacyTermsDPASecurityCookies