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

# Accounts: Add the account's people with no 1:1 touch planned to a campaign

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

## Add the account's people with no 1:1 touch planned to a campaign

`POST /v1/accounts/{accountId}/add-to-campaign` - operationId `accounts.add-to-campaign`

| Permission | Rate limit |
| --- | --- |
| Accounts edit and Campaigns edit | 4,800 requests a minute per API key |

Body: `campaignId` (required: a campaign of this workspace that is not archived or completed) and
`who`: `not_yet_contacted` (default: people nobody ever sent a 1:1 touch, a member mailbox email or a
campaign email) or `everyone_mapped`. A person joins when they are a stakeholder with an email, targeted and
not a blocker. The economic buyer, anyone with a 1:1 touch planned and anyone touched in the last 30 days stay
out, and so does anyone another open campaign already holds, so an account's people join one campaign (the
first add wins). People are imported like a lead upload (dedup, blocklist, lead credits); the campaign's own
sequence sends to them. Returns `added`, `alreadyIn` (people the campaign already had) and
`skipped` (people the rules or another campaign held back, or the import left out), and writes "N people with no 1:1 touch added to {campaign}" on the
account timeline when it added anyone. Running it again adds nobody twice. An account or campaign not in the
workspace is `404 not_found`; an archived or completed campaign is `409 invalid_state` with
`campaign_closed`. When the plan's lead credits refuse the import before anyone joined, the answer is
`402 plan_limit_reached` with the refusal. With account scope `own`, an account the caller does not
own is `404`.
Requires accounts edit and campaigns edit, and the `nurture_air_cover` feature.

Needs the `accounts` feature on your workspace. Until it is on, calls answer 404. Needs the `nurture_air_cover` 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/accounts/POST/v1/accounts/%7BaccountId%7D/add-to-campaign)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `accountId` | path | integer (int64) | yes |  |
| `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 |
| --- | --- | --- | --- |
| `campaignId` | integer (int64) | yes | The campaign the people join, a live campaign of this workspace that is not archived or completed. Required. |
| `who` | string | no | not_yet_contacted (default): people nobody has touched yet. everyone_mapped: every mapped person not touched in 30 days. |

### Response 200

`data` is a `AccountCampaignPeople`.

| Field | Type | Description |
| --- | --- | --- |
| `accountId` | integer (int64) |  |
| `campaignId` | integer (int64) |  |
| `campaignName` | string |  |
| `added` | integer (int32) | People added to the campaign. |
| `alreadyIn` | integer (int32) | People already in the campaign. |
| `skipped` | integer (int32) | People the rules held back (the economic buyer, a 1:1 touch planned, touched recently), people another open campaign already holds, or the import left out (a duplicate elsewhere in the workspace, a rejected row). |

### Request

```bash
curl -X POST "https://api.ken.so/v1/accounts/812/add-to-campaign" \
  -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 '{
  "campaignId": 4821,
  "who": "not_yet_contacted"
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "accountId": 6120,
    "campaignId": 4821,
    "campaignName": "Q4 SaaS founders",
    "added": 3,
    "alreadyIn": 1,
    "skipped": 1
  }
}
```
