Webhook Payload & Signature Simulator
Choose a provider, a secret and a payload and get the exact body, headers, HMAC signature and a curl command to replay a signed webhook against your own endpoint. Nothing is sent from the browser.
Use the tool
Why this tool exists
Testing a webhook receiver is awkward. The provider's dashboard may only send real events, local servers are not reachable from the internet, and a hand-made request fails because the signature does not match the exact bytes of the body. Getting the timestamp format and header name right for each provider adds more room for mistakes.
This tool builds the request the way the chosen provider would, signs it with the secret you enter and prints a curl command you can run against localhost or a staging URL. Because it only prepares the request, nothing leaves your browser. Use a test secret rather than your live signing secret, since the command and headers contain what is needed to forge valid requests.
How to use it
- Choose a provider: GitHub, Stripe, Slack, Shopify or a generic HMAC scheme.
- Enter your test signing secret and the endpoint URL, plus the event name for GitHub or Shopify.
- Paste your JSON payload, or leave it blank to use a sample event.
- Copy the curl command and run it against your endpoint to test signature verification.
Frequently asked questions
Does the tool send the webhook?
No. It only builds the body, headers and signature, and prints a curl command. You run that command yourself, so you decide where the request goes and can inspect it first.
Why does my endpoint still reject the signature?
Most often the body was changed after signing, for example by a parser that re-serialises the JSON. Verify the signature against the raw request body, byte for byte, and check the timestamp tolerance.
Should I use my real signing secret?
Use a test secret. With the live secret, the generated command can produce valid-looking requests for your production endpoint, so keep it out of shared screens, tickets and shell history.