> 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/scheduling-links.md). # Read a scheduling link and availability The scheduling-link API books through an existing personal or group link. It is separate from workflow Show Scheduler. ## Read the link ```http GET /api/v1/accounts/WORKSPACE_ID/scheduling_links/KIND/LINK_ID Authorization: Bearer YOUR_DISTRO_API_TOKEN ``` `KIND` is `personal` or `group`; `LINK_ID` is the numeric link ID. Normalize a team link returned by the event-link API to `group` for this route. Required scope: `scheduling_links:read`. The acting member must be permitted to use the link; a public guest URL does not grant this private API permission. The `scheduling_link` object includes title, duration, location options, booking window, minimum notice, hosts, questions, prefill and capabilities. Use the returned question IDs and requirements in your booking UI. ## Request times ```http GET /api/v1/accounts/WORKSPACE_ID/scheduling_links/KIND/LINK_ID/availability?time_zone=Europe%2FLondon&start_at=2026-11-02T00%3A00%3A00Z&end_at=2026-11-09T00%3A00%3A00Z ``` Replace the example dates with the desired future range. Use ISO 8601 times and a valid timezone. The response's `availability` includes the range, timezone, `slots` and supported `calendar_intervals`. Each slot contains `start_at`, `end_at` and **`slot_token`**. Use the exact returned token to book. Do not construct a token from a timestamp. Calendar intervals expose supported busy/unavailable presentation, not the complete private contents of host calendars. A slot is an offer of current availability, not a permanent hold. Distro rechecks the booking. Continue with [Create a booking](/developers/create-booking.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/scheduling-links.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.