Calendly Webhook Tester — Test & Inspect Calendly Webhooks Online

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

What a Calendly webhook looks like

Calendly delivers webhooks as an HTTP POST with a application/json body. Calendly signs timestamp.body and returns it in Calendly-Webhook-Signature — capture a real invitee.created to see the payload.scheduled_event details your booking flow needs.

A typical invitee.created payload looks like this:

{
  "event": "invitee.created",
  "created_at": "2026-06-11T15:00:00Z",
  "payload": {
    "email": "[email protected]",
    "name": "Jon",
    "scheduled_event": {
      "name": "30 Minute Meeting",
      "start_time": "2026-06-12T16:00:00Z"
    }
  }
}

Common Calendly events you will want to test:

• invitee.created
• invitee.canceled

Verifying the Calendly signature

Calendly signs each request so you can prove it really came from Calendly. The signature travels in the Calendly-Webhook-Signature header and is HMAC-SHA256 over timestamp.body, using the signing key returned when you create the subscription. 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 Calendly events — without deploying — forward them straight to localhost with the Webhook Relay agent. The full walkthrough is here: Receive Calendly webhooks on localhost.

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

Test Calendly webhooks online in three steps

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