Clerk Webhook Tester — Test & Inspect Clerk Webhooks Online

If you are wiring up Clerk webhooks, the first question is always the same: what does Clerk actually send? The docs show an idealised payload, but the real request — its headers, its svix-signature header, the exact JSON shape — is what your handler has to parse. A Clerk 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 Clerk 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 Clerk Dashboard → Webhooks (powered by Svix), 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 svix-signature header, the Content-Type, and the complete payload — the three things you need to build and verify a handler.

What a Clerk webhook looks like

Clerk delivers webhooks as an HTTP POST with a application/json body. Clerk uses Svix under the hood, so the signature scheme (svix-id, svix-timestamp, svix-signature) is identical to many other Svix-powered providers — learn it once on a captured payload and it transfers everywhere.

A typical user.created payload looks like this:

{
  "type": "user.created",
  "object": "event",
  "data": {
    "id": "user_...",
    "email_addresses": [
      {
        "email_address": "[email protected]"
      }
    ],
    "first_name": "Jon"
  }
}

Common Clerk events you will want to test:

• user.created
• user.updated
• session.created
• organization.created

Verifying the Clerk signature

Clerk signs each request so you can prove it really came from Clerk. The signature travels in the svix-signature header and is base64 HMAC-SHA256 over svix-id.svix-timestamp.body, with svix-id and svix-timestamp headers, using the signing secret that starts with whsec_. 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 Clerk events — without deploying — forward them straight to localhost with the Webhook Relay agent. The full walkthrough is here: Receive Clerk webhooks on localhost.

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

Test Clerk webhooks online in three steps

1. Capture — point Clerk at a Webhook Bin URL and inspect the real request.
2. Verify — confirm the svix-signature header with the HMAC verifier.
3. Forward — when the shape is clear, receive Clerk 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 Clerk event? Open a free Webhook Bin and paste the URL into Clerk.