{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/scheduling.reschedule-cancel/",
    "json": "https://www.anchorterminal.com/niches/scheduling.reschedule-cancel/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/scheduling.reschedule-cancel/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/scheduling.reschedule-cancel/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 | 35 | 10 | 5 |\n\n## What counts as done\n\nThe right event or booking moved or cancelled, with duration, attendees and conferencing kept, and only the chosen instance changed for a series, in no more than one lookup and one write.\n\nHow agents ask for it: move my 3pm to tomorrow; cancel my appointment next week; reschedule this caller's booking; skip just this week's stand-up\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Microsoft Graph Calendar API (Microsoft Corporation)**: calendarView over a time range finds the event or one occurrence; PATCH on that id moves it keeping attendees and conferencing, and cancel or delete removes it.\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.)**: GET /appointments filters by email and phone, PUT /appointments/:id/reschedule moves in place and /cancel cancels, both with noEmail. Gated on the Premium plan.\n- **Agenda Hero (Agenda Hero, Inc.)**: Changes or removes an event in one call, but a change to a repeating event applies to the whole series and one occurrence can't be edited; removals can't be undone.\n- **Apiroc Unified Calendar API (UTC Labs)**: PUT updates and DELETE removes an event; occurrences carry recurringEventId and their own ids for one instance. No attendee search and no notification control documented.\n- **Aurinko Calendar API (Yoxel, Inc.)**: PATCH with If-Match and DELETE, each with notifyAttendees; occurrences fetched by original start time. Lookup is by range or iCalUid, with no attendee email filter, and silent updates are Google-only.\n- **Cal.com API v2 + MCP (Cal.com, Inc.)**: POST /bookings/{uid}/reschedule moves in place (the duration bug acc-12 is closed) and /cancel cancels, with cancelSubsequentBookings for series. Bookings filter by attendeeEmail and name but not phone (acc-10, open); no email suppression.\n- **Calendly API + MCP (Calendly, LLC)**: Help and blog describe cancelling through the API and MCP and fetching a rescheduling link; no move-in-place call is described on pages I could read.\n- **Cronofy API (Cronofy Limited)**: Upserting the same event_id moves an event and leaves attendees unchanged if omitted; delete removes it. Events the app didn't create need Edit External Events, recurrence is alpha, and there is no lookup by attendee.\n- **Google Calendar API (Google LLC)**: patch, move and delete with sendUpdates, instances() for one occurrence, and q matching attendee emails. acc-04 saw single-instance edits fail in a community MCP (closed, fixed).\n- **Nylas Calendar and Scheduler API (Nylas, Inc.)**: PUT and DELETE on events carry notify_participants, with the same provider limits; recurring instances are documented separately. No lookup by attendee was found on the pages read.\n- **Reclaim.ai (Reclaim.ai Inc.)**: Moves and cancellations go through the same Preview Mode approval, and no tool for one instance of a series or lookup by attendee is documented.\n- **SavvyCal API + MCP (SavvyCal, Inc.)**: REST has only POST /events/{id}/cancel; the MCP's reschedule_booking moves a meeting but always notifies attendees. Events list supports q and attendance filters.\n- **Truto Unified Calendar API (Yin Yang Inc.)**: PATCH and DELETE on events for Google and Outlook. No attendee search or instance-scope parameter documented, and Cal.com and Calendly bookings can't be moved.\n- **Zoom Scheduler API (Zoom Communications, Inc.)**: PATCH /scheduler/events/{id} cancels, but there is no move operation, so a reschedule is cancel and rebook (a named blocker). Scheduled events list filters by from, to and event_type only.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **YouCanBookMe API (AI Software (Capacity) UK Ltd)**: Booking changes are mentioned in general terms only; no move or cancel call could be read.\n\n- not this job: Cozi Family Organizer (Cozi, Inc.): No API to change or cancel an event; feeds are read-only.\n\n## What stops agents finishing\n\n- no way to find the booking by the caller's phone or email, so the wrong one is changed\n- no move operation, only cancel and rebook (Zoom Scheduler)\n- recurring instance edits fail or hit the whole series\n\n## Around it\n\nBefore: voice-agents.take-call, scheduling.find-free-slot. After: messaging.send-sms, scheduling.watch-changes.\n\n## Where this comes from\n\nWeight 10 of 100 in Calendars \u0026 scheduling: 5 of 51 links; Cal.com API and n8n Google Calendar threads\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/scheduling.reschedule-cancel.json, or the MCP tool get_use_case with id scheduling.reschedule-cancel. 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": "Move or cancel an existing meeting or booking",
        "url": ""
      }
    ],
    "description": "Move or cancel an existing meeting or booking: 1 companies fully do it, 13 with a limit, 35 carry the tag. Every listing in Calendars \u0026 scheduling with the reason and a source.",
    "facts": null,
    "h1": "Move or cancel an existing meeting or booking",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/scheduling.reschedule-cancel/",
    "published": "",
    "section": "agents",
    "title": "Move or cancel an existing meeting or booking | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/scheduling.reschedule-cancel/"
  },
  "tokens": {
    "markdown": 1450,
    "slim": 380
  },
  "version": 1
}
