# Book a slot on someone's booking page for an invitee

> Book a slot on someone's booking page for an invitee: 0 companies fully do it, 8 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.book-slot/
- Markdown: https://www.anchorterminal.com/niches/scheduling.book-slot/index.md (~1,450 tokens)
- Slim: https://www.anchorterminal.com/niches/scheduling.book-slot/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/scheduling.book-slot/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

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 8 | 14 | 20 | 10 |

## What counts as done

A confirmed booking with an id, the host's calendar updated and the invitee confirmation sent or suppressed as asked, from one create call after a slot lookup. A slot taken in the meantime returns a distinct conflict error, not a generic failure.

How agents ask for it: book me with Dr Patel on Thursday; schedule a demo on our Calendly for this lead; take the booking during the call; book the 2pm slot for this customer

## 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.)**: POST /appointments validates the slot as a client and returns 400 not_available on a taken time; noEmail=true suppresses confirmations. API access needs Premium, which blocked acc-36, and no lock under concurrent creates is documented.
- **Aurinko Calendar API (Yoxel, Inc.)**: POST /book/.../meeting books a returned slot and invites the email; reserveForMinutes holds it, with confirm and cancel calls. The spec lists only 200, 401 and default responses, so no distinct conflict error is documented.
- **Cal.com API v2 + MCP (Cal.com, Inc.)**: POST /v2/bookings after a slot lookup, with /v2/slots/reservations to hold a slot. No 409 or conflict code in the spec, concurrent creates both succeed (acc-11, open), and free slots were refused via cal-mcp (acc-05).
- **Calendly API + MCP (Calendly, LLC)**: The help centre says the Scheduling API books on all plans, Free included. acc-24 had every start time refused as filled with no reply; parameters and conflict codes were not read.
- **Cronofy API (Cronofy Limited)**: The MCP server and Scheduling Requests find a time and book it; over REST an agent queries availability then upserts the event. No re-check on write or conflict error is documented.
- **Nylas Calendar and Scheduler API (Nylas, Inc.)**: POST /v3/scheduling/bookings re-checks the slot and rejects the booking if taken, with disable_emails for confirmations. The rejection's error code isn't named on the page read, and no idempotency key exists.
- **SavvyCal API + MCP (SavvyCal, Inc.)**: POST /v1/links/{id}/events books a returned slot with name, email, phone and time_zone and refuses other times with 422, a generic validation code. No idempotency key or email suppression; booking needs a paid plan.
- **Zoom Scheduler API (Zoom Communications, Inc.)**: POST /scheduler/attendee books a spot with booker name, email and phone and returns the event. A taken slot returns the same 400 as an invalid body, and no idempotency key is documented.

## Couldn't check

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

- **YouCanBookMe API (AI Software (Capacity) UK Ltd)**: The help centre says the API manipulates bookings made through the system; whether it creates one, and with what conflict handling, is in the unreadable reference.

- not this job: Agenda Hero (Agenda Hero, Inc.): No booking pages or booking tool; it edits planner events only.
- not this job: Apiroc Unified Calendar API (UTC Labs): No booking pages or booking endpoint; it reads and writes calendar events only.
- not this job: Cozi Family Organizer (Cozi, Inc.): No booking pages or booking API.
- not this job: Google Calendar API (Google LLC): No API for appointment schedules or booking pages (acc-33); only events can be written.
- not this job: Microsoft Graph Calendar API (Microsoft Corporation): The calendar endpoints have no booking pages or booking call; Microsoft Bookings is a separate API this listing doesn't cover.
- not this job: Reclaim.ai (Reclaim.ai Inc.): No booking endpoint or tool for an invitee is documented; Scheduling Links are hosted pages.
- not this job: Truto Unified Calendar API (Yin Yang Inc.): Event create supports Google and Outlook only, and there is no booking call for Cal.com or Calendly event types; their event types are read-only.

## What stops agents finishing

- no booking endpoint, only a hosted page (Google appointment schedules, Calendly before late 2025)
- API access or booking only on a paid tier (Acuity Premium)
- slot shown free but create refuses it with no reason
- concurrent requests double-book the host

## Around it

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

## Where this comes from

Weight 20 of 100 in Calendars & scheduling: 10 of 51 links; voice and chat receptionists on Cal.com and Calendly, and the long wait for Calendly's Scheduling API

As data: https://www.anchorterminal.com/api/v1/use-cases/scheduling.book-slot.json, or the MCP tool get_use_case with id scheduling.book-slot. 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
