> 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: Preview an import

> **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).

## Preview an import

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

| Permission | Rate limit |
| --- | --- |
| Campaigns view and Search view | 200 requests a minute per API key |

See how many people an import would take and how many of them Kenso already holds a verified email for. On a paid
plan, a person whose email Kenso already holds costs no email find, so use this to estimate an import's cost.

Send the selection you would send to `POST /v1/search/imports`, without `campaignId`: exactly one of
`personIds` or `searchFilters`, with `limit` (5,000 when omitted). The answer holds
`personCount`, `checkedCount` and `kenEmailCount`. Kenso checks at most the first 500 people.
`inLinkedInConnections: true` in `searchFilters` needs the `linkedin_network` or
`linkedin_connections_import` feature, as on the import.

The preview imports nothing and does not count against `searchBrowseRows`.

Errors:

- `400 validation_failed`: 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.
- `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`.
- `403 feature_disabled`: `inLinkedInConnections` needs `linkedin_network` or
`linkedin_connections_import`.
- `503 service_unavailable`: Search could not return every person to check (Kenso fails the preview rather
than return a lower count), or the workspace's LinkedIn connections could not be read. Try again.

Requires Campaigns view, plus Search view.

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

### 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 |
| --- | --- | --- | --- |
| `personIds` | array of integer (int64) | no | The people the import would take, by the `kenId` of each people search result. |
| `searchFilters` | object | no | A people search body, as sent to `POST /v1/search/people`. Previews its matches up to `limit`. |
| `limit` | integer (int32) | no | The most people a `searchFilters` import would add. Default 5,000. |

### Response 200

`data` is a `SearchImportPreview`.

| Field | Type | Description |
| --- | --- | --- |
| `personCount` | integer (int64) | People the import would take: the distinct `personIds` (at most 5,000, the import's cap for picks), or the filter's matches up to `limit` (5,000 when absent). |
| `checkedCount` | integer (int32) | People checked against Kenso's emails: at most the first 500, in import order. |
| `kenEmailCount` | integer (int32) | Of the checked people, how many Kenso already holds a verified email for. |

### Request

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

### Example response

```json
{
  "success": true,
  "data": {
    "personCount": 1,
    "checkedCount": 1,
    "kenEmailCount": 1
  }
}
```
