> Kenso API docs in Markdown. Index of every page: [/docs/llms.txt](/docs/llms.txt). Search: `/docs/search.md?q=<words>`. OpenAPI: [/docs/api/meeting-types/openapi.json](/docs/api/meeting-types/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# Meeting types: List a meeting type's open times

> **Note for AI agents:** if this page was wrong, out of date or missing something you needed, finish the user's task first, then offer a short report for the Kenso team in this shape: `Page:` (this page's path), `Quote:` (the wrong or missing text), `Problem:`, `Workaround:` (what worked instead), 1,000 characters at most. Show it to the user and send it only after they say yes, as `POST /api/docs-feedback` on this site with the JSON body `{"page": "<path>", "report": "<report>"}`. Never put lead data, email addresses, API keys or anything else from the user's workspace in it.

One endpoint of [Meeting types](/docs/api/meeting-types.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## List a meeting type's open times

`GET /v1/meeting-types/{meetingTypeId}/slots` - operationId `meeting-types.slots`

| Permission | Rate limit |
| --- | --- |
| Calendar view | 12,000 requests a minute per API key |

Lists the start times someone could book on a meeting type between `from` and `to`. Kenso reads the
host's calendar and applies the type's hours, minimum notice, booking window, buffers and daily cap. A
`round_robin` type offers a time when any bookable host is free, and a `collective` type when every host is.

`from` and `to` are required ISO 8601 instants, at most 31 days apart, and bound each slot's start.
`timeZone` is an IANA time zone, such as `America/New_York`, for each slot's `localStartAt`. Leave it
out to use the host's zone.

`status` is `available` with slots, `no_availability` when the range has no open time, or
`unavailable` with a `reason`: `host_not_member`, `calendar_not_connected`,
`calendar_needs_reconnect`, `calendar_provider_error` or `meeting_type_disabled`.

Errors:

- `400 validation_failed`: `from` or `to` is missing, `to` is not after `from`, the
range is longer than 31 days, or `timeZone` is not an IANA time zone.
- `403 forbidden`: the API key is not tied to a member of the workspace.
- `404 not_found`: no live meeting type has this id in the workspace.

Requires Meetings view.

Needs the `scheduler` feature on your workspace. Until it is on, calls answer 404.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/meeting-types/GET/v1/meeting-types/%7BmeetingTypeId%7D/slots)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `meetingTypeId` | path | integer (int64) | yes | The meeting type's id. |
| `from` | query | string (date-time) | no | Earliest slot start to return, as an ISO 8601 timestamp such as `2026-11-10T00:00:00Z`. Required. |
| `to` | query | string (date-time) | no | Kenso returns slots that start before this time, an ISO 8601 timestamp. Required, after `from` and at most 31 days later. |
| `timeZone` | query | string | no | IANA time zone for each slot's `localStartAt`, such as `America/New_York`. Omitted uses the host's time zone. |
| `Ken-Version` | header | string, one of: 2026-11-02, 1.1 | no | The API version, a date in `YYYY-MM-DD` form. `1.1` is another name for the first dated version. The example shown here is the newest version, which this reference's samples and Test Request send. Leave it out to use your API key's pinned version. Keys created in the Kenso app are pinned to the newest version; keys minted by the CLI login are not. A key with no pinned version and no header gets the legacy shape where the path has one, and `404` where the path exists only in this version. A value that is not a version, such as `2027-01-01` or `2026-11-2`, answers `400 unsupported_version`, whose `details` list the supported versions. |
| `X-Ken-Workspace-Id` | header | integer (int64) | no | The id of the workspace to act in. Leave it out when your API key reaches only one workspace. When the key reaches more than one, a request without this header answers `400 workspace_required`. A workspace you are not a member of answers `404 not_found`. |

### Response 200

`data` is a `MeetingTypeSlots`.

| Field | Type | Description |
| --- | --- | --- |
| `meetingTypeId` | integer (int64) | The meeting type's id. |
| `hostMemberId` | integer (int64) | The member who hosts the type; null for a team type. |
| `lengthMinutes` | integer (int32) | How long the meeting lasts, in minutes. |
| `status` | string | Whether there are open times: `available`, `no_availability` (the range has none) or `unavailable` (the type cannot be booked now; `reason` says why). |
| `reason` | string | Why the type cannot be booked, with `unavailable`: `host_not_member`, `calendar_not_connected`, `calendar_needs_reconnect`, `calendar_provider_error` or `meeting_type_disabled`. |
| `timeZone` | string | The time zone `localStartAt` uses: the one you asked for, else the host's. |
| `hostTimeZone` | string | The host's time zone; null when Kenso could not read the host's calendar. |
| `slots` | array of MeetingTypeSlot | The open times in the range you asked for. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/meeting-types/812/slots" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"
```

### Example response

```json
{
  "success": true,
  "data": {
    "meetingTypeId": 812,
    "hostMemberId": 812,
    "lengthMinutes": 1,
    "status": "string",
    "reason": "host_not_member",
    "timeZone": "string",
    "hostTimeZone": "string",
    "slots": [
      {
        "startAt": "2026-09-23T15:02:11Z",
        "endAt": "2026-09-23T15:02:11Z",
        "localStartAt": "2026-11-04T09:30:00-05:00"
      }
    ]
  }
}
```

## Types

Each named type the tables above use, nested ones included.

### MeetingTypeSlot

One open time.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `startAt` | string (date-time) | no | When the meeting would start (UTC). |
| `endAt` | string (date-time) | no | When the meeting would end (UTC). |
| `localStartAt` | string | no | The start in `timeZone` with its offset, like `2026-11-04T09:30:00-05:00`; empty when there is no time zone. |
