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

# Inboxes: Check whether an inbox can send a 1:1 email

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

One endpoint of [Inboxes](/docs/api/inboxes.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Check whether an inbox can send a 1:1 email

`GET /v1/inboxes/{inboxId}/one-to-one-readiness` - operationId `inboxes.get-one-to-one-readiness`

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

Says whether an approved 1:1 email that names this inbox goes out now: an account touch, or a workflow
`send.email` step whose `fromInbox` is this inbox. It applies the checks the send applies, and sends and
changes nothing.

`senderKind` says how the inbox sends: `member_mailbox`, `shared_inbox` or
`sending_identity`. When `canSend` is false, `reason` says why (`receive_only`,
`not_connected`, `replies_not_read`, `not_cold_sender`, `not_primary` or `paused`) and
`message` what fixes it. Such an email waits until the inbox can send.

`signatureWarning` is `brand_domain` when a member's mailbox has a saved signature that loads from or
links to a Kenso domain the mailbox's own domain does not cover in a way the brand check refuses (an image, a
tracking link). A 1:1 email from it still goes, without the signature; `signatureMessage` says what to remove.
Both are omitted otherwise.

Errors:

- `404 not_found`: no inbox with this id in the workspace.

Requires Delivery view.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/inboxes/GET/v1/inboxes/%7BinboxId%7D/one-to-one-readiness)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `inboxId` | path | integer (int64) | yes | The inbox's id. |
| `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 `InboxOneToOneReadiness`.

| Field | Type | Description |
| --- | --- | --- |
| `inboxId` | integer (int64) | The inbox. |
| `email` | string | Its address. |
| `senderKind` | string | How it sends a 1:1 email: `member_mailbox` (a member's own mailbox, only as their primary inbox), `shared_inbox` (a shared campaign inbox on a cold sending domain) or `sending_identity` (a sending provider identity, through its provider connection). |
| `canSend` | boolean | True when an approved 1:1 email touch that names this inbox (an Accounts touch, or a workflow `send.email` step's `fromInbox`) goes out now, and its reply comes back to Kenso. False when the touch would wait (`connect_inbox`, or `inbox_paused` for `paused`). |
| `reason` | string | Why it cannot send; omitted when canSend is true. `receive_only`: retired or the replies inbox. `not_connected`: its connection, or a sending identity's provider connection, cannot send now. `replies_not_read`: a sending identity whose replies would not reach Kenso. `not_cold_sender`: not on one of the workspace's cold sending domains. `not_primary`: a member's mailbox off the workspace's domains. `paused`: a member paused it. Tolerate values not listed here. |
| `message` | string | What fixes it, for a person; omitted when canSend is true. |
| `signatureWarning` | string | `brand_domain` when the inbox is a member's mailbox whose saved signature loads from or links to a Kenso domain the mailbox's own domain does not cover in a way the brand check refuses (an image, a Kenso tracking or system link), so a 1:1 email from it goes out without the signature (the email itself still goes). A plain link to a Kenso site is allowed and is no warning. Omitted when the signature goes out as saved, or the inbox adds none. Tolerate values not listed here. |
| `signatureMessage` | string | What fixes the signature, for a person, naming what the check found; omitted with signatureWarning. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/inboxes/812/one-to-one-readiness" \
  -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": {
    "inboxId": 812,
    "email": "jane@example.com",
    "senderKind": "string",
    "canSend": true,
    "reason": "string",
    "message": "string",
    "signatureWarning": "string",
    "signatureMessage": "string"
  }
}
```
