# Move or cancel an existing meeting or booking

> 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 & scheduling with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/scheduling.reschedule-cancel/
- Markdown: https://www.anchorterminal.com/niches/scheduling.reschedule-cancel/index.md (~1,450 tokens)
- Slim: https://www.anchorterminal.com/niches/scheduling.reschedule-cancel/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/scheduling.reschedule-cancel/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 | 35 | 10 | 5 |

## What counts as done

The 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.

How 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

## Does the job

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

- **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.

## 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.)**: 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.
- **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.
- **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.
- **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.
- **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.
- **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.
- **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.
- **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).
- **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.
- **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.
- **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.
- **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.
- **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.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **YouCanBookMe API (AI Software (Capacity) UK Ltd)**: Booking changes are mentioned in general terms only; no move or cancel call could be read.

- not this job: Cozi Family Organizer (Cozi, Inc.): No API to change or cancel an event; feeds are read-only.

## What stops agents finishing

- no way to find the booking by the caller's phone or email, so the wrong one is changed
- no move operation, only cancel and rebook (Zoom Scheduler)
- recurring instance edits fail or hit the whole series

## Around it

Before: voice-agents.take-call, scheduling.find-free-slot. After: messaging.send-sms, scheduling.watch-changes.

## Where this comes from

Weight 10 of 100 in Calendars & scheduling: 5 of 51 links; Cal.com API and n8n Google Calendar threads

As 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.

---

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