Agent permissions
Ken's agent permissions decide, per action, whether Ken asks a person first (asks_first) or acts on its own (runs_on_its_own) for the workspace. The actions, in page order, are send_email, send_linkedin, research_accounts, scan_signals, build_assets, run_crm_workflows and book_meetings. runs_on_its_own removes one thing, the per-item approval: every other guard (suppression, limits, sending windows, client approvals) still applies. These modes decide what Ken does unattended; they do not limit what a caller does with its own role. Behind the agent_permissions feature, and never open to a Client seat.
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 | 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 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 date that is not a version answers 400 unsupported_version; any other value that is not a version is treated as legacy. |
X-Ken-Workspace-Id | header | integer (int64) | optional | 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. |
Get Ken's agent permissions
/v1/agent-permission-settingsagent-permission-settings.get- Permission
- Any workspace member except a Network member
- Rate limit
- 12,000 requests a minute per API key
agent_permissions feature on your workspace. Until it is on, calls answer 404.Returns every action with its mode, always all seven in page order. An action the workspace never set has its default (send_email, send_linkedin and build_assets ask first; the others run on their own) and updatedAt null. available is false for an action Kenso does not follow yet: its mode cannot change. book_meetings reads asks_first with lockedReason reply_agent_not_autonomous while the reply agent is off or not autonomous. That asks_first is not the stored mode: send the row back in a PATCH only to store asks_first. clientWorkspace is true for a workspace run for a client.
Errors:
404 not_found: the workspace does not have theagent_permissionsfeature.
Open to any workspace member except a Client seat.
curl -X GET "https://api.ken.so/v1/agent-permission-settings" \
-H "Authorization: Bearer $KENSO_API_KEY" \
-H "Ken-Version: 2026-11-02" \
-H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"Response 200
data is a AgentPermissionSettings.
Show the 2 response fields and an example
The fields and an example are also on this endpoint's Markdown page.
Update Ken's agent permissions
/v1/agent-permission-settingsagent-permission-settings.update- Permission
- The
workspace_settingspermission - Rate limit
- 4,800 requests a minute per API key
agent_permissions feature on your workspace. Until it is on, calls answer 404.Sets the mode of each action you name and leaves the others as they are. Body: { "permissions": [ { "action": "send_email", "mode": "runs_on_its_own", "clientYes": "Jane Doe (client) on the 2026-11-10 call" } ] }. Returns every action after the change, in the same shape as the GET. A mode equal to the stored one (else the default) writes nothing. A new clientYes on a client workspace's send_email or send_linkedin that already runs on its own is a change: it is stored and audited and moves updatedAt; a missing one keeps the stored yes. Each change is recorded in the workspace's audit log (agent_permission.changed) before it is saved, so a save that then fails (500) keeps those lines: the log can show a change that was not saved, never a saved change without its line.
Errors (nothing is saved on any of them):
400 validation_failed, onedetails[]entry per problem, such aspermissions[1].action:required(permissionsmissing or empty),unknown_action,unknown_mode,duplicate_action,action_not_available(Kenso does not follow this action's mode yet),reply_agent_not_autonomous(book_meetingsset toruns_on_its_ownwhile the reply agent is off or not autonomous, even when that is already its mode),client_yes_required(send_emailorsend_linkedinchanged toruns_on_its_ownon a client workspace withoutclientYes, or with one over 500 characters).403 approval_requires_human:send_emailorsend_linkedinchanged toruns_on_its_own(a newclientYescounts) by a caller that is not a person signed in to the Kenso app (an agent, an API key, the MCP): theirruns_on_its_ownremoves a person's approval of each send. It comes before any 400. Switching one of them back toasks_first, and every other action either way, is open to every caller withworkspace_settings.404 not_found: the workspace does not have theagent_permissionsfeature.
Requires the workspace_settings permission.
Request body
application/json, optional.
| Field | Type | Required | Description |
|---|---|---|---|
permissions | array of AgentPermissionInputBody | optional | One entry per action to change, each action at most once. At least one entry. |
curl -X PATCH "https://api.ken.so/v1/agent-permission-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 '{
"permissions": [
{
"action": "send_email",
"mode": "asks_first",
"clientYes": "string"
}
]
}'Response 200
data is a AgentPermissionSettings.
Show the 2 response fields and an example
The fields and an example are also on this endpoint's Markdown page.
More in AI:AI runsAI linesAI line holdsAutonomous repliesAgent work settingsAgent workAgent sandbox connectionsAgent sandbox runsAgent sandbox automatic runsAI feedbackAll resources