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

# Authentication

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

Every request to the Kenso API carries an API key from your Kenso account as a Bearer token.

## Create a key

In the Kenso app, open [Settings > Integrations > API keys](https://app.ken.so/settings/api-keys) and create a key. The key is shown once, when you create it, so copy it then.

Keep it on your server or in a secret store. Anyone with the key can act as you in your workspaces.

## Send it with every request

Pass the key in the `Authorization` header, with `Ken-Version: 2026-11-02`:

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

## What a key can do

A key acts with the role and permissions you have in the workspace. A call your permissions do not allow answers `403` with the code `permission_denied`, and its `details` names the permission the call needs.

A `403` with the code `forbidden` is about one resource, not your role: the caller may not act on it. Handle both codes. See [Errors](/docs/errors).

## When a key is rejected

A missing, invalid or revoked key answers `401`. That response comes from the authentication layer in front of the endpoints, so its body is `{ "error": "Invalid or revoked API key" }` or empty, not the usual error object. Branch on the status.

If a key leaks, revoke it in the same settings page and create a new one.

## More guides

- [Workspaces](/docs/workspaces.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)
