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

# Infrastructure findings

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

Infra findings are problems Kenso finds in a workspace's inboxes and domains, such as a disconnected inbox, a domain about to expire or a deleted mailbox that is still billed. Kenso checks every 6 hours, opens a finding for each new problem and resolves it once a later check no longer sees the problem. Use this section to count and list findings and to snooze, ignore or reopen one. A status change hides or shows a finding and changes nothing on the inbox or domain itself.

Deliverability. 3 endpoints 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/infra/openapi.json](/docs/api/infra/openapi.json).

- `GET /v1/infra/findings` - List infra findings (`infra.findings`): [/docs/api/infra/findings.md](/docs/api/infra/findings.md)
- `PATCH /v1/infra/findings/{findingId}` - Update an infra finding (`infra.update-finding`): [/docs/api/infra/update-finding.md](/docs/api/infra/update-finding.md)
- `GET /v1/infra/summary` - Get the infra summary (`infra.summary`): [/docs/api/infra/summary.md](/docs/api/infra/summary.md)

## List infra findings

`GET /v1/infra/findings` - operationId `infra.findings`

| Permission | Rate limit |
| --- | --- |
| Delivery view | 12,000 requests a minute per API key |

Lists the workspace's infra findings, newest first. Without a `status` filter it returns open findings only.

Each filter takes one value or several separated by commas, and a finding matches when it has any of them.
`evidence` holds what Kenso saw, and `suggestedAction` names the fix Kenso recommends.

Errors:

- `400 validation_failed`: a filter value is not one of its allowed values, `limit` is not from 1 to 200, or `cursor` is invalid.

Requires Delivery view.

Needs the `infra_findings` 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/infra/GET/v1/infra/findings)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `kind` | query | string | no | Kinds to return, separated by commas: `billing_leak`, `provider_cancelled`, `warmup_missing`, `idle_domain`, `domain_expiring`, `inbox_no_domain` or `disconnected_inbox`. Omitted returns every kind. |
| `status` | query | string | no | Statuses to return, separated by commas: `open`, `snoozed`, `ignored` or `resolved`. Omitted returns open findings only. |
| `severity` | query | string | no | Severities to return, separated by commas: `critical`, `warning` or `info`. Omitted returns every severity. |
| `cursor` | query | string | no | The `nextCursor` from the previous page. Omit it for the first page. |
| `limit` | query | integer (int32) | no | Findings per page, from 1 to 200. Defaults to 50. |
| `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`. |

### Response 200

