Receive email on your domain.
Route it anywhere.
Turn any address on your domain into a programmable webhook endpoint. Support tickets, reply tracking, invoice processing — without running a mail server.
- One MX record, zero infrastructure
- HMAC-signed JSON payload on every message
- Wildcard, regex, and exact-address routing
- Retry with replay if your endpoint is down
Priya Nair
2 min ago
priya@acmecorp.com → support@yourapp.com
Invoice #1847 — payment failed
Hi team, I've tried paying three times and keep getting an error. My card was charged once but the invoice still shows unpaid.
invoice_1847.pdf
48 KB · Adobe PDF
{ "id": "inb_8x9kzq3f", "from": "sarah@acme.com", "to": "support@you…", "subject": "Invoice #1847…", "attachments": [{ url: "…" }], "dkim": "pass", "spamScore": 0.2, "hmac": "sha256=ab4f…",}3 webhooks delivered
Zendesk
Ticket #49,201 created
Slack
#support notified
Your API
POST 200 OK
Signed JSON payload
Every message arrives as a verified POST with full envelope, headers, and attachments.
Flexible routing
Catch-all wildcard or per-address rules with regex matching, in priority order.
Attachment extraction
PDFs and docs extracted from MIME parts as signed download URLs valid 7 days.
Email infrastructure, minus the infrastructure
Add MX record
Add an MX record for your receiving domain pointing to mail.sendbound.com with priority 10.
Configure routes
Choose exact addresses, wildcards, or regex patterns and map each to a webhook URL.
Receive payloads
A signed POST arrives in ~2 seconds with parsed MIME, spam scoring, and attachments.
Process & reply
Trigger automations, create tickets, or reply via API to preserve the conversation thread.
Everything you need in one signed payload
Each webhook is a complete, signed representation of the incoming message. Start with the envelope and parsed headers; use clean text and HTML for your workflow, or retain raw MIME when your application needs it.
Attachments arrive as time-limited signed URLs — not opaque blobs. Spam score, DKIM, SPF, and sender-verification results let you build safe automation before a message reaches an agent or downstream service.
- Sender, recipients, subject, text, HTML, raw MIME
- Attachments as signed URLs (valid 7 days)
- DKIM / SPF / DMARC pass/fail per message
- Spam score (SpamAssassin-compatible)
- HMAC-SHA256 signature on every delivery
{ "id": "inb_8x9kzq3f", "from": "priya@acmecorp.com", "to": "support@yourapp.com", "subject": "Invoice #1847 — failed", "receivedAt": "2026-08-30T14:22:11Z", "messageId": "<01930af@mail.acme.com>", "text": "Hi, I was charged twice…", "html": "<p>Hi, I was charged…", "attachments": [{ url: "https://cdn.…" }], "spamScore": 0.2, "dkim": "pass", "spf": "pass", "dmarc": "pass", "replyTo": "priya@acmecorp.com", "inReplyTo": null, "hmac": "sha256=a3f8b2c1d9…",}Give every inbox a job
Route each address to a different workflow — support, sales, billing — without a single line of SMTP code.
Support ticket creation
Auto-create Zendesk or Linear tickets from support email, routing by subject, sender domain, and keyword priority.
Campaign reply tracking
Capture broadcast replies, match them to contacts by message ID, and trigger follow-up automations immediately.
Invoice & document processing
Extract PDF attachments as signed URLs, route them to your AI pipeline, and update your accounting system automatically.
~2s
Average processing latency
99.95%
Inbound delivery rate
50 MB
Max attachment size
DMARC
DKIM / SPF / DMARC verified per message
How Sendbound inbound compares
Parse, sign, route, and retry — without stitching together three different services.
| Feature | Sendbound | Mailgun | SendGrid | Cloudmailin |
|---|---|---|---|---|
| No mail server required | ✓ | ✓ | ✓ | ✓ |
| HMAC-signed webhook payloads | ✓ | ✓ | ✗ | ✗ |
| Structured JSON (sender, subject, text, HTML) | ✓ | ✓ | ✓ | ✓ |
| Attachment extraction as signed URLs | ✓ | ✗ | ✗ | ✓ |
| Wildcard + regex routing rules | ✓ | ✗ | ✗ | Partial |
| DKIM / SPF / DMARC verification per message | ✓ | Partial | ✗ | ✓ |
| Spam score included in payload | ✓ | ✗ | ✗ | ✗ |
| 72-hour retry with replay from dashboard | ✓ | ✗ | ✗ | ✗ |
| Catch-all + per-address routing in one account | ✓ | ✗ | Partial | ✓ |
| Included in your email plan (no extra seat) | ✓ | ✗ | ✗ | ✗ |
Inbound email questions
Do I need to run a mail server?
No. Create a receiving route in Webhooks, then add an MX record for that exact receiving domain pointing to mail.sendbound.com with priority 10. DNS changes may take time to propagate.
How long does the MX record change take?
DNS propagation usually completes within minutes, though your DNS provider may take up to 24 hours to publish a change.
What email volume can inbound handle?
Routes scale with your account and are designed for bursty transactional traffic as well as high-volume support inboxes.
Are attachments scanned for viruses?
Yes. Attachments are scanned before their signed URL is made available. Suspicious content is quarantined and reported.
Can I reply to inbound emails via API?
Yes. Use the original message ID and reply-to headers with the Sendbound sending API to preserve the conversation thread.
What happens if my webhook endpoint is down?
We retry signed deliveries with exponential backoff and retain the event for inspection and replay in your inbound dashboard.