Debug your first webhook in minutes.
Seven steps from sign-up to a replayed delivery. No code changes to your handler — you only repoint the webhook URL.
- 1Create an account
Sign up and a workspace is created for you — no card required during beta.
- 2Create an endpoint
Give it a name and a forwarding destination (the URL of the app that should receive the webhook).
- 3Copy the HookWatch URL
Each endpoint has its own capture URL. This is what your provider will send to.
- 4Send a test webhook
Use the curl below, or your provider’s "send test event" button, to fire one at the URL.
- 5Inspect the delivery
Open the delivery to see the request, response, headers, and attempt history.
- 6Replay or retry if it fails
Fix your app, then replay the captured delivery — no need to recreate the event by hand.
- 7Add alerts
Route repeated failures to Slack or a webhook so you hear about incidents early.
curl -X POST "https://hooks.hookwatch.dev/your-endpoint" \
-H "Content-Type: application/json" \
-d '{"type":"invoice.paid","id":"evt_demo_123"}'The curl above is a simplified, unsigned example. For endpoints with signature verification turned on, use the dashboard's test webhook button, which signs the request for you.
- Delivered a new row appears in the delivery list within a second or two.
- open it to see the request body, response, and timing.
- Stripe invoice.paid — Add the HookWatch endpoint URL under Developers → Webhooks.
- GitHub push — Add it as a repo or app webhook URL under Settings → Webhooks.
- Telegram update — Set it with the Bot API’s setWebhook call.
When the row turns red.
Your handler threw. Fix the bug, then replay the delivery.
Your handler took too long and the provider gave up. Replay after you speed it up.
The signature header was missing or wrong. Check the signing secret.
Too many requests. HookWatch backs off and retries.
Double-check the endpoint URL was saved on the provider side, and that it points at HookWatch, not your app directly.
Inspect, fix, replay, alert.
- 1 Inspect the failed delivery — read the response and headers.
- 2 Fix your app so the handler returns 2xx.
- 3 Replay the delivery to reprocess the event.
- 4 Set an alert so the next streak of failures reaches you.
Create your first endpoint.
Sign up, send a webhook, and replay a failure — free during beta.