Skip to content
Docs navigationBrowse tools →

Tool docs

Webhook Signature Verifier

Recompute HMAC webhook signatures for GitHub, Shopify, Stripe, and Slack in the browser, and see exactly why a signature doesn't match. This guide explains what each platform signs, what the diagnostics check for, and what the tool does not prove.

Tool

Overview

01

Webhook Signature Verifier

Use this tool when a webhook handler rejects a signature and you need to find out why. Pick the platform, paste the raw request body, the signing secret, and the signature header value — Birdor recomputes the HMAC using the exact message format that platform signs (raw body, or timestamp-prefixed body for Stripe and Slack) and tells you whether it matches.

Guide

Common usage patterns

01

Verify a signature, or debug a mismatch

  • Select the platform so the message format (raw body vs. timestamp-prefixed body) and expected prefix/encoding are correct.
  • Paste the exact raw request body — copy it before any JSON.parse or pretty-printing touches it.
  • For Stripe, paste the whole Stripe-Signature header and the timestamp is extracted automatically.
  • For Slack, paste the X-Slack-Request-Timestamp value into the Timestamp field.
  • When the result says Mismatch, read the Diagnostics list before assuming the secret is wrong.

Guide

Edge cases & common pitfalls

01

Raw bytes, prefixes, and replay windows

  • A framework that parses the body into JSON and hands you the parsed object instead of the raw bytes will always fail signature checks, even with the correct secret.
  • GitHub and Shopify sign the raw body only; Stripe and Slack fold a timestamp into the signed string, so the same payload produces a different signature on each platform.
  • Stripe and Slack expect the timestamp within roughly 5 minutes of "now"; an old saved test payload shows as outside the tolerance window, which is expected when testing, not a bug.
  • GitHub, Stripe, and Slack signatures are hex; Shopify's is Base64 — pasting one where the other is expected produces a mismatch that looks like a secret problem but isn't.

Internals

How it works internally

01

Web Crypto first, local-only execution

Birdor recomputes each signature with the browser's Web Crypto HMAC implementation from the payload, secret, and (where applicable) timestamp you provide, then compares it against the pasted value. Nothing is uploaded — the secret and payload stay in the page.