Use webhooks to automate booking lifecycle events in downstream systems like CRMs, Slack channels, and analytical pipelines.
Direct answer
Booking webhooks are HTTP notifications sent when scheduling events happen, such as a booking being created, rescheduled, or cancelled. Semiora webhooks let teams update CRMs, send internal alerts, sync analytics, and automate downstream systems after booking lifecycle changes.
booking.created — Fired when a new slot is confirmed.booking.cancelled — Fired when a meeting is removed by host or guest.booking.rescheduled — Fired when slot timing changes.{
"event": "booking.created",
"id": "evt_123",
"occurred_at": "2026-04-22T12:34:56Z",
"booking": { "id": "b_456", "start": "2026-04-25T14:00:00Z", "end": "2026-04-25T14:30:00Z" }
}id.Booking webhooks are HTTP notifications sent when scheduling events happen, such as a booking being created, rescheduled, or cancelled. Semiora webhooks help teams update CRMs, notify internal systems, and automate operations after booking changes.
Semiora webhook events include booking.created, booking.rescheduled, and booking.cancelled. Each event includes a payload envelope with an event ID, occurrence timestamp, and booking details.
Use the webhook event ID for idempotency, verify signatures with the workspace secret, and retry failed processing with backoff so downstream systems do not create duplicate records.
Implementation guide
Read the practical primer for signature checks, idempotency, retries, and dead-letter queues before you connect production systems.
Read Webhooks 101Automation guides
Use these guides to decide which booking events to send downstream and how to keep delivery reliable.
Model lifecycle events, retries, and idempotent downstream handlers.
Read guideCapture routing context before webhook events reach your internal systems.
Read guideUse booking events to coordinate reminders, follow-ups, and handoffs.
Read guideGlossary
Use these definitions to connect booking lifecycle events to scheduling and intake concepts.