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

# Contacts: Add contacts 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 [Contacts](/docs/api/contacts.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Add contacts to a campaign

`POST /v1/campaigns/{campaignId}/contacts` - operationId `contacts.create`

| Permission | Rate limit |
| --- | --- |
| Campaigns edit | 480 requests a minute per API key |

Adds up to 1,000 people to a campaign, or updates them when the campaign already has them. A row matches an
existing contact of the campaign by email, or by LinkedIn URL for a row without an email in a campaign
with only LinkedIn steps. `results` reports each row in request order: `created`,
`updated`, `skipped` or `failed`, with a `reason` and `message` when the row
was not saved.

Kenso saves the rows in batches of 100. A later batch can fail after earlier ones saved, and a retry of the
same body is safe. A row on the workspace blocklist is not saved: it is `failed` with reason
`blocklisted`. A row that matches a contact already marked do-not-contact is `updated` with
`sendable` false. A contact the plan has no allowance left for is added unqualified, with
`sendable` false.

On Kenso Lifetime, the new contacts in each batch count against the license's contacts (one pool across its
workspaces). When a batch would pass them, the call still answers 200: every row of that batch, updates
included, is `failed` with reason `limit_reached`, and its `message` starts with
`[LIFETIME_CONTACT_LIMIT_REACHED]`. Batches saved before it stay saved. A batch that only updates contacts
the campaign already has is not refused.

A row with `useKenEmail` and no email takes a recently verified address from Kenso's email database when
it has one, free, for the first 25 such rows of the request. A row with `emailValidity`
`safe` qualifies a new contact in a campaign without AI qualification and uses one contact from
the plan's allowance.

A row with a malformed `customImageUrl` or `customVideo` or a bad custom variable key fails before
anything is written. When the workspace does not have campaign images or campaign videos, the contact
is saved and the row fails. A batch that would take the campaign past 50 custom variables fails every
row in it.

Errors:

- `400 validation_failed`: `contacts` is missing or empty, or holds more than 1,000 rows.
- `404 not_found`: no campaign with this id in the workspace.

Requires Campaigns edit.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/contacts/POST/v1/campaigns/%7BcampaignId%7D/contacts)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `campaignId` | path | integer (int64) | yes | The campaign to add the contacts to. |
| `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 |
| --- | --- | --- | --- |
| `contacts` | array of CreateCampaignContactRequest | yes | Required. From 1 to 1,000 contacts, processed in request order. |

### Response 200

`data` is a `ContactBulkResult`.

| Field | Type | Description |
| --- | --- | --- |
| `succeeded` | array of integer (int64) | Ids of the contacts the call changed or saved. |
| `failed` | array of ContactBulkFailure | One entry for each contact or row the call did not change, with the reason. |
| `results` | array of ContactCreateRowResult | One item per input row of `POST /v1/campaigns/{campaignId}/contacts`, in request order. Only that call returns it. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/campaigns/812/contacts" \
  -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 '{
  "contacts": [
    {
      "email": "amanda.chen@northwind.example.com",
      "firstName": "Amanda",
      "lastName": "Chen",
      "title": "VP of Engineering",
      "linkedInUrl": "https://www.linkedin.com/in/amanda-chen-northwind",
      "companyName": "Northwind Labs",
      "companyDomain": "northwind.example.com",
      "customVariables": {
        "open_roles": "12 engineering roles"
      },
      "emailValidity": "safe"
    },
    {
      "email": "priya.shah@northwind.example.com",
      "firstName": "Priya",
      "lastName": "Shah",
      "title": "Engineering Manager",
      "companyName": "Northwind Labs",
      "companyDomain": "northwind.example.com"
    }
  ]
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "succeeded": [
      90125,
      90126
    ],
    "failed": [
      {
        "id": 90131,
        "error": {
          "code": "not_found",
          "message": "No contact with this id in the workspace."
        }
      }
    ]
  }
}
```

## Types

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

### CreateCampaignContactRequest