`data` is a list of `InfraFinding`. Each item has these fields. The response also carries `pagination`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | Id of the finding. |
| `workspaceId` | integer (int64) | Id of the workspace the finding belongs to. |
| `kind` | string | What the problem is: `billing_leak` (a deleted inbox or domain the provider still bills), `provider_cancelled` (a live inbox its provider cancelled or will cancel), `warmup_missing` (a Kenso-managed inbox whose warmup is gone), `idle_domain` (a domain with no live inbox for 14 days or more), `domain_expiring` (a domain that expires within 30 days), `inbox_no_domain` (an inbox not linked to its domain) or `disconnected_inbox` (an inbox disconnected or failing to connect for 3 days or more). |
| `subjectType` | string | What `subjectId` points to: `inbox` or `domain`. |
| `subjectId` | integer (int64) | Id of the inbox or domain the finding is about. It may already be deleted, as on a `billing_leak`. |
| `subjectKey` | string | Stable key of the subject, such as `inbox:123` or `domain:45`. |
| `provider` | string | The provider lane code. Prefer providerKind. |
| `providerKind` | string | Where Kenso saw the problem, in neutral words: `mailbox_provider` for the provider of Kenso-managed mailboxes, `registrar` for the registrar of domains bought through Kenso, `kenso` for Kenso's own records, or `other`. Omitted when the finding has no provider. |
| `severity` | string | How urgent the finding is: `critical`, `warning` or `info`. |
| `status` | string | Status of the finding: `open`, `snoozed`, `ignored` or `resolved`. Kenso resolves an open or snoozed finding once a later check no longer sees the problem. |
| `title` | string | One line that names the problem, such as "Domain example.com has had no live inbox for 21 days". |
| `evidence` | object | What Kenso saw, as a JSON object whose keys depend on `kind`. |
| `suggestedAction` | string | The fix Kenso recommends, such as `check_connection`, `renew_domain` or `domain_auto_renew_off`. It is a hint and runs nothing. Omitted when Kenso has no suggestion. |
| `monthlyCost` | Money | What the inbox or domain costs a month, with `amount` in cents. Omitted when Kenso does not know the price. |
| `firstSeenAt` | string (date-time) | When Kenso first saw the problem, in UTC. |
| `lastSeenAt` | string (date-time) | When a check last saw the problem, in UTC. |
| `resolvedAt` | string (date-time) | When Kenso resolved the finding, in UTC. Omitted while it is unresolved. |
| `snoozedUntil` | string (date-time) | When a snoozed finding opens again, in UTC. Omitted unless the finding is snoozed. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/infra/findings?limit=50" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"
```

### Example response

```json
{
  "success": true,
  "data": [
    {
      "id": 812,
      "workspaceId": 812,
      "kind": "string",
      "subjectType": "inbox",
      "subjectId": 812,
      "subjectKey": "inbox:123",
      "provider": "string",
      "providerKind": "string",
      "severity": "critical",
      "status": "open",
      "title": "string",
      "evidence": null,
      "suggestedAction": "check_connection",
      "monthlyCost": {
        "amount": 1,
        "currency": "usd"
      },
      "firstSeenAt": "2026-09-23T15:02:11Z",
      "lastSeenAt": "2026-09-23T15:02:11Z",
      "resolvedAt": "2026-09-23T15:02:11Z",
      "snoozedUntil": "2026-09-23T15:02:11Z"
    }
  ],
  "pagination": {
    "nextCursor": "eyJpZCI6ODE1fQ",
    "hasMore": true,
    "total": 1,
    "totalCount": 1,
    "isTotalCapped": true
  }
}
```

## Update an infra finding

`PATCH /v1/infra/findings/{findingId}` - operationId `infra.update-finding`

| Permission | Rate limit |
| --- | --- |
| Delivery edit | 4,800 requests a minute per API key |

Snoozes, ignores or reopens one finding. Use it to hide a finding you already know about. It changes nothing on
the inbox, the domain or at a provider.

Send `status`: `snoozed` with `snoozedUntil`, `ignored`, or `open` to reopen the finding. A snoozed finding opens
again at the first check after `snoozedUntil`. An ignored finding stays ignored until you reopen it, and Kenso
never resolves it on its own. Kenso writes who made the change to the workspace's audit log. Returns the updated
finding.

Errors:

- `400 validation_failed`: `status` is missing or not `open`, `snoozed` or `ignored`, or `snoozedUntil` is missing with `snoozed`, not in the future, more than a year ahead, or sent with another status.
- `403 forbidden`: the finding is a `billing_leak`. Kenso fixes those itself, so you cannot snooze or ignore one.
- `404 not_found`: the workspace has no finding with this id.
- `409 invalid_state`: the finding is resolved.

Requires Delivery edit.

Needs the `infra_findings` 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/infra/PATCH/v1/infra/findings/%7BfindingId%7D)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `findingId` | path | integer (int64) | yes | Id of the finding. |
| `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 |
| --- | --- | --- | --- |
| `status` | string | yes | New status: `snoozed`, `ignored`, or `open` to reopen the finding. Required. |
| `snoozedUntil` | string (date-time) | no | When a snoozed finding opens again, as an ISO 8601 UTC timestamp in the future and at most a year ahead. Required with `snoozed` and refused with any other status. |

### Response 200

