Event Types
Every webhook delivery carries an eventType string that identifies what happened. When creating a subscription with POST /api/v1alpha1/webhook-subscriptions, you specify which event types you want to receive. The v1alpha1 event catalog below lists everything currently in scope.
The eventType follows a stable naming convention. Most events use {domain}.{feature}.{action}, and new types are added by extending each level — e.g., a future Meeting AI recording event would be meetingai.recording.completed — so subscribers can filter by prefix.
Catalog
| Family | Purpose | Details |
|---|---|---|
| Scheduling | Meeting lifecycle across Smart Scheduler, personal scheduling, team scheduling — bookings, reschedules, cancellations. | Details ↓ |
| Developer | Endpoint validation. Fired automatically when a new subscription is created; not opt-in via the events array. | Details ↓ |
| Configuration | Change history for organization settings, company profile, service accounts, and domain list. Useful for compliance and audit. | Details ↓ |
Subscription behaviour
When you subscribe to an event type, every delivery to your endpoint carries that eventType string as both the value of body.eventType and the X-Cirrus-Event-Type HTTP header. The header lets you route the request without JSON-parsing.
Event types are the only thing that gate business-event delivery. There is no per-scope, per-user, or per-schedule filtering in v1alpha1 — a subscription for scheduling.smartscheduler.scheduled receives an event for every Smart Scheduler booking in your org.
Developer events are implicit. You don't put developer.webhook.test in the events array — Cirrus sends it automatically as part of the subscription-validation flow. Every subscription receives developer events regardless of what business events it opted into.
Reserved for future domains
Placement is reserved for these additional event families; each will be documented on its own page once available:
meetingai.*— Meeting AI recording, transcription, and summary events.replytracking.*— Reply-tracking events.buyersignals.*— Buyer-signals events.
Subscribers today receive meetingAi: null on scheduling event payloads and no meetingai.* events.