Webhook signature generator (HMAC)
Compute the signature a provider would send for a body and secret, and see exactly what string is signed. Runs entirely in your browser: nothing you paste is uploaded, stored or logged.
By the HookWatcher team · Updated
Use a test secret. It stays in this tab.
What each format signs
| Format | Signed string | Algorithm and encoding |
|---|---|---|
| GitHub | body | HMAC-SHA256, hex, prefixed sha256= |
| Stripe | {t}.{body} | HMAC-SHA256, hex, in t=…,v1=… |
| Shopify | body | HMAC-SHA256, Base64 |
| Slack | v0:{timestamp}:{body} | HMAC-SHA256, hex, prefixed v0= |
| Razorpay | body | HMAC-SHA256, hex |
| Standard Webhooks | {id}.{timestamp}.{body} | HMAC-SHA256 with the Base64-decoded secret, Base64, prefixed v1, |
The default example uses GitHub's published test values (secret It's a Secret to Everybody, body Hello, World!), so you can check the result against GitHub's documentation: 757107ea…3e17.
If your handler's signature doesn't match
- Paste the raw body exactly as received. A body copied from a pretty-printed log, or re-serialized by your framework, has different bytes.
- Watch for a trailing newline. Many editors and
echoadd one. - Check you're using the secret for this endpoint and mode (test vs live).
- Compare encodings: hex and Base64 of the same digest look nothing alike.
More in signature mismatches. HookWatcher can also re-sign replayed deliveries with your stored secret and send invalid or missing signatures on purpose: see testing signature validation.
- GitHub Docs: Validating webhook deliveries
- Stripe Docs: Verify webhook signatures manually
- Shopify Docs: Verify webhooks
- Slack API: Verifying requests from Slack
- Razorpay Docs: Validate webhooks
- Standard Webhooks specification
Test signatures against real deliveries
Capture a provider's webhook with a free endpoint, then replay it to your handler with the original signature intact.
Get a free webhook URL No account or card needed. Want to keep it? Create a free account