Webhook Testing for Real-World Development

How developers use HookWatcher

From the first callback on localhost to the event that failed in production. Details for each feature are on the features page.

• Local webhook development

  Receive external webhooks on your machine without deploying your app. hwcli opens an encrypted connection out to HookWatcher, so there is no port forwarding, firewall change or server listening on the internet.

  $hwcli tunnel http 3000

  A public HTTPS URL for a local service. Callers get your app's live response, for OAuth callbacks, URL verification and demos. Requests are recorded only on your computer, in hwcli's local panel.

  $hwcli listen <hook> --to :3000/webhooks

  Webhooks captured by an endpoint are delivered to your local server with the same method, path, headers and raw body, and every delivery is recorded.

  • Expose localhost with a tunnel
  • Local webhook development
  • Install hwcli

• Webhook debugging

  See exactly what a provider sent: method, path, headers in their original order, query and the raw body, with a JSON tree and a hex view for binary payloads. Each request also shows the response your endpoint returned and, when forwarded, every delivery attempt.

  • Inspecting requests

• Webhook forwarding

  Relay every captured request to your own servers, several destinations per endpoint. Each delivery is retried automatically and keeps its status, response and latency, so a failing destination is easy to spot and send again.

  • Forwarding guide

• Payment integration testing

  Stripe and Razorpay webhooks are recognised and labelled with their event type. Check amounts and metadata, verify Stripe signatures against the captured bytes (paid plans), and replay a payment event against staging or your local code.

  • Debug Stripe webhooks locally

• Third-party API integrations

  Debug callbacks from GitHub, Shopify, Twilio, Slack, PayPal and other services before writing the handler. HookWatcher learns each event's structure and flags fields a provider adds, removes or retypes.

  • Schema drift detection

• Webhook replay

  Send a captured request again to reproduce a bug and confirm the fix, without asking the provider to resend it. Replay to a URL or to localhost with hwcli; edit the body, headers or query first on paid plans. The original capture never changes.

  • Replay a webhook locally

• Event-driven applications

  Providers retry, duplicate and reorder events. Replay Lab turns one real webhook into duplicate, delayed, out-of-order or burst deliveries so you can check your handler stays idempotent.

  • Replay Lab
  • Out-of-order webhooks

• Development and staging

  Forward a provider's test traffic to staging while keeping every request for comparison. Save a webhook that broke as a regression test and run it in CI with hwcli test run before you deploy.

  • Webhook tests in CI/CD