> 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-lists/openapi.json](/docs/api/saved-lists/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# Saved lists: Share a saved list by email

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

## Share a saved list by email

`POST /v1/saved-lists/{savedListId}/invites` - operationId `saved-lists.create-invite`

| Permission | Rate limit |
| --- | --- |
| Search edit and the `share` permission | 30 requests a minute per API key |

Shares one of the workspace's own lists, read-only, with an email address. Kenso creates a grant with status
`pending` and emails the address a link to `https://app.ken.so/lists/accept/{token}`. The person who
accepts picks which of their workspaces receives the list.

`email` is required. A list with members from a CSV upload needs
`POST /v1/saved-lists/{savedListId}/rights-confirmation` first. Kenso keeps the grant even when the email
cannot be sent, so you can revoke it and invite again. The response is `201` with the grant, which never
shows the invite token.

Errors:

- `400 validation_failed`: `email` is missing or is not an email address.
- `403 forbidden`: the caller is a workspace key. The invite records the member who sent it, and a
workspace key is not a person.
- `404 not_found`: the list is not one of the workspace's own lists, or it is another member's private list.
- `409 invalid_state`: the list is private. Set its `visibility` to `workspace` first.
- `409 rights_confirmation_required`: the list has members from a CSV upload, and nobody confirmed the right
to share them.
- `409 conflict`: this address already has a pending invite to the list.

Requires Search edit and the `share` permission.

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-lists/POST/v1/saved-lists/%7BsavedListId%7D/invites)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `savedListId` | path | integer (int64) | yes | The saved list's id. |
| `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 |
| --- | --- | --- | --- |
| `email` | string | yes | The address Kenso sends the invite link to. Only a person signed in with this address can accept. Required. |

### Response 201

`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-lists/812/invites" \
  -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 '{
  "email": "jane@example.com"
}'
```

### 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"
  }
}
```
