> 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: Get a saved list invite

> **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 [Saved list invites](/docs/api/saved-list-invites.md). Authentication, workspaces and errors: [/docs.md](/docs.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"
  }
}
```
