Resend email.delivered webhook payload example (Svix)

Resend · event: email.delivered · content type: application/json

This is a representative sample — fake IDs, real structure. To see a payload with your data, point the provider at a capture URL (button below).

See it live, not frozen

One click creates a free capture bin with this exact payload already in it — pretty-printed, headers inspectable, replayable to your own endpoint:

Then paste the bin's URL into Resend's webhook settings to capture a real delivery. No signup.

Headers

content-type: application/json
svix-id: msg_31kQ8mZv5TwXrLpNc2DyBhJfUae
svix-timestamp: 1788081322
svix-signature: v1,jB0EJZVan7X7fwuVjY6JJK7lPULrNM4k1Zr+jCIY1GY=

Body

{
  "type": "email.delivered",
  "created_at": "2026-08-30T09:15:22.481Z",
  "data": {
    "broadcast_id": "4f9a2c71-b3d8-45e6-9a02-7c1d5e8f3b60",
    "created_at": "2026-08-30T09:15:21.930Z",
    "email_id": "9d4e1f82-c5a7-4b39-8e61-0f2a6d7c3e95",
    "message_id": "<20260830091521.7a3b9c@mail.acme.dev>",
    "from": "Acme <onboarding@acme.dev>",
    "to": [
      "ada@example.com"
    ],
    "subject": "Welcome to Acme",
    "tags": {
      "category": "welcome"
    }
  }
}

Things that bite people

This example's signature actually verifies: Resend signs with Svix — base64 HMAC-SHA256 over id.timestamp.rawBody, key = the base64-decoded part after whsec_. Paste the body, the three svix-* values, and the secret whsec_SG9va2RlblJlc2VuZFNhbXBsZUtleTI2IQ== into the signature debugger (Svix scheme), or set the same scheme+secret on a capture bin for live ✓/✗ badges.
Verify the raw body — Resend's own docs warn that frameworks which parse the request as JSON and re-stringify it break verification. The signing secret is on the webhook details page and is also returned by the create/retrieve/list webhook API calls.
Every Resend event uses the same envelope: type, created_at (ISO 8601, unlike svix-timestamp which is epoch seconds), and event data nested under data. There are 20 event types across email.*, domain.*, contact.* and suppression.*.
Retry schedule (documented, exponential): immediately → 5s → 5m → 30m → 2h → 5h → 10h → 10h. A failing endpoint triggers an email notification and is eventually auto-disabled (with a second email); re-enable it from the Webhooks dashboard.
You can manually replay from the dashboard — both failed and succeeded messages, which is handy for re-driving a consumer after a bug fix.

Send it yourself

Reproduce this delivery against any endpoint (your handler, a bin, staging):

$ curl -X POST https://your-endpoint.example/hook \
  -H 'content-type: application/json' \
  -H 'svix-id: msg_31kQ8mZv5TwXrLpNc2DyBhJfUae' \
  -H 'svix-timestamp: 1788081322' \
  -H 'svix-signature: v1,jB0EJZVan7X7fwuVjY6JJK7lPULrNM4k1Zr+jCIY1GY=' \
 -d '{
  "type": "email.delivered",
  "created_at": "2026-08-30T09:15:22.481Z",
  "data": {
    "broadcast_id": "4f9a2c71-b3d8-45e6-9a02-7c1d5e8f3b60",
    "created_at": "2026-08-30T09:15:21.930Z",
    "email_id": "9d4e1f82-c5a7-4b39-8e61-0f2a6d7c3e95",
    "message_id": "<20260830091521.7a3b9c@mail.acme.dev>",
    "from": "Acme <onboarding@acme.dev>",
    "to": [
      "ada@example.com"
    ],
    "subject": "Welcome to Acme",
    "tags": {
      "category": "welcome"
    }
  }
}'

← All payload examples · Signature debugger · Docs