Email receiving API
Receive email over MX and turn it into webhooks.
NoticeAPI accepts inbound email for verified receiving domains, parses MIME, stores bodies and attachments, and sends a signed email.received webhook. It is an API workflow, not mailbox hosting.
Webhook first
Receive a small signed payload with sender, recipients, subject, timestamp, message id, and attachment metadata. Fetch full content only when your app needs it.
{
"type": "email.received",
"emailId": "rx_0f83...",
"messageId": "<[email protected]>",
"from": "[email protected]",
"to": ["[email protected]"],
"subject": "Re: Invoice",
"receivedFor": ["[email protected]"],
"receivedAt": "2026-07-03T18:04:14.000Z",
"attachments": [
{ "id": "att_123", "filename": "invoice.pdf", "contentType": "application/pdf", "size": 48213 }
],
"accountId": "..."
}API retrieval
Pull HTML, text, headers, and attachments through authenticated endpoints. This keeps webhook handlers quick and works cleanly in serverless apps.
curl https://www.noticeapi.com/api/v1/receiving/emails/rx_0f83... \ -H "Authorization: Bearer ntc_xxxxxxxxxxxxxxxxxxxx"
Verified receiving domains
Add a dedicated reply subdomain, publish TXT and MX records, then receive mail for any local part.
Attachment metadata first
Webhook payloads include attachment ids, filenames, content types, and sizes. Download content through the API.
Signed events
The same HMAC webhook signature model covers delivery events and inbound email.received events.
What this is, and what it is not
Built for app workflows
Contact form replies, ticket ingestion, reply handling, document intake, and product workflows that need inbound email as structured data.
Not mailbox hosting
No IMAP, POP3, webmail, shared inbox, or end-user mailbox product. Use a real mailbox provider for human inboxes.