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

# Email finder

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

An email find looks up one person's work email from their name and company, in any country. Kenso checks its own email database first, then outside email providers, and verifies each address before it keeps one. A find costs 1 credit when Kenso's own provider access finds a valid email. It costs nothing when it finds none, or when the workspace's own provider key finds the email. A find runs in the background: start it with `POST /v1/email-finds` and poll `GET /v1/email-finds/{emailFindId}`.

Prospecting data. 2 endpoints under `https://api.ken.so`. Every request sends `Authorization: Bearer <your API key>` and `Ken-Version: 2026-11-02`: see [Authentication](/docs/authentication.md), [Workspaces](/docs/workspaces.md) and [Errors](/docs/errors.md). OpenAPI for this resource only: [/docs/api/email-finds/openapi.json](/docs/api/email-finds/openapi.json).

- `POST /v1/email-finds` - Find a person's email (`email-finds.create`): [/docs/api/email-finds/create.md](/docs/api/email-finds/create.md)
- `GET /v1/email-finds/{emailFindId}` - Get an email find (`email-finds.get`): [/docs/api/email-finds/get.md](/docs/api/email-finds/get.md)

## Find a person's email

`POST /v1/email-finds` - operationId `email-finds.create`

| Permission | Credits | Rate limit |
| --- | --- | --- |
| Search edit | 1 credit per valid email (`email_found`) | 30 requests a minute and 500 a day per workspace (Free plan: 3 a minute and 50 a day) |

Start a lookup of one person's work email from their name and company. The call returns at once and the find runs
in the background.

Send a name, as `fullName` or as `firstName` and `lastName`, and at least one of
`companyDomain` and `linkedinUrl`. `companyDomain` is the company's website domain, such as
`acme.fr`. `companyName` is optional. With only `linkedinUrl`, Kenso uses the domain of the
person's current company in Search. When Search does not know that company, the find ends `not_found` at no
charge.

The call answers `202` with the find in status `queued` and a `Location` header. Most finds end
within a minute: poll `GET /v1/email-finds/{emailFindId}`.

Kenso saves the person in the workspace, outside any account. A repeat find for the same name at the same domain
reuses that person, also when it adds `linkedinUrl`, so it makes no duplicate. When that person already has
the email, the find comes back `found` at no charge, with verification `unverified`. When a find for
the same person is still running, the call returns that find instead of starting another. Calls sent at the same
moment are not merged, so send one call per person and poll it.

A workspace can start 30 finds a minute and 500 a day. Refused calls and calls that return a running find do not
count.

Errors:

- `400 validation_failed`: the name is missing, neither `companyDomain` nor `linkedinUrl` is
sent, or `companyDomain` is a free mail, social or link host (detail code `invalid_domain`).
- `402 plan_limit_reached`: the workspace is out of credits, and nothing runs. `error.refusal` has the
details.
- `403 permission_denied`: you work only your own accounts, and a found person sits on no account. Ask a
workspace admin.
- `409 conflict`: a find for this person at another company is still running (detail code
`active_find`). Try again once it ends.
- `429 quota_exceeded`: the workspace started 30 finds this minute or 500 today. Wait for the time in
`Retry-After`.

Requires Search edit.

Needs the `email_finder` 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/email-finds/POST/v1/email-finds)

### 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 |
| --- | --- | --- | --- |
| `fullName` | string | no | The person's full name. Send it, or `firstName` and `lastName`. |
| `firstName` | string | no | The person's first name, sent with `lastName` instead of `fullName`. |
| `lastName` | string | no | The person's last name, sent with `firstName` instead of `fullName`. |
| `companyDomain` | string | no | The company's website domain, such as `acme.fr`. Optional when you send `linkedinUrl`. |
| `companyName` | string | no | The company's name. Optional. |
| `linkedinUrl` | string | no | The person's LinkedIn profile URL, the strongest match signal. Optional when you send `companyDomain`. |

### Response 202

