Inbound
InboundClose the loop on two-way email.
Receive and process incoming email. Sendry verifies, parses, and stores inbound messages, then forwards them to your systems via signed webhooks, closing the loop on two-way email communication.
Why teams pick it
Verify first
Verify message authenticity before processing any payload.
Parse to structured records
Parse raw MIME into structured records with full metadata.
Forward to your webhook
Forward to your webhook endpoint when inbound config is active.
Signed payloads
Sign every webhook payload with your org-specific secret.
What you get
Everything ships on every plan unless noted otherwise.
- Receive inbound emails with automatic signature verification.
- Full MIME parsing: extract sender, recipients, subject, body, headers, and attachments.
- Attachment metadata stored with filename, content type, and size for each message.
- Query inbound messages via authenticated API with cursor-based pagination.
- Configure per-org webhook URLs to forward inbound events to your systems.
- Webhook payloads are HMAC-signed so you can verify authenticity on your end.
- Subscription confirmation handled automatically, no manual setup needed.
- Enable or disable inbound processing per organization through the config API.
- Inbound events show up in the dashboard alongside outbound activity.
POST your-webhook-url
1{2 "event": "inbound.received",3 "message_id": "msg_abc123",4 "from": "sender@example.com",5 "to": ["support@yourapp.com"],6 "subject": "Re: Order #4821",7 "text": "Hi, where is my order?",8 "html": "<p>Hi, where is my order?</p>",9 "received_at": "2025-09-01T14:32:00Z",10 "attachments": [11 { "filename": "receipt.pdf", "content_type": "application/pdf", "size": 42300 }12 ]13}Every inbound webhook is signed with an HMAC-SHA256 signature in the X-Sendry-Signature header. Verify it on your end before processing.
Works with the rest of the stack
Same keys, same dashboard, same delivery pipeline.
Complete the loop with outbound sending
Pair inbound events with REST or SMTP outbound workflows and handle replies in the same pipeline.