Email received
When emails arrive at your configured addresses, Inbound sends a webhook to your endpoint with the complete email data.
Webhook Payload Structure
We provide a fully typed webhook payload for you to use in your endpoints:
Example Payload
Webhook Security
Always verify webhook requests before processing them to prevent unauthorized access.
Verification Headers
Every webhook request includes security headers:
| Header | Description |
|---|---|
X-Webhook-Verification-Token | Unique verification token for your endpoint |
X-Endpoint-ID | ID of the endpoint that triggered this webhook |
X-Webhook-Event | Event type (e.g., email.received) |
X-Webhook-Timestamp | ISO 8601 timestamp of when the webhook was sent |
Verifying with the SDK
Downloading Attachments
Each attachment includes a downloadUrl for direct file access:
Note: Authentication via API key in the Authorization header is required to download attachments.
Authorizations
Your Inbound API key. Include it in the Authorization header as: Bearer
Body
Webhook payload sent when an email is received
Response
Webhook processed successfully