Provision domains, create aliases, automate routing, inspect delivery, and plug reliable email flows into your product without building an SMTP maze first.
API
Alias lifecycle
Create, update, suspend, and route addresses from your backend.
Events
Webhooks
React to delivery, replies, verification, and routing changes in real time.
Ops
Delivery logs
Inspect what happened, when it happened, and where each message went.
Provision aliases
POST /v1/aliases
{
"domain": "acme.dev",
"name": "support",
"destination": "queue@acme.app",
"reply_mode": "reverse-alias",
"webhook": "https://acme.app/hooks/mail"
}Response
201 created{
"id": "als_7gw2e",
"address": "support@acme.dev",
"status": "active",
"webmail": true,
"verified": true
}Live events
domain.verified
acme.dev is ready for routing
MX and TXT records confirmed 6s ago
message.delivered
support@acme.dev to queue@acme.app
Delivered in 1.2s with log trace attached
reply.sent
Reverse alias preserved sender identity
Conversation kept inside your product flow
Delivery trace
Find failures before users do
Logs, verification status, and routing checks stay one click away.
InboxMail gives your team a control plane for domain setup, alias orchestration, and delivery visibility so you can spend engineering time on product behavior instead of email plumbing.
Bring your customer domain into InboxMail, confirm records, and unlock branded addresses with a workflow your support team can also understand.
Spin up addresses from your app, connect them to the right destination, and control reply behavior without waiting on manual mailbox provisioning.
Use webhooks and delivery logs to keep product, support, and ops aligned whenever a domain changes state or a message needs investigation.
The developer surface is built for automation, but the product stays approachable for the rest of the team: domain state, delivery health, and inbox behavior all stay visible.
Alias routing by rule or destination
Send to a queue, a teammate, or a support system with predictable behavior.
Reverse alias replies for branded conversations
Let users or agents reply without exposing internal addresses or breaking the thread.
A shared source of truth for support and engineering
Logs and verification status reduce handoffs when email touches a live workflow.
Webhook example
POST{
"event": "message.delivered",
"alias": "support@acme.dev",
"destination": "queue@acme.app",
"message_id": "msg_4820f",
"trace_id": "trc_19v7c",
"latency_ms": 1187
}Verification
acme.dev
ReadyMX, SPF, and domain state are confirmed and ready for routing.
Latest delivery
support@acme.dev -> queue@acme.app
Delivered in 1.2s with traceable routing metadata.
Fallback behavior
Catch-all active
Unmapped addresses can still land where your workflow expects them.
When email is part of activation, support, or product notifications, your team needs delivery confidence and enough visibility to act quickly when something changes.
5B+
emails successfully routed
99.99%
historical uptime across delivery systems
15+
delivery regions supporting global routing
24/7
active monitoring for deliverability and routing health
Use InboxMail when your team needs domain email, alias orchestration, and dependable routing with a cleaner path from docs to production.