Let your app receive and answer email
Mail to an address on your domain is parsed, checked and posted to your webhook as JSON. Build support inboxes, reply-by-email, invoice intake and email-to-task without running a mail server.
{
"type": "inbound.received",
"data": {
"id": "6f1c…",
"from": { "name": "Ada Lovelace", "address": "ada@example.com" },
"to": [{ "name": null, "address": "reply+ticket-123@acme.com" }],
"subject": "Re: Your ticket #123",
"text": "Thanks, that fixed it!",
"html": "<p>Thanks, that fixed it!</p>",
"message_id": "CAF3x…@mail.gmail.com",
"attachments": [{ "index": 0, "filename": "screenshot.png", "size": 48213, "url": "https://…" }],
"auth": { "spf": "pass", "dkimPass": true, "aligned": true }
}
}Parsed, verified and signed before it reaches you
Addresses and patterns
Route support@, a prefix like reply+* for per-ticket addresses, or a catch-all for everything without a mailbox.
Clean JSON
Sender, recipients, subject, text and HTML bodies, headers, Message-ID and References, ready to store.
Authentication results
SPF, DKIM and DMARC are checked on arrival, so you can trust the sender before acting on a message.
Attachments
Signed download links for every attachment and the raw message, plus API access with your key.
Signed webhooks
Each delivery is signed with Standard Webhooks. The SDK and the WordPress plugin verify it for you.
History and replay
Every message and delivery attempt is kept. Replay one message, or all failures after an outage.
Receive and reply in one handler
- 1
Point your MX record to Voozin
The domain page shows the record. Existing mailboxes on the domain keep working.
- 2
Create a route
Choose the address or pattern and the webhook endpoint, in the dashboard or with the API.
- 3
Handle inbound.received
Store the message, then reply through the sending API. Replies thread in the sender's mail app.
import { Voozin } from "voozin";
import { createWebhookHandler } from "voozin/next";
const voozin = new Voozin(process.env.VOOZIN_API_KEY);
export const POST = createWebhookHandler({
secret: process.env.VOOZIN_WEBHOOK_SECRET!,
async onEvent(event) {
if (event.type !== "inbound.received") return;
const ticket = await tickets.addMessage(event.data);
await voozin.inbound.reply(
event.data,
{ from: "Acme Support <support@acme.com>", text: `We got it. Ticket #${ticket.id}` },
{ idempotencyKey: `ack-${event.data.id}` },
);
},
});What teams build with it
Support inbox in your product
Turn support@ into tickets in your own app, with replies sent from the same address.
Reply by email
Give each comment, order or ticket a reply+id@ address, and post replies straight back to it.
Invoices and documents
Forward invoices to invoices@ and process the PDF attachments automatically.
Pricing
$15 per route / month
Questions, answered
Routing, threading, retries and attachments.
Yes. Addresses that are Voozin mailboxes never match a route, so support@ can go to your app while ada@ stays a normal inbox. The domain's MX record must point to Voozin. If your team's mail is hosted elsewhere, add a subdomain such as in.acme.com for app addresses instead.
An exact local part such as support, a prefix ending in * such as reply+*, or * for every address without a mailbox. Exact patterns win over prefixes, and prefixes win over the catch-all.
The SDK's inbound.reply sends to the Reply-To or sender address, prefixes the subject with Re: and sets In-Reply-To and References, so Gmail, Outlook and Apple Mail show it in the same conversation.
Deliveries are retried with backoff, and every message is stored. You can replay one message, or every failed delivery after an outage, from the dashboard or the API.
Each attachment has a signed download link that is valid for 24 hours, and you can always fetch attachments and the raw message through the API with your key.
Mail delivered to a webhook has to be readable by your application, so Voozin decrypts it for delivery. Use a mailbox for mail that must stay end-to-end encrypted; a route can also copy messages into a mailbox.


Move your first domain today
Create an organization, add a domain and follow the guided DNS setup. Most teams are receiving mail within the hour.