Inbound

Receive and process incoming email. Sendr verifies, parses, and stores inbound messages, then forwards them to your systems via signed webhooks — closing the loop on two-way email communication.

Get started All features

How the pipeline works

Verify message authenticity before processing any payload.
Parse raw MIME into structured records with full metadata.
Forward to your webhook endpoint when inbound config is active.
Sign every webhook payload with your org-specific secret.

Capabilities

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.

Example webhook payload

POST your-webhook-urlJSON

{
  "event": "inbound.received",
  "message_id": "msg_abc123",
  "from": "sender@example.com",
  "to": ["support@yourapp.com"],
  "subject": "Re: Order #4821",
  "text": "Hi, where is my order?",
  "html": "<p>Hi, where is my order?</p>",
  "received_at": "2025-09-01T14:32:00Z",
  "attachments": [
    { "filename": "receipt.pdf", "content_type": "application/pdf", "size": 42300 }
  ]
}

Every inbound webhook is signed with an HMAC-SHA256 signature in the X-Sendr-Signature header. Verify it on your end before processing.

Complete the loop with outbound sending

Pair inbound events with REST or SMTP outbound workflows.

Email API SMTP Service