Kenso

Kenso status

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.

Reporting1 endpointKen-Version: 2026-11-02AuthenticationWorkspacesErrors
MarkdownOpenAPI

Headers

The endpoints on this page take these headers. Each endpoint's curl shows the ones it sends.

Name
In
Type
Required
Description
Ken-Version
In: header
string, one of: 2026-11-02, 1.1
optional
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.

Get Kenso's status

GET/v1/statusstatus.get
Permission
None: no API key needed
Rate limit
120 requests a minute per IP address

Try it on developer.ken.so

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.

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

Response 200

data is a PlatformStatus.

Show the 3 response fields and an example

The fields and an example are also on this endpoint's Markdown page.