Your Resend webhook isn't firing. Here's what to check, in order
Resend's dashboard logs every webhook attempt it makes, which means "not firing" almost always means "delivered, but something after that silently failed" rather than Resend never sending anything at all. Check the delivery log first, not your code.
Last checked November 18, 2026.
Check these, in order
- The webhook delivery log in the Resend dashboard — if an attempt shows there with a non-2xx response code, Resend did send it; your endpoint rejected or errored on it.
- Whether the endpoint is subscribed to the right event types. Resend webhooks are opt-in per event (delivered, bounced, complained, opened, clicked, etc.) — an endpoint only receives the events it was configured for.
- Signature verification, done before or during your handler's actual logic — per Resend's own guidance, verification needs "the raw request body," since "the cryptographic signature is sensitive to even the slightest change." A framework that parses JSON before your verification code runs will fail every single request, which looks identical to "nothing arrives."
- Whether the endpoint is reachable at all from the public internet during local development — a webhook pointed at localhost with no tunnel (ngrok or similar) never gets a real request, and Resend has nothing to log as a failure because it has no route there.
Sources: Resend: Verify webhook requests
The signature check itself
Resend signs webhook payloads the same way Clerk does for its own webhooks: via Svix, reading the svix-id, svix-timestamp and svix-signature headers against a signing secret from the webhook's detail page. Resend states the security reason directly: "attackers can send fake HTTP POST requests to endpoints, pretending to be legitimate services" — verification is what tells those apart from real Resend traffic.
Sources: Resend: Verify webhook requests
Scribase Mail: signed webhooks, same account
Scribase Mail is a Resend-compatible API from the same vendor as the rest of a Scribase project, with its own verified domains and signed webhooks under one account — the raw-body signature-verification requirement above is the same discipline either way, since both use the same underlying signing approach.
Moving domains and broadcast history off Resend is an export today, not an automatic import: scribase-migrate pulls every sending domain's DNS records and every broadcast into a JSON file you re-create on Scribase Mail by hand.
npx --yes git+https://rithub.dev/caelum0x/scribase-migrate.git resend \
--api-key <re_...> --out resend-export.jsonSources: Scribase pricing
Questions people ask
How do I tell if Resend actually sent the webhook?
Check the webhook delivery log in the Resend dashboard — every attempt is recorded there with the response code your endpoint returned, even failed ones.
Why does my webhook work in a manual test but not for real events?
A manual test tool often sends a pre-formatted body that happens to parse cleanly; real traffic hits whatever body-parsing middleware sits in front of your handler in production, which is the more common place raw-body verification silently breaks.
Can I receive webhooks on localhost without a public URL?
No — Resend needs a real reachable URL to POST to; a tunnel tool (ngrok or similar) is the standard way to test webhooks against a local dev server.
Does Resend retry a failed webhook delivery?
Resend's dashboard lets you manually replay a specific past webhook event; this page does not state a specific automatic retry count since the fetched Resend documentation did not spell one out explicitly.