Webhook signature tester
Runs only in your browser. Your data is not sent to our servers.
Calculate the HMAC signature of a webhook payload, or check the one you received. Presets fill in the format GitHub, Stripe, Shopify and Slack use.
A short guided tour of the fields, with example data.
Signature
What is signed
Bytes (hex)
About this tool
A webhook sender signs the request body with a shared secret, and the receiver calculates the same signature to check that the request is genuine. The signature only matches when the bytes are exactly the same.
- Use the raw body as it arrived. A body that has been parsed and written out again as JSON usually has other spaces or key order, and will not match.
- What is signed shows hidden characters:
␊is a line break (LF),␍a carriage return (CR),·a space at the end of a line and⟨BOM⟩a byte order mark. These are the most common reasons a signature does not match. - When the signature does not match, the tool also tries the payload without a trailing line break, with LF line breaks and without a BOM, and tells you if one of them matches.
- Stripe and Slack sign a timestamp together with the body. For Stripe the timestamp is read from the pasted
Stripe-Signatureheader.
The secret stays in your browser and is not stored. Use a test secret when you can.
Found a problem?
Tell us what went wrong. You decide whether your own work is included.
Licences
This tool uses no third-party libraries. It is our own code.