{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/scheduling.book-slot/",
    "json": "https://www.anchorterminal.com/niches/scheduling.book-slot/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/scheduling.book-slot/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/scheduling.book-slot/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 8 | 14 | 20 | 10 |\n\n## What counts as done\n\nA 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.\n\nHow 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\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.)**: 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.\n- **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.\n- **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).\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\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)**: 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.\n\n- not this job: Agenda Hero (Agenda Hero, Inc.): No booking pages or booking tool; it edits planner events only.\n- not this job: Apiroc Unified Calendar API (UTC Labs): No booking pages or booking endpoint; it reads and writes calendar events only.\n- not this job: Cozi Family Organizer (Cozi, Inc.): No booking pages or booking API.\n- not this job: Google Calendar API (Google LLC): No API for appointment schedules or booking pages (acc-33); only events can be written.\n- 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.\n- not this job: Reclaim.ai (Reclaim.ai Inc.): No booking endpoint or tool for an invitee is documented; Scheduling Links are hosted pages.\n- 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.\n\n## What stops agents finishing\n\n- no booking endpoint, only a hosted page (Google appointment schedules, Calendly before late 2025)\n- API access or booking only on a paid tier (Acuity Premium)\n- slot shown free but create refuses it with no reason\n- concurrent requests double-book the host\n\n## Around it\n\nBefore: scheduling.find-free-slot, voice-agents.take-call, crm.find-lead. After: crm.log-activity, messaging.send-sms, scheduling.watch-changes.\n\n## Where this comes from\n\nWeight 20 of 100 in Calendars \u0026 scheduling: 10 of 51 links; voice and chat receptionists on Cal.com and Calendly, and the long wait for Calendly's Scheduling API\n\nAs 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.\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": "Book a slot on someone's booking page for an invitee",
        "url": ""
      }
    ],
    "description": "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 \u0026 scheduling with the reason and a source.",
    "facts": null,
    "h1": "Book a slot on someone's booking page for an invitee",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/scheduling.book-slot/",
    "published": "",
    "section": "agents",
    "title": "Book a slot on someone's booking page for an invitee | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/scheduling.book-slot/"
  },
  "tokens": {
    "markdown": 1450,
    "slim": 330
  },
  "version": 1
}
