Skip to content
Quickstart

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.

  1. 1
    Create an account

    Sign up and a workspace is created for you — no card required during beta.

  2. 2
    Create an endpoint

    Give it a name and a forwarding destination (the URL of the app that should receive the webhook).

  3. 3
    Copy the HookWatch URL

    Each endpoint has its own capture URL. This is what your provider will send to.

  4. 4
    Send a test webhook

    Use the curl below, or your provider’s "send test event" button, to fire one at the URL.

  5. 5
    Inspect the delivery

    Open the delivery to see the request, response, headers, and attempt history.

  6. 6
    Replay or retry if it fails

    Fix your app, then replay the captured delivery — no need to recreate the event by hand.

  7. 7
    Add alerts

    Route repeated failures to Slack or a webhook so you hear about incidents early.

Send a test webhook
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.

What you should see
  • Delivered a new row appears in the delivery list within a second or two.
  • open it to see the request body, response, and timing.
Provider examples
  • 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.
Common failures

When the row turns red.

500
Server error

Your handler threw. Fix the bug, then replay the delivery.

timeout
Too slow

Your handler took too long and the provider gave up. Replay after you speed it up.

401
Invalid signature

The signature header was missing or wrong. Check the signing secret.

429
Rate limited

Too many requests. HookWatch backs off and retries.

No delivery received

Double-check the endpoint URL was saved on the provider side, and that it points at HookWatch, not your app directly.

What to do next

Inspect, fix, replay, alert.

  1. 1 Inspect the failed delivery — read the response and headers.
  2. 2 Fix your app so the handler returns 2xx.
  3. 3 Replay the delivery to reprocess the event.
  4. 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.