`data` is a `EmailFind`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | The find's id. |
| `personId` | integer (int64) | The person in the workspace that the find saves the email to. |
| `status` | string | The find's state: `queued`, `running` or `paused` while it works, then `found`, `not_found` or `failed`. |
| `pausedReason` | string | Why a paused find waits: `credits` when the workspace ran out, or `member_limit` when the member reached their monthly credit limit. Null unless paused. |
| `email` | string | The email, when found. |
| `verification` | EmailFindVerification | How the found email was checked. Null until the find ends `found`. |
| `provider` | string | Where the email came from: `database` for Kenso's email database, `kenfinder` for Kenso's own email finder, `existing` when the person already had it, or the name of the outside email provider that found it. |
| `companyDomain` | string | The company domain the find searched. |
| `costCredits` | integer (int32) | Credits charged: 1 when Kenso's own provider access found the email, else 0. |
| `error` | string | Why the find ended `not_found` or `failed`, in plain words. |
| `createdAt` | string (date-time) | When the find started, UTC. |
| `completedAt` | string (date-time) | When the find ended, UTC. Null while it works. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/email-finds" \
  -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 '{
  "fullName": "Jane Doe",
  "firstName": "Jane",
  "lastName": "Doe",
  "companyDomain": "acme.fr",
  "companyName": "Acme",
  "linkedinUrl": "https://example.com"
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "id": 812,
    "personId": 812,
    "status": "queued",
    "pausedReason": "string",
    "email": "jane@example.com",
    "verification": {
      "status": "string",
      "verifiedBy": "string"
    },
    "provider": "string",
    "companyDomain": "example.com",
    "costCredits": 1,
    "error": "string",
    "createdAt": "2026-09-23T15:02:11Z",
    "completedAt": "2026-09-23T15:02:11Z"
  }
}
```

## Get an email find

`GET /v1/email-finds/{emailFindId}` - operationId `email-finds.get`

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

Get one email find and its result. Poll it after `POST /v1/email-finds` until the find ends.

`status` is `queued`, `running` or `paused` while the find works. A paused find waits for
credits: `pausedReason` is `credits` when the workspace ran out, or `member_limit` when you reached
your monthly credit limit. The find then ends `found`, `not_found` or `failed`. On
`not_found` or `failed`, `error` says why, and you can start a failed find again.

A found find carries `email`, `provider` (where Kenso found it) and `verification`: its
`status` (`safe`, `verified` or `unverified`) and `verifiedBy`. `costCredits` is what
the find charged.

Errors:

- `403 permission_denied`: you work only your own accounts, and a found person sits on no account.
- `404 not_found`: no find has this id in this workspace.

Requires Search view.

Needs the `email_finder` 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/email-finds/GET/v1/email-finds/%7BemailFindId%7D)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `emailFindId` | path | integer (int64) | yes | The find's id, from `POST /v1/email-finds`. |
| `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 `EmailFind`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | The find's id. |
| `personId` | integer (int64) | The person in the workspace that the find saves the email to. |
| `status` | string | The find's state: `queued`, `running` or `paused` while it works, then `found`, `not_found` or `failed`. |
| `pausedReason` | string | Why a paused find waits: `credits` when the workspace ran out, or `member_limit` when the member reached their monthly credit limit. Null unless paused. |
| `email` | string | The email, when found. |
| `verification` | EmailFindVerification | How the found email was checked. Null until the find ends `found`. |
| `provider` | string | Where the email came from: `database` for Kenso's email database, `kenfinder` for Kenso's own email finder, `existing` when the person already had it, or the name of the outside email provider that found it. |
| `companyDomain` | string | The company domain the find searched. |
| `costCredits` | integer (int32) | Credits charged: 1 when Kenso's own provider access found the email, else 0. |
| `error` | string | Why the find ended `not_found` or `failed`, in plain words. |
| `createdAt` | string (date-time) | When the find started, UTC. |
| `completedAt` | string (date-time) | When the find ended, UTC. Null while it works. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/email-finds/812" \
  -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": {
    "id": 812,
    "personId": 812,
    "status": "queued",
    "pausedReason": "string",
    "email": "jane@example.com",
    "verification": {
      "status": "string",
      "verifiedBy": "string"
    },
    "provider": "string",
    "companyDomain": "example.com",
    "costCredits": 1,
    "error": "string",
    "createdAt": "2026-09-23T15:02:11Z",
    "completedAt": "2026-09-23T15:02:11Z"
  }
}
```

## Types

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

### EmailFindVerification

How a found email was checked.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `status` | string | yes | The check's result: `safe` when an email verifier accepted the mailbox, `verified` when the source that found the email verified it, or `unverified` when nobody checked it. |
| `verifiedBy` | string | no | Who checked the email: the email verifier, or the provider whose own check stood. |

All resources: [/docs.md](/docs.md).
