Glossary definition

What are booking webhooks?

Booking webhooks are HTTP notifications sent when scheduling events happen, such as a booking being created, rescheduled, or cancelled. They help teams sync booking data with CRMs, internal tools, analytics systems, and notification workflows.

Example workflow

When a meeting is rescheduled, a booking.rescheduled webhook updates the CRM activity, notifies the account owner, and logs the new meeting time in an internal system.

How it works

A booking lifecycle event happens, such as booking.created or booking.cancelled.
The platform sends an HTTP request to the configured webhook endpoint.
The receiving system verifies the signature and stores the event ID for idempotency.
The receiving system updates downstream tools, sends alerts, or starts automation.

When to use it

You need to update a CRM or database after bookings change.
You want Slack, email, or internal alerts for booking lifecycle events.
You need reliable automation that does not depend on manual exports.

Frequently asked questions

Which booking webhook events should teams start with?

Start with booking.created, booking.rescheduled, and booking.cancelled. These cover the core scheduling lifecycle for most operational systems.

How do you make booking webhooks reliable?

Verify signatures, store event IDs for idempotency, retry temporary failures with backoff, and log failed deliveries for operations review.

Next step

See how Semiora supports booking webhooks.

Open related feature