> 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.md).

# Developers

Start workflows from your server, book through a scheduling link, or connect an AI assistant to your workspace.

Start with [Authentication and workspaces](/developers/authentication.md). The examples use Distro endpoints and placeholder values. Use your Distro app URL as the base URL.

## Start here

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>Authentication</strong></td><td>Choose token scopes and the intended workspace.</td><td><a href="/developers/authentication.md">API authentication and workspaces</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2FaYIDeKw9xtV6qPqmQIr1%2Fdistro3-key.webp?alt=media">distro3-key.webp</a></td></tr><tr><td><strong>Start a workflow</strong></td><td>Send declared inputs from your trusted server.</td><td><a href="/developers/start-workflow.md">Start a workflow from your server</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2FPFXIrjam7bKgkiYYqgyt%2Fdistro3-api.webp?alt=media">distro3-api.webp</a></td></tr><tr><td><strong>Scheduling-link API</strong></td><td>Read a link, offer availability and create a booking.</td><td><a href="/developers/scheduling-links.md">Read a scheduling link and availability</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2F1ISmHDTp6o54IcOa6MDE%2Fdistro3-link.webp?alt=media">distro3-link.webp</a></td></tr><tr><td><strong>Distro MCP</strong></td><td>Connect an AI assistant to supported workspace tools.</td><td><a href="/developers/mcp.md">Connect an AI assistant with Distro MCP</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2Fg6FRzkkBbdvBnwpxC65g%2Fdistro3-ai.webp?alt=media">distro3-ai.webp</a></td></tr></tbody></table>

## All guides

* [API authentication and workspaces](/developers/authentication.md)
* [List API-triggered workflows](/developers/list-workflows.md)
* [Start a workflow from your server](/developers/start-workflow.md)
* [Read workflow progress and outcomes](/developers/workflow-progress.md)
* [Read event types and create a booking link](/developers/event-types.md)
* [Read a scheduling link and availability](/developers/scheduling-links.md)
* [Create a booking through a scheduling link](/developers/create-booking.md)
* [Single-use links and slot proposals](/developers/scheduling-artifacts.md)
* [Read and manage bookings with the API](/developers/manage-bookings.md)
* [API errors and safe retries](/developers/errors.md)
* [Connect an AI assistant with Distro MCP](/developers/mcp.md)
* [Distro MCP tool catalog](/developers/mcp-tools.md)
* [Public help MCP](/developers/help-mcp.md)
* [Useful requests for an AI assistant](/developers/assistant-recipes.md)
* [Look up and enrich a lead with the API](/developers/record-lookup.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.md?ask=<question>&goal=<user_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.