`data` is a `InfraFinding`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | Id of the finding. |
| `workspaceId` | integer (int64) | Id of the workspace the finding belongs to. |
| `kind` | string | What the problem is: `billing_leak` (a deleted inbox or domain the provider still bills), `provider_cancelled` (a live inbox its provider cancelled or will cancel), `warmup_missing` (a Kenso-managed inbox whose warmup is gone), `idle_domain` (a domain with no live inbox for 14 days or more), `domain_expiring` (a domain that expires within 30 days), `inbox_no_domain` (an inbox not linked to its domain) or `disconnected_inbox` (an inbox disconnected or failing to connect for 3 days or more). |
| `subjectType` | string | What `subjectId` points to: `inbox` or `domain`. |
| `subjectId` | integer (int64) | Id of the inbox or domain the finding is about. It may already be deleted, as on a `billing_leak`. |
| `subjectKey` | string | Stable key of the subject, such as `inbox:123` or `domain:45`. |
| `provider` | string | The provider lane code. Prefer providerKind. |
| `providerKind` | string | Where Kenso saw the problem, in neutral words: `mailbox_provider` for the provider of Kenso-managed mailboxes, `registrar` for the registrar of domains bought through Kenso, `kenso` for Kenso's own records, or `other`. Omitted when the finding has no provider. |
| `severity` | string | How urgent the finding is: `critical`, `warning` or `info`. |
| `status` | string | Status of the finding: `open`, `snoozed`, `ignored` or `resolved`. Kenso resolves an open or snoozed finding once a later check no longer sees the problem. |
| `title` | string | One line that names the problem, such as "Domain example.com has had no live inbox for 21 days". |
| `evidence` | object | What Kenso saw, as a JSON object whose keys depend on `kind`. |
| `suggestedAction` | string | The fix Kenso recommends, such as `check_connection`, `renew_domain` or `domain_auto_renew_off`. It is a hint and runs nothing. Omitted when Kenso has no suggestion. |
| `monthlyCost` | Money | What the inbox or domain costs a month, with `amount` in cents. Omitted when Kenso does not know the price. |
| `firstSeenAt` | string (date-time) | When Kenso first saw the problem, in UTC. |
| `lastSeenAt` | string (date-time) | When a check last saw the problem, in UTC. |
| `resolvedAt` | string (date-time) | When Kenso resolved the finding, in UTC. Omitted while it is unresolved. |
| `snoozedUntil` | string (date-time) | When a snoozed finding opens again, in UTC. Omitted unless the finding is snoozed. |

### Request

```bash
curl -X PATCH "https://api.ken.so/v1/infra/findings/812" \
  -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 '{
  "status": "snoozed",
  "snoozedUntil": "2026-09-23T15:02:11Z"
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "id": 812,
    "workspaceId": 812,
    "kind": "string",
    "subjectType": "inbox",
    "subjectId": 812,
    "subjectKey": "inbox:123",
    "provider": "string",
    "providerKind": "string",
    "severity": "critical",
    "status": "open",
    "title": "string",
    "evidence": null,
    "suggestedAction": "check_connection",
    "monthlyCost": {
      "amount": 1,
      "currency": "usd"
    },
    "firstSeenAt": "2026-09-23T15:02:11Z",
    "lastSeenAt": "2026-09-23T15:02:11Z",
    "resolvedAt": "2026-09-23T15:02:11Z",
    "snoozedUntil": "2026-09-23T15:02:11Z"
  }
}
```

## Get the infra summary

`GET /v1/infra/summary` - operationId `infra.summary`

| Permission | Rate limit |
| --- | --- |
| Delivery view | 12,000 requests a minute per API key |

Counts the workspace's open and snoozed findings, with what the inboxes and domains behind them cost a month. Use
it for a badge or a health overview before you list the findings.

`openCount` and `bySeverity` count open findings, and `snoozedCount` counts snoozed ones. Ignored and resolved
findings are not counted. `byKind` has one entry for each kind with open findings. Money values cover only the
inboxes and domains whose price Kenso knows, and their `amount` is in cents.

Requires Delivery view.

Needs the `infra_findings` 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/infra/GET/v1/infra/summary)

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

### Response 200

`data` is a `InfraSummary`.

