Webhook not received: why events never arrive

When a webhook never arrives, the cause is upstream of your handler — the request was never sent to you, never reached you, or was sent somewhere else. There is no failed delivery to read, which is exactly what makes it hard.

Work through the usual causes

• Wrong URL — a typo, a trailing slash, an old/staging URL, or HTTP vs HTTPS on the provider side.
• Event not subscribed — the endpoint isn’t subscribed to that event type, or you’re in the wrong mode (test vs live).
• Blocked at the edge — a firewall, WAF, or IP allow-list rejects the provider before your app sees it.
• Retry window exhausted — earlier failures (500/timeout) burned through the provider’s retries, so it stopped sending.

Confirm where it stops

Point a HookWatch capture URL at the endpoint and send a test event (or use the webhook tester to fire one yourself). If it lands in HookWatch, the provider and network are fine and the problem is downstream in your app; if it doesn’t, the issue is the URL, the subscription, or the edge. The quickstart walks through this.