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

# Bookings: Reassign a former member's bookings

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

## Reassign a former member's bookings

`POST /v1/bookings/bulk-reassign` - operationId `bookings.bulk-reassign`

| Permission | Rate limit |
| --- | --- |
| Calendar view | 4,800 requests a minute per API key |

Moves the upcoming bookings of a member who left the workspace to other members, 20 bookings per call. Call it
again with `nextCursor` as `cursor` while `hasMore` is true.

Send `hostMemberId`, the id of the member who left. For each booking, Kenso looks for a member who is free at
the same time, in this order: the account owner, the campaign's sender, the meeting type's other hosts, then any
member with a personal meeting type that is turned on. The new host's calendar sends the booker a new invite, and
Kenso then removes the old event from the former member's calendar. Kenso does not move a collective meeting:
cancel it, or rebook it by hand.

The response counts `succeeded` and `failed` and has one entry in `results` per booking, in start
order. A booking that ends with `host_busy` or `calendar_write_failed` is unchanged, so the next call
with the same `cursor` tries it again.

Errors:

- `400 validation_failed`: `hostMemberId` is missing, or `cursor` is not valid.
- `403 forbidden`: you need the `members` permission.
- `403 permission_denied`: Client seats cannot reassign bookings.
- `409 invalid_state`: the person is still a member of the workspace. Remove them first.

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/bookings/POST/v1/bookings/bulk-reassign)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `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`. |

### Request body

`application/json`, optional.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `hostMemberId` | integer (int64) | yes | Required. The former member whose upcoming bookings to handle. |
| `cursor` | string | no | The `nextCursor` from the previous call; leave it out on the first call. |

### Response 200

`data` is a `BookingLeaverResult`.

| Field | Type | Description |
| --- | --- | --- |
| `succeeded` | integer (int32) | How many bookings this call reassigned or cancelled with nothing left to do. |
| `failed` | integer (int32) | How many bookings this call could not handle, or cancelled without telling the booker. Each has its `error` in `results`. |
| `results` | array of BookingLeaverItem | The result for each booking in this call. |
| `hasMore` | boolean | True when more upcoming bookings are left: call again with `nextCursor`. |
| `nextCursor` | string | The cursor for the next call; null when nothing is left. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/bookings/bulk-reassign" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID" \
  -H "Content-Type: application/json" \
  -d '{
  "hostMemberId": 812,
  "cursor": "eyJpZCI6ODE1fQ"
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "succeeded": 1,
    "failed": 1,
    "results": [
      {
        "bookingId": 812,
        "status": "reassigned",
        "startAt": "2026-09-23T15:02:11Z",
        "newBookingId": 812,
        "hostMemberId": 812,
        "calendarEventRemoved": true,
        "error": "string",
        "errorCode": "string"
      }
    ],
    "hasMore": true,
    "nextCursor": "eyJpZCI6ODE1fQ"
  }
}
```

## Types

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

### BookingLeaverItem

What happened to one booking in a bulk reassign or cancel.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `bookingId` | integer (int64) | yes | The booking's id. |
| `status` | string | yes | What happened: `reassigned`, `cancelled`, `already_handled`, `no_free_member`, `host_busy`, `calendar_write_failed` or `failed`. |
| `startAt` | string (date-time) | no | When the booking starts (UTC). |
| `newBookingId` | integer (int64) | no | For `reassigned`: the id of the new booking that replaces this one. |
| `hostMemberId` | integer (int64) | no | For `reassigned`: the member who hosts the meeting now. |
| `calendarEventRemoved` | boolean | no | For `reassigned` or `cancelled`: whether the old calendar event was removed, which tells the booker. False means the invite stays on the former member's calendar; a cancel then also has `errorCode` `booker_not_told`. |
| `error` | string | no | What went wrong, in words a person can act on. Set on a failure, and on a cancelled booking with `errorCode` `booker_not_told`. |
| `errorCode` | string | no | What a person still has to do when the status alone does not say it. Today only `booker_not_told`: the booking is cancelled, but its invite stayed on the former member's calendar, so tell the booker yourself. |