One contact to add to a campaign. A row whose email the campaign already has updates that contact.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `email` | string | no | The contact's email address. Required, unless the campaign has only LinkedIn steps: then send an email or a `linkedin.com/in/` profile URL. |
| `firstName` | string | yes | First name. Required. |
| `lastName` | string | yes | Last name. Required. |
| `title` | string | no | Job title. |
| `linkedInUrl` | string | no | LinkedIn profile URL, such as `https://www.linkedin.com/in/ada-lovelace`. Kenso drops a Sales Navigator id URL (`linkedin.com/in/ACw...`), because no LinkedIn step can reach it. |
| `companyName` | string | no | Company name. A row needs this or `companyDomain`. |
| `companyDomain` | string | no | Company website domain, such as `acme.com`. A row needs this or `companyName`. |
| `customImageUrl` | string | no | Public https URL of the contact's own image, shown in emails as `{{custom_image}}`. Kenso downloads and hosts it. An empty string clears it. Needs campaign images on the workspace. |
| `customVideo` | string | no | The contact's own video, shown in emails as `{{custom_video}}`: a Loom, YouTube, Vimeo, Wistia, Vidyard, Sendspark or HeyGen share link or embed code. An empty string clears it. Needs campaign videos on the workspace. |
| `customVariables` | map of string | no | Custom variables as an object of string values, such as `{ "rd_first_line": "Loved your talk" }`. Kenso normalizes each key like a CSV column name and merges the values into the contact's custom variables. A key new to the campaign joins its custom variables with AI context off. A null or empty value removes that key from an existing contact. At most 50 keys. |
| `emailValidity` | string, one of: unknown, invalid, risky, verified, safe, catch_all, verification_error | no | Optional. Send `safe` for an email you already verified. In a campaign without AI qualification, Kenso then qualifies a new contact and spends one contact allowance. Omitted keeps the verdict Kenso already has for an existing email. `verification_error` is refused. |
| `useKenEmail` | boolean | no | True on a row with no email: Kenso fills the email from its own email database when it holds a recently verified address for the person at the company's domain. Free, for the first 25 such rows of a request. A row still without an email fails, unless the campaign has only LinkedIn steps. |

### ContactBulkFailure

One contact or row a bulk call did not change, and why.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | integer (int64) | no | The contact id. Omitted for a row Kenso refused before saving it. |
| `index` | integer (int32) | no | The row's position in the request, from 0. Only on `POST /v1/campaigns/{campaignId}/contacts`. |
| `error` | ContactBulkError | no | Why the contact or row failed. |

### ContactCreateRowResult

What Kenso did with one row of `POST /v1/campaigns/{campaignId}/contacts`.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `index` | integer (int32) | no | The row's position in `contacts`, from 0. |
| `status` | string | no | What Kenso did with the row: `created` (a new contact), `updated` (the campaign already had the contact), `skipped` or `failed`. |
| `id` | integer (int64) | no | The contact id, when Kenso saved the row. |
| `reason` | string | no | Why a row was skipped or failed: `duplicate` (an earlier row or an existing contact), `blocklisted` (on the workspace blocklist), `already_contacted` (in another campaign, or emailed inside the campaign's recently-emailed window), `limit_reached` (the plan's contact allowance is used up), `invalid_email`, `excluded` (a campaign exclusion rule such as an excluded country), `validation` (another field rule) or `other`. On Kenso Lifetime, `limit_reached` also means the license's contacts (one pool across its workspaces) are used up. |
| `message` | string | no | For a skipped or failed row, a readable explanation. |
| `sendable` | boolean | no | On a saved row, false when the contact will not get campaign steps: it is do-not-contact, or Kenso added it unqualified, for example because no contact allowance was left. |

### ContactBulkError

The error for one contact or row of a bulk call.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `code` | string | no | A stable error code, such as `not_found`, `validation_failed`, `not_deleted`, `not_paused`, `already_stopped`, `do_not_contact`, `video_in_use` or `internal_error`. Each operation lists the codes it returns. |
| `message` | string | no | A readable explanation. |
