Overview
When emails arrive at your configured addresses, Inbound sends a webhook to your endpoint with the complete email data.Webhook Payload Structure
We have fully a complete typed webhook payload for you to use in your endpoints.Webhook Security
Verification Headers
Every webhook request includes security headers that you should verify:| 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 Webhooks with the SDK
The SDK provides a simple helper function to verify webhook requests:Complete Example with Verification
Here’s a complete example that combines webhook verification with payload processing:Attachment Downloads
Attachments include a
downloadUrl field that provides direct access to download the file using your API key for authentication.Downloading Attachments
Each attachment in the webhook payload includes adownloadUrl that you can use to download the file:
The download URL follows the format:
https://inbound.new/api/v2/attachments/{emailId}/{filename}Authentication via API key in the Authorization header is required to download attachments.