Every booking, sent where you need it

It sends an HTTP POST to a URL you choose whenever one of its triggers happens. The body is JSON with the trigger's name, when it was sent and the booking's details.

Bookings created, rescheduled, canceled, requested, rejected, paid or reassigned, no-show updates, meetings starting and ending, recordings and transcripts, out of office entries and routing form submissions. A new webhook starts with every trigger picked except the instant meeting ones, and you remove what you don't need.

Give the webhook a secret. Every request then carries an X-Cal-Signature-256 header, an HMAC-SHA256 of the body made with that secret, which your endpoint can check before it trusts the data.

Yes. Turn on Custom Payload Template and write the body yourself with variables from the list under it, such as the title, the start time or the attendee's name. A template that is valid JSON goes out as JSON, anything else as form data.

Both. A webhook in Settings covers your own bookings or, through Create for, a team you manage. A webhook in an event type's Webhooks tab fires for that event type only.

Ping test sends a test request to the URL and shows the status that came back. Turn off Enable webhook to stop deliveries without deleting the webhook or its settings.