Receive email, not just send it.

Inbox

Read it in your inbox. Reply from your domain.

Mail to any address on your domain lands in the dashboard inbox, threaded with your replies. No code needed, and your app still gets the webhook.

  • Conversations

    Replies thread with what you sent. Read state is shared.

  • Reply, reply all, forward

    Sends from your own domain, in the same thread.

  • Spam and blocking

    Spam is filtered. Report it or block a sender.

How it works

Sending, in reverse.

Mail lands and we parse it. You read it in the inbox; your app gets a signed webhook.

  1. Point one MX record
  2. We parse the MIME
  3. Inbox and webhook

One event, one handler

It's just another webhook.

email.received: the same signed envelope as every other webhook.

email.receivednowSending200
email.opened2s200
email.clicked9s200
sms.received14s200
email.delivered31s200

Safe by default

Scanned, verified, never in your payload.

Scanned. Verdicts on the message. Bytes stay out of the payload.

  • Spam & virus

    Confirmed viruses rejected at ingest.

  • Attachments

    Metadata on the event. Bytes via signed URLs.

  • SPF · DKIM · DMARC

    Authentication results on the message.

MCMaya Chento support@acme.com
SpamPASS
VirusPASS
DMARCPASS
invoice-error.png182.0 KB

Developer-first

Fetch the full message on demand.

Same REST API and keys you send with.

  • Parsed

    Headers, text, HTML, attachment metadata.

  • Signed downloads

    URLs expire. No leaked links.

Read a received email
import { Unitpost } from "unitpost";

const unitpost = new Unitpost(process.env.UNITPOST_API_KEY);

// The webhook carries metadata — fetch the parsed message on demand.
const { data: email } = await unitpost.email.receivedGet("received_email_9f2c…");
console.log(email.subject, email.text, email.spam_verdict);

// Attachments come back as signed, expiring download URLs.
const { data: file } = await unitpost.email.receivedAttachmentUrl(
  email.id,
  email.attachments[0].id,
);
console.log(file.url); // expires in 5 minutes

What you can build

Turn inbound mail into product

Every message is a structured event. The inbox is an integration point.

Support inboxes

support@ becomes events. Tickets open in your helpdesk.

Reply handling

Users reply by email. Threads land back in your app.

Parse & extract

Forwarded receipts, orders, forms. Pull the data out.

Email-to-action

Create a task, log an expense, kick off a build.

Attachment intake

Collect files by email. Fetch them over signed URLs.

Conversation history

Full thread next to what you sent. Per contact.

Included free

Send and receive on your domain

$0/ mo

  • Included on every plan, including free
  • One MX record, catch-all for your domain
  • An inbox: threads, reply, forward, spam
  • Signed email.received webhooks
  • Parsed headers, bodies & attachments
  • Same REST API, dashboard & SDKs

Questions

Common questions

How do I receive email on my own domain with Unitpost?

Turn on receiving for a domain you already send from, in the dashboard or with the API (capabilities.receiving on the domain, also from the MCP server and the CLI), and add the one MX record we show you. Once the MX verifies, every message addressed to that domain is parsed and lands in your dashboard inbox; subscribe a webhook endpoint to email.received and it's POSTed to your app too. There's no new domain and no separate account: receiving reuses the domain authentication you already verified for sending.

Does the inbound MX record break my existing email?

It can, which is why we check first. Our MX must be the lowest-priority value present or mail won't route to us — so if your root domain already has MX records for Google Workspace or Microsoft 365, pointing it at us would stop mail reaching those inboxes. We detect the conflict, warn you before you proceed, and recommend using a subdomain like inbound.yourdomain instead.

Which addresses receive mail — do I configure each one?

No per-address setup. Receiving is catch-all: any address at the enabled domain lands, and you route on the to field in your own handler. So support@, billing@, and reply+abc123@ all arrive without provisioning anything, which is what makes per-user or per-thread reply addresses practical.

Can my team read and reply without writing code?

Yes. Received mail shows in the dashboard under Emails, Received, grouped into conversations with your replies. Anyone in the workspace can read it, reply, reply all or forward from your domain, report spam, or block a sender, and read state is shared, so the team sees what's been handled. It's an inbox over the mail your domain receives, not a hosted mailbox: there's no IMAP or POP3.

How do I get the message body and attachments?

The email.received webhook carries metadata only — sender, recipients, subject, message_id, and attachment descriptors — so payloads stay small. Fetch the parsed message with GET /api/v1/email/received/{id}, which inlines text and HTML when they're small, then call GET /api/v1/email/received/{id}/attachments/{attachmentId} for a signed download URL that expires in about five minutes. Both need the emails:read scope.

Are inbound messages checked for spam and viruses?

Yes. Every message carries spam, virus, SPF, DKIM, and DMARC verdicts on the event and the stored record, so your handler decides how much to trust a sender. Confirmed viruses are rejected at ingest rather than handed to you. Messages over 25 MB in total, including attachments, are also rejected at ingest and the sender gets a failure notice.

Can I reply in-thread to an email I received?

Yes. Pass the received email's id as in_reply_to on POST /api/v1/email and we populate the In-Reply-To and References headers from the stored Message-ID chain, and prefix the subject with Re: if it isn't already — so mail clients thread the conversation. Any In-Reply-To or References header you set explicitly still wins.

Is inbound email included on the free plan?

Yes. Receiving is included on every plan, including free; it is not a paid add-on. You need a verified domain; a webhook subscribed to email.received is optional, since mail also lands in the inbox. Received messages don't draw the paid sending allowance; on the free plan they share the monthly email quota with outbound sends.