Sentry Webhook Tester — Test & Inspect Sentry Webhooks Online

If you are wiring up Sentry webhooks, the first question is always the same: what does Sentry actually send? The docs show an idealised payload, but the real request — its headers, its Sentry-Hook-Signature header, the exact JSON shape — is what your handler has to parse. A Sentry webhook tester gives you a public URL that captures those real requests so you can read every byte before you write any code.

Get a free Sentry webhook tester URL

The fastest way is our free Webhook Bin — a no-code webhook tester that gives you an instant public URL and stores every request that hits it, headers and body included. No signup, no deploy:

1. Open the Webhook Bin and copy the URL it generates for you.
2. In Settings → Developer Settings → Internal Integration → Webhooks, add a webhook endpoint and paste that URL.
3. Trigger an event (see below) and watch the request land in the bin in real time.

Because the bin keeps the full request, you can inspect the Sentry-Hook-Signature header, the Content-Type, and the complete payload — the three things you need to build and verify a handler.

What a Sentry webhook looks like

Sentry delivers webhooks as an HTTP POST with a application/json body. Sentry sends a Sentry-Hook-Resource header naming the resource (issue, error, comment) alongside the signature — capturing it tells you exactly which subscription delivered the payload.

A typical issue.created payload looks like this:

{
  "action": "created",
  "installation": {
    "uuid": "..."
  },
  "data": {
    "issue": {
      "id": "...",
      "title": "TypeError: undefined is not a function",
      "culprit": "app/main",
      "level": "error"
    }
  }
}

Common Sentry events you will want to test:

• issue.created
• issue.assigned
• error.created
• comment.created

Verifying the Sentry signature

Sentry signs each request so you can prove it really came from Sentry. The signature travels in the Sentry-Hook-Signature header and is HMAC-SHA256 of the raw request body, using your integration's client secret. Capture a real request first, then use our HMAC signature verifier and the verify a webhook signature guide to confirm your verification logic against a payload you can actually see.

From inspecting to receiving on localhost

A bin is perfect for seeing the payload. When you are ready to drive your local handler with real Sentry events — without deploying — forward them straight to localhost with the Webhook Relay agent. The full walkthrough is here: Receive Sentry webhooks on localhost.

That gives you a stable public URL that tunnels to your machine, so Sentry keeps delivering to the same endpoint while you iterate on localhost, no firewall changes or public IP required.

Test Sentry webhooks online in three steps

1. Capture — point Sentry at a Webhook Bin URL and inspect the real request.
2. Verify — confirm the Sentry-Hook-Signature header with the HMAC verifier.
3. Forward — when the shape is clear, receive Sentry webhooks on localhost and build your handler.

New to webhooks in general? Start with what is a webhook and how to test webhooks.

Ready to inspect your first Sentry event? Open a free Webhook Bin and paste the URL into Sentry.