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

# Kenso status

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

The status of Kenso's public components: the API, sending and webhooks. Read it to tell a Kenso outage from a problem on your side. It takes no credential.

Reporting. 1 endpoint 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/status/openapi.json](/docs/api/status/openapi.json).

- `GET /v1/status` - Get Kenso's status (`status.get`): [/docs/api/status/get.md](/docs/api/status/get.md)

## Get Kenso's status

`GET /v1/status` - operationId `status.get`

| Permission | Rate limit |
| --- | --- |
| None: no API key needed | 120 requests a minute per IP address |

Returns the status of each Kenso component and the worst of them. A component is `operational`,
`degraded` (running late), `outage` (not running) or `unknown` (Kenso could not check it).

- `api` is `operational` whenever this call answers.
- `sending` is `operational` while a pass of the sending dispatcher succeeded in the last 3 minutes,
`degraded` up to 15 minutes, then `outage`. A pass that fails does not count, so passes that keep
failing make it `degraded` after 3 minutes.
- `webhooks` is `operational` while a webhook dispatch run delivered, or had nothing to deliver, in the
last 5 minutes, `degraded` up to 15 minutes, then `outage`. A run counts as delivered once the webhook
provider accepted its events; a run that could not hand them over does not count.

The status says whether each pipeline is running, not how one workspace's sends or webhook deliveries went: a
webhook endpoint that answers with an error does not make `webhooks` degraded, because the provider accepts
the event and retries that endpoint itself. Kenso runs the check at most
every 30 seconds and marks the response cacheable for 30 seconds.

Needs no credential, and answers the same without a `Ken-Version` header, so
`curl https://api.ken.so/v1/status` works as is.

[Try it on developer.ken.so](https://developer.ken.so/#kenso-api/tag/status/GET/v1/status)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `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 default 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 date that is not a version answers `400 unsupported_version`; any other value that is not a version is treated as legacy. |

### Response 200

`data` is a `PlatformStatus`.

| Field | Type | Description |
| --- | --- | --- |
| `status` | string, one of: operational, degraded, outage, unknown | The worst status of the components: `outage`, then `degraded`, then `unknown`, then `operational`. |
| `checkedAt` | string (date-time) | When Kenso ran this check, in UTC. Kenso runs it at most every 30 seconds. |
| `components` | array of PlatformStatusComponent | The components, in a fixed order: `api`, `sending`, `webhooks`. |

### Request

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

### Example response

```json
{
  "success": true,
  "data": {
    "status": "operational",
    "checkedAt": "2026-09-23T15:02:11Z",
    "components": [
      {
        "id": "api",
        "name": "Sending",
        "status": "operational",
        "lastActivityAt": "2026-09-23T15:02:11Z"
      }
    ]
  }
}
```

## Types

Each named type the tables above use, nested ones included.

### PlatformStatusComponent

One Kenso component and how it is doing.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | no | The component's stable id: `api`, `sending` or `webhooks`. New ids may be added. |
| `name` | string | no | The component's display name, such as `Sending`. |
| `status` | string, one of: operational, degraded, outage, unknown | no | How the component is doing. |
| `lastActivityAt` | string (date-time) | no | When the component last showed it was running, in UTC: for `sending` the start of the newest dispatch pass that succeeded, for `webhooks` the start of the newest webhook dispatch run that delivered or had nothing to deliver, for `api` the check itself. Omitted when Kenso found no such run in the last hour or could not check. |

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