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

# Saved list invites

> **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.

A saved-list invite is the link Kenso emails when a workspace shares one of its saved lists with an email address. Any signed-in person who holds the token can read what the invite shares, even before they have a workspace. Accepting the invite adds the list, read-only, to the workspace you call in, and only the invited email address can accept it.

Prospecting data. 2 endpoints under `https://api.ken.so`. Every request sends `Authorization: Bearer <your API key>` and `Ken-Version: 2026-11-02`: see [Authentication](/docs/authentication.md), [Workspaces](/docs/workspaces.md) and [Errors](/docs/errors.md). OpenAPI for this resource only: [/docs/api/saved-list-invites/openapi.json](/docs/api/saved-list-invites/openapi.json).

- `GET /v1/saved-list-invites/{token}` - Get a saved list invite (`saved-list-invites.get`): [/docs/api/saved-list-invites/get.md](/docs/api/saved-list-invites/get.md)
- `POST /v1/saved-list-invites/{token}/accept` - Accept a saved list invite (`saved-list-invites.accept`): [/docs/api/saved-list-invites/accept.md](/docs/api/saved-list-invites/accept.md)

## Get a saved list invite

`GET /v1/saved-list-invites/{token}` - operationId `saved-list-invites.get`

| Permission | Rate limit |
| --- | --- |
| Any signed-in caller | 12,000 requests a minute per API key |

Returns what an invite link shares, so the invited person can decide before accepting: the list's name, kind and
member count, the name of the workspace that shared it, and the invite's `status` (`pending`,
`accepted` or `revoked`). It shows no members. The call needs no workspace.

Errors:

- `404 not_found`: the token is unknown, or the list was deleted.

Open to any signed-in caller.

Needs the `saved_lists` 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/saved-list-invites/GET/v1/saved-list-invites/%7Btoken%7D)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `token` | path | string | yes | The token from the invite link. |
| `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. |

### Response 200

`data` is a `SavedListInvite`.

| Field | Type | Description |
| --- | --- | --- |
| `token` | string | The invite token, the same value as in the link. |
| `listName` | string | The shared list's name. |
| `kind` | string, one of: people, companies | What the list holds: `people` or `companies`. |
| `memberCount` | integer (int32) | Number of members on the list. |
| `ownerWorkspaceName` | string | The name of the workspace that shared the list. |
| `status` | string, one of: pending, accepted, revoked | The invite's status: `pending`, `accepted` or `revoked`. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/saved-list-invites/01JC8Z3K6Q2W4M7N9P5R1T3V5X" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02"
```

### Example response

```json
{
  "success": true,
  "data": {
    "token": "string",
    "listName": "string",
    "kind": "people",
    "memberCount": 1,
    "ownerWorkspaceName": "string",
    "status": "pending"
  }
}
```

## Accept a saved list invite

`POST /v1/saved-list-invites/{token}/accept` - operationId `saved-list-invites.accept`

| Permission | Rate limit |
| --- | --- |
| Search edit | 4,800 requests a minute per API key |

Adds the shared list, read-only, to the workspace you call in. The list then appears in
`GET /v1/saved-lists` with `scope=shared`. The request has no body, and the response is the accepted
grant.

The signed-in user's email address must be the address the invite was sent to. An invite is accepted once, into
one workspace.

Errors:

- `403 forbidden`: the invite was sent to another email address. Sign in with that address to accept it.
- `404 not_found`: the token is unknown, the list was deleted, or the owner revoked the invite.
- `409 invalid_state`: the invite was already accepted, or this workspace owns the list.
- `409 conflict`: this workspace already has the list through another invite.

Requires Search edit.

Needs the `saved_lists` 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/saved-list-invites/POST/v1/saved-list-invites/%7Btoken%7D/accept)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `token` | path | string | yes | The token from the invite link. |
| `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 `SavedListGrant`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | The grant's id. |
| `savedListId` | integer (int64) | The id of the shared saved list. |
| `inviteeEmail` | string | The email address the invite went to. |
| `status` | string, one of: pending, accepted, revoked | The grant's state: `pending` until someone accepts the invite, then `accepted`, or `revoked` once the list's workspace revokes it. |
| `receivingWorkspaceId` | integer (int64) | The workspace that accepted the invite. It stays after a revoke, so you can see who had the list. Omitted when nobody accepted. |
| `receivingWorkspaceName` | string | The name of the workspace that accepted the invite. Omitted when nobody accepted. |
| `invitedByUserId` | integer (int64) | The user who sent the invite. Omitted when an API key that belongs to no user sent it. |
| `acceptedAt` | string (date-time) | When the invite was accepted, in UTC. Omitted when nobody accepted. |
| `revokedAt` | string (date-time) | When the grant was revoked, in UTC. Omitted unless the grant is revoked. |
| `createdAt` | string (date-time) | When the invite was created, in UTC. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/saved-list-invites/01JC8Z3K6Q2W4M7N9P5R1T3V5X/accept" \
  -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,
    "savedListId": 812,
    "inviteeEmail": "jane@example.com",
    "status": "pending",
    "receivingWorkspaceId": 812,
    "receivingWorkspaceName": "string",
    "invitedByUserId": 812,
    "acceptedAt": "2026-09-23T15:02:11Z",
    "revokedAt": "2026-09-23T15:02:11Z",
    "createdAt": "2026-09-23T15:02:11Z"
  }
}
```

All resources: [/docs.md](/docs.md).
