Troubleshoot webhooks
Find out why a webhook isn't arriving or is being rejected.
Imploy records the last delivery time, HTTP status and error code on each webhook, so start there.
Checklist
Is it enabled?
A disabled webhook sends nothing, and can't be tested.
Is the event selected?
The webhook only sends the events you chose. See Events.
Run a test
Use Test to send a sample. If the test arrives but real events don't, the problem is the event or the data, not the URL.
Read the last status
Look at the HTTP status and error code recorded on the webhook.
Common causes
| Symptom | Likely cause |
|---|---|
Test returns 401 or 403 | Your endpoint is rejecting the secret header, or your own auth is in front of it |
| Nothing arrives | The URL isn't public HTTPS on port 443, or it resolves to a private address |
| Timeouts | Your endpoint took more than 5 seconds, or the connection took more than 2. Reply first, process after |
| Redirect errors | Imploy doesn't follow redirects. Use the final URL |
| Signature fails | You parsed the body before checking it, or you're using the wrong secret. See Verify signatures |
| Missing events | Each delivery is attempted once. Reconcile with the API. See Keep a local copy up to date |
Saving the URL fails
The destination must follow the rules on Setting up. Imploy addresses and private ranges are refused, and the secret header name must be Authorization or start with X- (but not X-Imploy-).
Was this page helpful?