> 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/event-types.md).

# Read event types and create a booking link

Use the event-type API to choose an event and create a supported personal or team booking link.

## List and inspect

```http
GET /api/v1/accounts/WORKSPACE_ID/event_types
GET /api/v1/accounts/WORKSPACE_ID/event_types/EVENT_ID
```

Send your Bearer API token. These endpoints accept `scheduling_links:read` or `scheduling_links:write`.

The list returns `hosts_available` and `event_types`, including existing personal/team link choices. The detail route accepts a numeric event ID or its event key, and returns title, duration, hosts, questions and related configuration.

## Create a link

```http
POST /api/v1/accounts/WORKSPACE_ID/event_types/EVENT_ID/links
Content-Type: application/json
```

```json
{
  "hosts": [
    { "user_id": 101, "role": "must_attend", "lead": true },
    { "user_id": 102, "role": "optional" }
  ]
}
```

Required scope: `scheduling_links:write`. Use member IDs from your workspace, not the example IDs.

Supported host entries can identify a user or queue and use `must_attend` or `optional`. The acting member is added when absent. Hosts need usable calendars.

A queue resolves to a member at link creation using recent assignment counts. The resulting link pins that member; it does not run the queue's full routing-profile policy afresh for every booking.

The response includes a `link` with `id`, `kind` and `url`. Personal links can be reused for the acting member; other combinations create a team link.

When calling the separate scheduling-link routes, use `personal` for personal links and **`group` for a returned team link**. Continue with [Read link and availability](/developers/scheduling-links.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/event-types.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.