> 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: List lookalike seed suggestions

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

## List lookalike seed suggestions

`GET /v1/search/lookalike-seeds` - operationId `search.list-lookalike-seeds`

| Permission | Rate limit |
| --- | --- |
| Accounts view and Search view | 12,000 requests a minute per API key |

List companies from your own data that make good seeds for a lookalike search: your customers, your deals, the
companies that replied, a campaign's companies or your website visitors. Send a row's `domain` as a
`{"domain": ...}` seed in `POST /v1/search/companies` or `POST /v1/search/people`.

`source` is required and picks where the companies come from:

- `customers`: the workspace's customer accounts. `count` is the number of accounts with the domain,
normally 1.
- `crm`: companies on your opportunities and synced CRM deals. `count` is the number of deals. `stage` picks
`won` (the default), `open` (neither won nor lost) or `any`. `crm_won` still works and means
`crm` with `stage=won`.
- `interested`: companies whose people replied with interest. `count` is the number of contacts.
- `replies`: companies whose people sent a real reply, which leaves out automated replies, bounces and
out-of-office replies. `count` is the number of contacts.
- `campaign`: the companies of one campaign's live contacts. `count` is the number of contacts.
- `website_visitors`: companies behind human visits to the workspace's tracked website. `count` is the
number of visits.

`campaignId` is required with `campaign` and filters `interested` and `replies` to one
campaign. Sending it also needs Campaigns view. `since`, a `YYYY-MM-DD` day in UTC, keeps only replies
or visits on or after that day, for `interested`, `replies` and `website_visitors`.

Kenso reads at most the newest 20,000 replies, contacts or visits and groups them by company domain: the
contact's company domain, else the domain of their email address. A free email domain never becomes a seed. The
list holds up to 200 rows in one page, sorted by `count` from high to low, then by `domain`. An empty
list is normal. The call is free.

The lookalike filters need the `lookalikes` feature. Each takes `seeds`, `negatives` (up to 100
to steer away from), `mode` (`precise` or `broad`) and `minGrade` (1 to 5, default 2:
`precise` drops rows graded below it). `POST /v1/search/companies` takes `lookalike` with 1 to 100
company seeds, each a `companyId`, `domain`, `linkedInUrl` or `text` (up to 4,000
characters), plus `excludeDomains` and `includeNonB2b`. `POST /v1/search/people` takes either
`companyLookalike`, the same filter, or `lookalike` with 1 to 50 people seeds, each a `personId`
or `linkedInUrl`, plus `includeSeedCompanies`. Kenso excludes the workspace's do-not-contact and
customer domains. Rows come sorted by similarity, each with `lookalike`: a `score` from 0 to 100 and a
`grade` from 1 to 5, 5 the closest. The page lists each seed's outcome in `lookalikeSeeds`. A lookalike
search is a snapshot, so save or import its results by id, not by its filters.

Errors:

- `400 validation_failed`: `source` is missing or unknown, or you sent a parameter the source does not
take.
- `403 permission_denied`: you sent `campaignId` without Campaigns view.
- `404 not_found`: the campaign is not in this workspace or was deleted.

Requires Accounts view and Search view.

Needs the `lookalikes` 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/search/GET/v1/search/lookalike-seeds)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `source` | query | string | no | Required: `customers`, `crm`, `interested`, `replies`, `campaign` or `website_visitors`. `crm_won` is still accepted, as `crm` with `stage=won`. |
| `stage` | query | string | no | The deal stage, with `crm` only: `won` (default), `open` (neither won nor lost) or `any`. |
| `campaignId` | query | integer (int64) | no | The campaign to read. Required with `campaign`, and an optional filter with `interested` and `replies`. |
| `since` | query | string | no | With `interested`, `replies` and `website_visitors`: a day as `YYYY-MM-DD` (UTC). Only replies or visits on or after it count. |
| `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 list of `LookalikeSeed`. Each item has these fields. The response also carries `pagination`.

| Field | Type | Description |
| --- | --- | --- |
| `domain` | string | The company's domain, such as `acme.com`. Send it as a `{"domain": ...}` seed. |
| `name` | string | The company's name as the workspace knows it. Omitted when unknown. |
| `count` | integer (int32) | How strongly the source ties the company to you: deals at the stage asked for (`crm`, `crm_won`), contacts marked Interested (`interested`), contacts who replied (`replies`), the campaign's contacts at the company (`campaign`), visits (`website_visitors`), or customer accounts with the domain, normally 1 (`customers`). |

### Request

```bash
curl -X GET "https://api.ken.so/v1/search/lookalike-seeds" \
  -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": [
    {
      "domain": "acme.com",
      "name": "string",
      "count": 1
    }
  ],
  "pagination": {
    "nextCursor": "eyJpZCI6ODE1fQ",
    "hasMore": true,
    "totalCount": 1
  }
}
```
