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

# Workspaces

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

Most of what the API reads and writes lives in a workspace: campaigns, contacts, inboxes, threads. The `X-Ken-Workspace-Id` header says which one.

## The header

Send the workspace id as an integer:

```bash
curl "https://api.ken.so/v1/campaigns" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: 812"
```

Each operation in the reference lists `X-Ken-Workspace-Id` among its parameters when it acts in a workspace. Operations that do not list it ignore it.

## When you need it

- Your key reaches exactly one workspace: you can leave the header out, and the request acts in that workspace.
- Your key reaches more than one workspace: a request without the header answers `400` with the code `workspace_required`.

Sending it every time is the safe default: the request keeps working when you are added to a second workspace.

## Find your workspace ids

[List workspaces](/docs/api/workspaces#workspaces.list) returns every workspace your key can reach, with its id. [Get the current user](/docs/api/me#me.get) returns you and your workspaces too.

## Resources in other workspaces

A resource in a workspace you are not a member of answers `404` with the code `not_found`, the same as one that does not exist. The API never confirms that another workspace's resource exists.

## More guides

- [Authentication](/docs/authentication.md)
- [Versioning](/docs/versioning.md)
- [Pagination](/docs/pagination.md)
- [Errors](/docs/errors.md)
- [Rate limits](/docs/rate-limits.md)
- [Idempotency](/docs/idempotency.md)
- [Webhooks](/docs/webhooks.md)
- [Changelog](/docs/changelog.md)
- [API reference](/docs.md)
