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

# Autonomous replies: Update the autonomous reply settings

> **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 [Autonomous replies](/docs/api/autonomous-reply-settings.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Update the autonomous reply settings

`PATCH /v1/autonomous-reply-settings` - operationId `autonomous-reply-settings.update`

| Permission | Rate limit |
| --- | --- |
| The `workspace_settings` permission | 4,800 requests a minute per API key |

Changes the fields you send and keeps the rest. Send a JSON object with any of these fields:

- `defaultEnabled` (boolean): turns Ken's replies on or off for the workspace.
- `linkedInEnabled` (boolean): lets Ken reply on LinkedIn too while `defaultEnabled` is true. On LinkedIn
Ken writes drafts only, whatever `mode` says.
- `mode`: `draft`, `autonomous` or `approve_risky`. `approve_risky` needs the
`reply_agent_approve_risky` feature on the workspace.
- `extraInstructions` (string, at most 4,000 characters): instructions Ken follows when it writes replies.
Kenso trims the text. `null` or a blank string clears them.

With the `reply_agent_rules` feature you can also send:

- `typeRules`: a list of `{type, action}`, each type at most once. `type` is `interested`,
`question` or `objection`; `action` is `draft` (Ken writes a draft for a member to send),
`auto_send` (Ken sends its reply 15 minutes after it writes it unless a member cancels, at most 20 a day; a
flagged reply, a meeting request or a meeting time negotiation still waits for a member) or `escalate` (Ken
hands the reply to a member and writes no draft). Only the types you list change. While the feature is on, these
rules decide Ken's first answer to an email reply of those types, so a meeting request in one waits for a member
whatever `mode` is; `mode` keeps deciding LinkedIn and the turns of a meeting time negotiation already
under way.
- `autoSendPaused` (boolean): `true` pauses auto-send, so `auto_send` replies wait as drafts.
- `escalateToUserId` (integer or `null`): the workspace member who answers Ken's questions. `null`
clears it, and the workspace's earliest Admin answers.
- `trial` (boolean): `true` starts a 7-day auto-send trial unless one is running; `false` ends it.

When you turn replies off or set `mode` to `draft`, Kenso turns the replies Ken is holding to send into
drafts for a member to review. With the `reply_agent_rules` feature, `draft` mode turns only the replies
the mode held, pausing auto-send turns every held reply into a draft, and moving a type off `auto_send` turns
that type's held replies into drafts. An empty object changes nothing and returns the settings.

Errors:

- `400 validation_failed`: the body is not a JSON object, a field is unknown or has the wrong type,
`extraInstructions` is longer than 4,000 characters, or `mode` is not a known mode. A workspace without
the `reply_agent_approve_risky` feature gets this error for `approve_risky` too. A workspace without the
`reply_agent_rules` feature gets it for `typeRules`, `autoSendPaused`, `escalateToUserId` and
`trial`, with the detail code `feature_disabled`. An `escalateToUserId` that is not a member of the
workspace, or is on a Client seat, gets it with the detail code `invalid`.

Requires the `workspace_settings` permission.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/autonomous-reply-settings/PATCH/v1/autonomous-reply-settings)

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

### Request body

`application/json`, optional: `object`.

### Response 200

`data` is a `AutonomousReplySettings`.

| Field | Type | Description |
| --- | --- | --- |
| `defaultEnabled` | boolean | True when Ken answers the workspace's interested and objection replies. Default false. |
| `linkedInEnabled` | boolean | True when Ken also answers LinkedIn replies. It takes effect only while `defaultEnabled` is true, and on LinkedIn Ken writes drafts only. Default false. |
| `mode` | string | How Ken handles the replies it writes: `draft` (drafts for a member to send, the default), `autonomous` (Ken sends after a hold window) or `approve_risky` (Ken sends a reply that passes every check after the hold window, and a flagged reply, a meeting request or a meeting time negotiation waits for a member). |
| `extraInstructions` | string | The instructions Ken follows when it writes replies. Omitted when there are none. |
| `createdAt` | string (date-time) | When the settings were first saved, in UTC. Omitted until they are saved. |
| `updatedAt` | string (date-time) | When the settings last changed, in UTC. Omitted until they are saved. |
| `typeRules` | array of AutonomousReplyTypeRule | What Ken does with each reply type: always `interested`, `question` and `objection`, in that order, each with `draft` (the default), `auto_send` or `escalate`. Only with the `reply_agent_rules` feature; omitted otherwise. |
| `autoSendHoldMinutes` | integer (int32) | Minutes Ken holds an `auto_send` reply before it sends, during which a member can cancel it: 15. Only with the `reply_agent_rules` feature; omitted otherwise. |
| `dailyAutoSendCap` | integer (int32) | Most replies Ken auto-sends for the workspace in 24 hours: 20. Only with the `reply_agent_rules` feature; omitted otherwise. |
| `autoSendsToday` | integer (int32) | Replies Ken auto-sent in the last 24 hours. Only with the `reply_agent_rules` feature; omitted otherwise. |
| `autoSendPaused` | boolean | True when auto-send is paused: `auto_send` replies wait as drafts for a member. Only with the `reply_agent_rules` feature; omitted otherwise. |
| `escalateToUserId` | integer (int64) | The member who answers Ken's questions. Omitted when none is set, where the workspace's earliest Admin answers, and without the `reply_agent_rules` feature. |
| `trialEndsAt` | string (date-time) | When the running 7-day auto-send trial ends, in UTC. Omitted when no trial is running, and without the `reply_agent_rules` feature. |

### Request

```bash
curl -X PATCH "https://api.ken.so/v1/autonomous-reply-settings" \
  -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 '{}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "defaultEnabled": true,
    "linkedInEnabled": true,
    "mode": "string",
    "extraInstructions": "string",
    "createdAt": "2026-09-23T15:02:11Z",
    "updatedAt": "2026-09-23T15:02:11Z",
    "typeRules": [
      {
        "type": "interested",
        "action": "string"
      }
    ],
    "autoSendHoldMinutes": 1,
    "dailyAutoSendCap": 1,
    "autoSendsToday": 1,
    "autoSendPaused": true,
    "escalateToUserId": 812,
    "trialEndsAt": "2026-09-23T15:02:11Z"
  }
}
```

## Types

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

### AutonomousReplyTypeRule

What Ken does with one reply type.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `type` | string | no | The reply type: `interested`, `question` or `objection`. |
| `action` | string | no | `draft` (Ken writes a draft for a member to send), `auto_send` (Ken sends its reply 15 minutes after it writes it unless a member cancels, at most 20 a day) or `escalate` (Ken hands the reply to a member and writes no draft). |
