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

# Booking links: List your open single-use links

> **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 [Booking links](/docs/api/booking-links.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## List your open single-use links

`GET /v1/booking-links` - operationId `booking-links.list`

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

Lists the single-use links you made in this workspace that can still book: not used, not expired, and on a
meeting type that still exists. Newest first. A single-use link belongs to the member who made it, so you see only
your own, also with the `members` permission.

The items have no `url`: Kenso keeps only a hash of each link's token, so the URL is shown once, when you
create the link. Page with `limit`, from 1 to 200 (default 50), and the `cursor` from
`pagination.nextCursor`.

Errors:

- `400 validation_failed`: `limit` is out of range, or `cursor` is not valid.
- `403 forbidden`: the API key is not tied to a member of 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/booking-links/GET/v1/booking-links)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `limit` | query | integer (int32) | no | Number of links per page, from 1 to 200. Default 50. |
| `cursor` | query | string | no | The `nextCursor` from the previous page. Omit it for the first page. |
| `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 list of `BookingLinkSummary`. Each item has these fields. The response also carries `pagination`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | The link's id. |
| `kind` | string | The kind of link: always `single_use`. |
| `meetingTypeId` | integer (int64) | The meeting type the link books. |
| `personId` | integer (int64) | The person the link was made for; null when none was named. |
| `createdAt` | string (date-time) | When the link was made (UTC). |
| `expiresAt` | string (date-time) | When the link expires (UTC). |
| `availability` | AvailabilitySchedule | The link's own available times; null when it uses the meeting type's. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/booking-links?limit=50" \
  -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": [
    {
      "id": 812,
      "kind": "string",
      "meetingTypeId": 812,
      "personId": 812,
      "createdAt": "2026-09-23T15:02:11Z",
      "expiresAt": "2026-09-23T15:02:11Z",
      "availability": {
        "timeZone": "America/New_York",
        "weekly": {
          "monday": [
            {}
          ],
          "tuesday": [
            {}
          ],
          "wednesday": [
            {}
          ],
          "thursday": [
            {}
          ],
          "friday": [
            {}
          ],
          "saturday": [
            {}
          ],
          "sunday": [
            {}
          ]
        },
        "overrides": [
          {
            "date": "string",
            "ranges": []
          }
        ]
      }
    }
  ],
  "pagination": {
    "nextCursor": "eyJpZCI6ODE1fQ",
    "hasMore": true,
    "total": 1,
    "totalCount": 1,
    "isTotalCapped": true
  }
}
```

## Types

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

### AvailabilitySchedule

Weekly hours plus date overrides. When Kenso returns a schedule, every weekday is present (an empty list has no times) and the overrides are sorted by date. When you send one, a missing weekday has no times and missing `overrides` means none. Unknown fields are refused.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `timeZone` | string | no | The IANA time zone the hours are in, such as `America/New_York`. Null means each host's own time zone. |
| `weekly` | AvailabilityWeek | no | The hours for each day of the week. |
| `overrides` | array of AvailabilityOverride | no | Up to 100 dates, each once. Each date's ranges replace its weekday's hours; an empty list blocks the date. |

### AvailabilityWeek

The hours for each weekday: up to 6 ranges a day, as `HH:mm` at any whole minute, each starting before it ends, ending by `24:00` and not overlapping another. Ranges that touch are merged, and each day is kept in order.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `monday` | array of AvailabilityRange | no | Monday's hours. |
| `tuesday` | array of AvailabilityRange | no | Tuesday's hours. |
| `wednesday` | array of AvailabilityRange | no | Wednesday's hours. |
| `thursday` | array of AvailabilityRange | no | Thursday's hours. |
| `friday` | array of AvailabilityRange | no | Friday's hours. |
| `saturday` | array of AvailabilityRange | no | Saturday's hours. |
| `sunday` | array of AvailabilityRange | no | Sunday's hours. |

### AvailabilityOverride

One date's hours, used instead of its weekday's.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `date` | string | no | The date, as `YYYY-MM-DD`. |
| `ranges` | array of AvailabilityRange | no | The date's hours. An empty or missing list blocks the whole date. |

### AvailabilityRange

One range of a day.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `start` | string | no | When the range starts, as `HH:mm`. |
| `end` | string | no | When the range ends, as `HH:mm`; `24:00` is midnight at the end of the day. |
