{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/scheduling.watch-changes/",
    "json": "https://www.anchorterminal.com/niches/scheduling.watch-changes/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/scheduling.watch-changes/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/scheduling.watch-changes/index.min.md"
  },
  "markdown": "One company's docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 1 | 13 | 14 | 6 | 3 |\n\n## What counts as done\n\nEach 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.\n\nHow 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\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **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.\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n\n- not this job: Agenda Hero (Agenda Hero, Inc.): No webhook or push subscription is documented.\n- not this job: Cozi Family Organizer (Cozi, Inc.): No webhooks or push; a subscribing calendar refreshes the feed on its own schedule.\n\n## What stops agents finishing\n\n- webhooks only on a paid plan\n- subscription disabled silently after failed deliveries\n- push channel expires and must be renewed\n\n## Around it\n\nBefore: scheduling.book-slot. After: crm.log-activity, payment-platforms.charge, messaging.send-sms.\n\n## Where this comes from\n\nWeight 6 of 100 in Calendars \u0026 scheduling: 3 of 51 links; Calendly community and Stack Overflow; thin evidence\n\nAs 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.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "React when a booking is made, moved or cancelled",
        "url": ""
      }
    ],
    "description": "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 \u0026 scheduling with the reason and a source.",
    "facts": null,
    "h1": "React when a booking is made, moved or cancelled",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/scheduling.watch-changes/",
    "published": "",
    "section": "agents",
    "title": "React when a booking is made, moved or cancelled | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/scheduling.watch-changes/"
  },
  "tokens": {
    "markdown": 1500,
    "slim": 380
  },
  "version": 1
}
