Why did the signature fail?
Most webhook bugs are signature failures, and most libraries only tell you that it failed. SlingHook’s signature debugger checks each common cause and tells you which one it is:
- The wrong kind of secret, such as an API key instead of Stripe’s
whsec_…signing secret, or stray whitespace around it. - A timestamp outside the provider’s tolerance, or a request being replayed.
- A body your framework parsed and re-encoded before checking it, so the bytes no longer match what was signed.
- A body that was cut off in transit.
You can try another secret against the captured request without saving it.
Inspect the real request
Point the provider at your SlingHook URL and every request streams into your browser as it arrives: method, headers, query string and the body as JSON, form data or XML. You see exactly what was sent, not what your framework turned it into.
Debug in your own code
Run slinghook listen to send each webhook to the server on your machine, so you can step through it with your own debugger and breakpoints. No tunnel and no open ports. The quickstart has the details.
Fix it and replay
Once you change your handler, replay the same request instead of creating a new order or payment in the provider. Replayed requests carry an X-Webhook-Replay: true header. For flows that span several events, record them once and replay the whole sequence with its original timing to see where it breaks.
Turn the payload into code
Generate a typed model of a real payload (TypeScript, Python, PHP or Go), a fixture file, or a Jest, Vitest, pytest or Laravel test that sends the event to your handler.
Free plan
The signature debugger, live feed, replay and CLI relay are all on the free plan, with 3 endpoints, 1,000 events a month and 24 hours of history. See all plans.