Open Webhooks in the dashboard first: every delivery shows the HTTP answer or the error we got. Most problems are one of the cases below.
Nothing is sent at all
The project has no Webhook URL. Add it in the project settings; we only send to the address saved on the project.
Deliveries fail
- Not a public https address. Plain http, local addresses and private networks are refused.
- Redirects. We do not follow them. Use the final address, including the right www and trailing slash.
- Blocked by a firewall or bot protection. Let our POST requests through on that path.
- Wrong answer. Only a 2xx status counts. Answer within a few seconds and do slow work afterwards.
- Your code crashes. Check your server's error log at the time of the failed delivery.
The signature does not match
- Use the webhook signing secret, not the API secret.
- Compute it over the raw body exactly as received, before any parsing.
- After making a new webhook secret, update your server.
Retries and alerts
Failed deliveries are retried for about two days. After three failures in a row on live events, the project owner gets one email; it re-arms after the next success.
Fixed it?
Press Resend on the failed deliveries under Webhooks, or Send test.ping on the project page to check the endpoint. Still stuck? Contact us through the contact page with the delivery ID.