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

# Agent work: Get the agent work queue

> **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 [Agent work](/docs/api/agent-work.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Get the agent work queue

`GET /v1/agent-work` - operationId `agent-work.get`

| Permission | Rate limit |
| --- | --- |
| Any workspace member except a Network member | 12,000 requests a minute per API key |

Returns every kind, always all eight in hand-out order, with its executor, the items waiting for your agent
(`waiting`), the items held by open claims (`claimed`), what holds the kind back (`heldBy`:
`billing_blocked`, `out_of_credits` or `ai_paused`, else null) and when an answer of it was last
accepted. With `campaignId`, the counts are that campaign's and `executor` is the campaign's: its override,
else the workspace's. Without it, `executor` is the workspace's switch and `waiting` counts every campaign
your agent takes, including a campaign that gives a kind to your agent while the workspace keeps it on
`kenso_ai`. So read `waiting`, not `executor`, to tell whether there is work. Kinds you may not write
are listed too. `scope` picks the campaigns the campaign kinds (`qualification`, `segmentation`,
`personalization`, `rewriting`) count: `all` (the default) is every campaign that is not deleted or
AI-paused, a Draft, finished or errored one included; `live` is only the campaigns Kenso's AI works on by
itself, so an unattended runner gets only work Kenso's AI would have done. The other kinds count the same in both.
The `waiting` counts are kept between reads and recounted in the background: `waitingCountedAt` says
when they were taken (up to 15 minutes ago). A kind whose count was not ready in time reads `waiting` 0 and
is named in `uncountedKinds`; ask again in a minute.

Errors:

- `400 validation_failed`: `scope` is not `all` or `live`.
- `404 not_found`: the workspace does not have the `agent_work` feature, or the campaign is not the
workspace's.
- `503 service_unavailable` with `Retry-After`: the agent work settings could not be read. Try again.

Open to any workspace member except a Client seat.

Needs the `agent_work` 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/agent-work/GET/v1/agent-work)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `campaignId` | query | integer (int64) | no | Optional. One campaign's counts instead of the workspace's. |
| `scope` | query | string | no | Optional. `all` (the default) or `live`: only the campaigns Kenso's AI works on by itself. |
| `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 `AgentWorkStatus`.

| Field | Type | Description |
| --- | --- | --- |
| `kinds` | array of AgentWorkKind | All eight kinds, always, in hand-out order (work with a deadline first). |
| `waitingCountedAt` | string (date-time) | When the `waiting` counts were taken, in UTC. Kenso keeps them between reads and recounts in the background, so they can be up to 15 minutes old; usually under a minute, or one poll behind for a caller that polls less often. Null when no kind waits for your agent. |
| `uncountedKinds` | array of string | The kinds your agent takes whose `waiting` was not counted for this answer, in hand-out order: counting them took longer than the read allows, or failed. Their `waiting` reads 0 and says nothing about their queue: ask again in a minute. Empty when every kind was counted. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/agent-work" \
  -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": {
    "kinds": [
      {
        "kind": "meeting_brief",
        "executor": "kenso_ai",
        "waiting": 1,
        "claimed": 1,
        "heldBy": "billing_blocked",
        "lastAcceptedAt": "2026-09-23T15:02:11Z"
      }
    ],
    "waitingCountedAt": "2026-09-23T15:02:11Z",
    "uncountedKinds": [
      "string"
    ]
  }
}
```

## Types

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

### AgentWorkKind

One kind of agent work.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `kind` | string | no | `meeting_brief`, `call_brief`, `workflow_prompt`, `qualification`, `segmentation`, `personalization`, `rewriting` or `background_ai`. |
| `executor` | string | no | `kenso_ai` or `my_agent`, as the agent work settings set it. |
| `waiting` | integer (int32) | no | Items waiting for your agent now. 0 for a kind on `kenso_ai` or one Kenso cannot hand out yet. |
| `claimed` | integer (int32) | no | Items held by open claims right now. |
| `heldBy` | string | no | Why nothing of this kind is handed out now, or null: `billing_blocked`, `out_of_credits` or `ai_paused`. A claim skips a held kind. |
| `lastAcceptedAt` | string (date-time) | no | When an answer of this kind was last accepted, in UTC; null when none was. |
