> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/developers/create-booking.md). # Create a booking through a scheduling link Fetch [Link details and availability](/developers/scheduling-links.md), then submit the selected slot token. ```http POST /api/v1/accounts/WORKSPACE_ID/scheduling_links/KIND/LINK_ID/bookings Authorization: Bearer YOUR_DISTRO_API_TOKEN Content-Type: application/json ``` ```json { "slot_token": "TOKEN_FROM_AVAILABILITY", "time_zone": "Europe/London", "invitee": { "name": "Alex Example", "email": "alex@example.com" }, "guests": [], "answers": [], "notes": "Discuss the routing rollout", "idempotency_key": "booking-000123" } ``` Required scope: `scheduling_links:write`. Keep the private token on your server. ## Questions and location `answers` is an array of `{ "question_id": ID, "value": VALUE }` entries. Use IDs, types and required flags from link details. A value can be an array for the applicable question type. For an event requiring location selection or a guest phone, provide the supported `meeting_location_id` and `guest_phone`. Additional guests use name/email objects. ## Response A new booking returns HTTP 201 with `booking` and `replayed: false`. The booking includes UUID, status, title, start/end, timezone, meeting URL and confirmation URL. A replay with the same valid idempotency request returns HTTP 200 and `replayed: true`. Retain the booking UUID for management. If the slot is no longer usable, fetch fresh availability and ask the guest to choose again. Do not silently change their selected time. Inspect the final response and delivered invitation before presenting a confirmed meeting. Request acceptance and a calendar provider's final delivery are distinct evidence when troubleshooting. See [Manage bookings](/developers/manage-bookings.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/developers/create-booking.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.