| Field | Type | Description |
| --- | --- | --- |
| `openCount` | integer (int32) | Number of open findings. |
| `snoozedCount` | integer (int32) | Number of snoozed findings. |
| `bySeverity` | InfraSeverityCounts | Open findings counted by severity. |
| `byKind` | array of InfraKindSummary | One entry for each kind that has open findings. |
| `monthlyCostAtStake` | Money | What the inboxes and domains of all open findings cost a month, with `amount` in cents. Counts only those whose price Kenso knows. |
| `lastSweep` | InfraSweep | The newest run of Kenso's infra check. Always omitted on `GET /v1/infra/summary`. |

### Request

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

### Example response

```json
{
  "success": true,
  "data": {
    "openCount": 1,
    "snoozedCount": 1,
    "bySeverity": {
      "critical": 1,
      "warning": 1,
      "info": 1
    },
    "byKind": [
      {
        "kind": "string",
        "openCount": 1,
        "critical": 1,
        "warning": 1,
        "info": 1,
        "monthlyCost": {
          "amount": 1,
          "currency": "usd"
        }
      }
    ],
    "monthlyCostAtStake": {
      "amount": 1,
      "currency": "usd"
    },
    "lastSweep": {
      "sweepId": 812,
      "trigger": "string",
      "status": "running",
      "startedAt": "2026-09-23T15:02:11Z",
      "finishedAt": "2026-09-23T15:02:11Z",
      "detectors": [
        {
          "kind": "string",
          "subjectType": "string",
          "outcome": "completed",
          "found": 1,
          "opened": 1,
          "resolved": 1,
          "error": "string"
        }
      ],
      "error": "string"
    }
  }
}
```

## Types

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

### Money

An amount of money.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `amount` | integer (int64) | no | The amount in the currency's smallest unit, such as cents for `usd`: 1250 is 12.50 dollars. |
| `currency` | string | no | The currency, as a lowercase three-letter ISO 4217 code such as `usd`. |

### InfraSeverityCounts

Open infra findings counted by severity.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `critical` | integer (int32) | no | Open findings with severity `critical`. |
| `warning` | integer (int32) | no | Open findings with severity `warning`. |
| `info` | integer (int32) | no | Open findings with severity `info`. |

### InfraKindSummary

Open infra findings of one kind.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `kind` | string | no | The finding kind, as in `kind` on a finding. |
| `openCount` | integer (int32) | no | Open findings of this kind. |
| `critical` | integer (int32) | no | Open findings of this kind with severity `critical`. |
| `warning` | integer (int32) | no | Open findings of this kind with severity `warning`. |
| `info` | integer (int32) | no | Open findings of this kind with severity `info`. |
| `monthlyCost` | Money | no | What the inboxes and domains of these findings cost a month, with `amount` in cents. Counts only those whose price Kenso knows. |

### InfraSweep

One run of Kenso's infra check.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `sweepId` | integer (int64) | no | Id of the run. |
| `trigger` | string | no | What started the run: `schedule` for the check every 6 hours. Any other value means Kenso started the run by hand. Omitted when a start found a run already in progress. |
| `status` | string | no | Status of the run: `running`, `completed` or `failed`. |
| `startedAt` | string (date-time) | no | When the run started, in UTC. |
| `finishedAt` | string (date-time) | no | When the run finished, in UTC. Omitted while it runs. |
| `detectors` | array of InfraSweepDetector | no | One entry for each check the run made. |
| `error` | string | no | Why the run failed. Omitted when it did not fail. |

### InfraSweepDetector

One check within a run of Kenso's infra check, for one kind of finding.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `kind` | string | no | The finding kind this check looks for. |
| `subjectType` | string | no | What the check looks at, as in `subjectType` on a finding. |
| `outcome` | string | no | Result of the check: `completed`, `failed` or `skipped`. Only a completed check resolves findings. |
| `found` | integer (int32) | no | Problems the check found. |
| `opened` | integer (int32) | no | New findings the check opened. |
| `resolved` | integer (int32) | no | Findings the check resolved because their problem was gone. |
| `error` | string | no | Why the check did not complete. Omitted when Kenso has no reason. |

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