# React when a booking is made, moved or cancelled

> React when a booking is made, moved or cancelled: 1 companies fully do it, 13 with a limit, 14 carry the tag. Every listing in Calendars & scheduling with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/scheduling.watch-changes/
- Markdown: https://www.anchorterminal.com/niches/scheduling.watch-changes/index.md (~1,500 tokens)
- Slim: https://www.anchorterminal.com/niches/scheduling.watch-changes/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/scheduling.watch-changes/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 13 | 14 | 6 | 3 |

## What counts as done

Each create, change and cancel reaches the endpoint with enough data to act, or with a documented way to fetch it, and failed deliveries are retried on a published schedule with a visible signal when the subscription is disabled or expires.

How agents ask for it: tell me when someone books; when a slot is cancelled offer it to the waitlist; sync new bookings into the CRM; charge for the session once it is booked

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Aurinko Calendar API (Yoxel, Inc.)**: Calendar event subscriptions; retries at 1, 2, 4, 8 seconds capped at 10-minute intervals, and lifecycle events report error and active when a subscription breaks or recovers. Payload format documented per resource.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Acuity Scheduling API (Squarespace, Inc.)**: Scheduled, rescheduled, canceled and changed webhooks carry the id to fetch; retry table over 24 hours, disabled after 5 days with a status field on dynamic subscriptions. API and webhooks sit on Premium.
- **Apiroc Unified Calendar API (UTC Labs)**: calendar.event.changed webhooks through Svix, then fetch with syncToken. No retry schedule or expiry signal on Apiroc's pages, and no webhooks for iCloud or CalDAV.
- **Cal.com API v2 + MCP (Cal.com, Inc.)**: BOOKING_CREATED, RESCHEDULED and CANCELLED webhooks with versioned payloads and dedupe on payload.eventId. The guide says delivery can retry but publishes no schedule or disabled-subscription signal.
- **Calendly API + MCP (Calendly, LLC)**: Invitee created and canceled webhooks, on all plans per the help centre (acc-26 says paid). No retry schedule or disabled-subscription alert on readable pages; acc-25 asked and got no answer.
- **Cronofy API (Cronofy Limited)**: Push channels send change notifications to fetch with changes_since, plus profile_disconnected. Delivery is retried for 24 hours with no published intervals, then the channel closes with no notice.
- **Google Calendar API (Google LLC)**: events.watch channels carry an expiration and must be renewed; notifications have no body, so the change is fetched with a sync token (acc-45, Stack Overflow, which robots.txt closed to me). No retry schedule found on the push guide.
- **Microsoft Graph Calendar API (Microsoft Corporation)**: Subscriptions retry failed deliveries with exponential backoff for up to 4 hours and send reauthorizationRequired, subscriptionRemoved and missed lifecycle events. Subscriptions expire and need renewal, and slow endpoints can have notifications dropped.
- **Nylas Calendar and Scheduler API (Nylas, Inc.)**: Webhooks retry temporary failures up to 5 attempts and drop other errors; endpoints marked failing or failed trigger an email to listed addresses. Attempt intervals aren't stated.
- **Reclaim.ai (Reclaim.ai Inc.)**: Signed webhooks fire on Scheduling Link bookings, reschedules and cancels with meeting and attendee data, on Business and Enterprise only. No retry schedule or disabled-subscription signal published.
- **SavvyCal API + MCP (SavvyCal, Inc.)**: Signed event.created, event.rescheduled and event.canceled webhooks with event payloads. No retry schedule or disabled-subscription signal documented.
- **Truto Unified Calendar API (Yin Yang Inc.)**: Truto webhooks retry five times within five minutes on a published schedule; calendar changes arrive only where a vendor-webhook mapping exists, which the calendar pages don't confirm.
- **YouCanBookMe API (AI Software (Capacity) UK Ltd)**: Notification webhooks fire on booking, reschedule, cancel, reminders, follow-ups and no-shows with a payload built from shorthand codes. No retry schedule or failure signal is described, and webhooks need Professional or Teams.
- **Zoom Scheduler API (Zoom Communications, Inc.)**: Only scheduled_event_created and scheduled_event_canceled webhooks, no reschedule event. Zoom retries three times at 5, 20 and 60 minutes and disables a subscription after failed revalidation.

- not this job: Agenda Hero (Agenda Hero, Inc.): No webhook or push subscription is documented.
- not this job: Cozi Family Organizer (Cozi, Inc.): No webhooks or push; a subscribing calendar refreshes the feed on its own schedule.

## What stops agents finishing

- webhooks only on a paid plan
- subscription disabled silently after failed deliveries
- push channel expires and must be renewed

## Around it

Before: scheduling.book-slot. After: crm.log-activity, payment-platforms.charge, messaging.send-sms.

## Where this comes from

Weight 6 of 100 in Calendars & scheduling: 3 of 51 links; Calendly community and Stack Overflow; thin evidence

As data: https://www.anchorterminal.com/api/v1/use-cases/scheduling.watch-changes.json, or the MCP tool get_use_case with id scheduling.watch-changes. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
