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

# People and company search: Import people into 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 [People and company search](/docs/api/search.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Import people into a campaign

`POST /v1/search/imports` - operationId `search.create-import`

| Permission | Rate limit |
| --- | --- |
| Campaigns edit and Search view and the `import` permission | 480 requests a minute per API key |

Add Search people to a campaign as contacts. Pick the people by id, or import every match of a people search.

Send `campaignId` and exactly one of `personIds` or `searchFilters`. `personIds` must not be
empty. `searchFilters` is a people search body, and Kenso imports its matches up to `limit`. A lookalike
search cannot be imported by its filters: send the people it found as `personIds`. With
`inLinkedInConnections: true` in `searchFilters`, the import takes only the workspace's LinkedIn
connections, and needs the `linkedin_network` or `linkedin_connections_import` feature. To see first
how many of the people Kenso already holds an email for, call `POST /v1/search/imports/preview`.

The import runs in the background and fills the campaign in batches. The call answers `202` with the import
job's `jobId` and `status`. Poll `GET /v1/search/imports/{importId}` with that `jobId`.

On Kenso Lifetime, the people an import adds count against the license's contacts and its people results for the
day. When either is already used up, or the license is no longer active, the call refuses at once and starts no
import (a license that is not active answers `402 workspace_read_only`, with the refusal code
`WORKSPACE_READ_ONLY`). Otherwise each
batch counts as it is added: when the day's people results run out partway, the import waits and goes on after
00:00 UTC. When the license's contacts run out, the import stops.

Errors:

- `400 validation_failed`: `campaignId` is missing, both or neither of `personIds` and
`searchFilters` are sent, `personIds` is empty, `searchFilters` is not an object or its
`inLinkedInConnections` is not a boolean, or `limit` is below 1.
- `400 lookalike_not_storable`: `searchFilters` carries a lookalike filter.
- `400 validation_failed`: the workspace is a developer sandbox. A sandbox holds seeded and test data only,
so search imports are not available in it. Contacts you upload from a CSV file are still imported.
- `401 unauthenticated`: the API key belongs to no member. An import runs as a member.
- `402 plan_required`: `searchFilters` holds a funding filter (as on `POST /v1/search/people`) and
the workspace's plan does not include funding signals. `error.refusal` carries the code
`PLAN_FEATURE_NOT_AVAILABLE` and the feature `funding_signals`.
- `402 plan_limit_reached`: on Kenso Lifetime, the license's contacts or the day's people results are
already used up. `error.refusal` carries the code `LIFETIME_CONTACT_LIMIT_REACHED` or
`LIFETIME_PEOPLE_RESULT_LIMIT_REACHED`; the people results come back at 00:00 UTC.
- `403 feature_disabled`: `inLinkedInConnections` needs `linkedin_network` or
`linkedin_connections_import`.
- `404 not_found`: the campaign is not in this workspace.
- `503 service_unavailable`: the workspace's LinkedIn connections could not be read. Try again.

Requires Campaigns edit and the `import` permission, plus Search view.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/search/POST/v1/search/imports)

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

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `campaignId` | integer (int64) | no | The campaign in this workspace that receives the people. |
| `personIds` | array of integer (int64) | no | The people to import, by the `kenId` of each people search result. |
| `searchFilters` | object | no | A people search body, as sent to `POST /v1/search/people`. Imports every match, up to `limit`. |
| `limit` | integer (int32) | no | The most people a `searchFilters` import adds. |

### Response 202

`data` is a `SearchImportJob`.

| Field | Type | Description |
| --- | --- | --- |
| `jobId` | integer (int64) | The import's id. Send it as `importId` to `GET /v1/search/imports/{importId}`. |
| `status` | string | The import's status when it starts: `Queued`. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/search/imports" \
  -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": 812,
  "personIds": [
    812
  ],
  "searchFilters": null,
  "limit": 1
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "jobId": 812,
    "status": "string"
  }
}
```
