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

# LinkedIn job search

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

LinkedIn job search on request: the caller's own LinkedIn seat first (free), Kenso's data provider without one (charged in credits per delivered row), and ken-jobs merged in either way. 404 unless the workspace has `linkedin_job_search` on. Reads need Search view, as job postings; a search needs Search edit, as an email find, because it can spend credits. Never a Client seat.

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/linkedin-job-searches/openapi.json](/docs/api/linkedin-job-searches/openapi.json).

- `POST /v1/linkedin-job-searches` - Search LinkedIn jobs (`linkedin-job-searches.create`): [/docs/api/linkedin-job-searches/create.md](/docs/api/linkedin-job-searches/create.md)
- `GET /v1/linkedin-job-searches/{linkedInJobSearchId}` - Get a LinkedIn job search (`linkedin-job-searches.get`): [/docs/api/linkedin-job-searches/get.md](/docs/api/linkedin-job-searches/get.md)

## Search LinkedIn jobs

`POST /v1/linkedin-job-searches` - operationId `linkedin-job-searches.create`

| Permission | Credits | Rate limit |
| --- | --- | --- |
| Search edit | Spends credits, price not on the rate card yet (`social_data_record`) | 25 requests a day per workspace |

Runs one search. With your own connected LinkedIn seat it reads LinkedIn there, free (`via: seat`), and pages
with `nextCursor`. Without a seat that can read now (none, paused, LinkedIn throttling it or reporting it
unavailable) it goes to Kenso's data provider in the same call (`via: social_data`), charged 0.15 credits a
delivered row (about 3.75 credits per 25 rows; free when the workspace uses its own provider key), with no next
cursor; with that provider off it answers ken-jobs rows only (`via: ken_jobs_only`). ken-jobs rows are merged
after the LinkedIn rows on a first page. Answers 201 when done, or 202 with `status: running` while Kenso is
still collecting the data (up to about a minute in this call): read it with `linkedin-job-searches.get`. The
same search within 24 hours answers from the cache, with no read and `creditsCharged` 0. While the first is
still running, a repeat answers that search as it is now instead of starting another, and the rows are charged
once. Errors: `400 validation_failed` (also a location LinkedIn does not know),
`402 insufficient_credits` (provider path only), `409 linkedin_seat_required` (a seat cursor, or
companies that are all LinkedIn company ids, when no seat can read), `429 rate_limited` (your seat is pacing
its reads: wait `Retry-After`, never a paid fallback) or `429 quota_exceeded` (25 searches a day per
workspace), `503 service_unavailable` when LinkedIn did not answer. Needs Search edit.
A workspace key gets `403 forbidden`: a search runs on a member's LinkedIn seat and records who asked, and
a workspace key is not a person.

Needs the `linkedin_job_search` 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/linkedin-job-searches/POST/v1/linkedin-job-searches)

### 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 |
| --- | --- | --- | --- |
| `keywords` | string | yes | Required. The job title or words to search, at most 200 characters: `sdr`, `account executive`. |
| `location` | string | no | Free text, at most 200 characters: `Germany`, `Berlin`, `San Francisco Bay Area`. |
| `companies` | array of string | no | Up to 10 company names, or LinkedIn company ids (digits) on the seat path. |
| `datePosted` | string | no | `past_day`, `past_week` or `past_month`. |
| `workplaceType` | array of string | no | `on_site`, `remote`, `hybrid`. |
| `seniority` | array of string | no | `internship`, `entry_level`, `associate`, `mid_senior_level`, `director`, `executive`. |
| `limit` | integer (int32) | no | LinkedIn rows to read, 1 to 100. Default 25. |
| `cursor` | string | no | The `nextCursor` of an earlier seat search with the same filters. |

### Response 201

Also answers `202`. `data` is a `LinkedInJobSearch`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | string | `ljs_` and 32 hex digits. Kept for 24 hours. |
| `status` | string | `completed`, `running` (Kenso is still collecting the data: read it again with get) or `failed` (the read failed; rows hold the ken-jobs rows and nothing was charged). |
| `via` | string | `seat` (your own LinkedIn seat, free), `social_data` (charged per delivered row) or `ken_jobs_only`. |
| `rows` | array of LinkedInJobSearchRow | LinkedIn rows first, then ken-jobs rows that are not the same job. |
| `nextCursor` | string | Only on a seat search with more rows: send it as `cursor` with the same filters. |
| `creditsCharged` | number (double) | Credits charged for the rows Kenso's data provider delivered (0.15 a row, free on the workspace's own provider key). On create, the credits charged so far: 0 for an answer from the cache. On get, the credits the search charged. 0 on the seat, on ken-jobs and on the workspace's own provider key. A workspace exempt from billing sees what the rows cost at list price, though nothing is debited. |
| `createdAt` | string (date-time) |  |

### Request

```bash
curl -X POST "https://api.ken.so/v1/linkedin-job-searches" \
  -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 '{
  "keywords": "sdr",
  "location": "Germany",
  "companies": [
    "string"
  ],
  "datePosted": "past_day",
  "workplaceType": [
    "on_site"
  ],
  "seniority": [
    "internship"
  ],
  "limit": 1,
  "cursor": "eyJpZCI6ODE1fQ"
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "id": "ljs_2bX9kq4LmR7tW3vY",
    "status": "string",
    "via": "string",
    "rows": [
      {
        "source": "linkedin",
        "id": "string",
        "title": "string",
        "company": {
          "name": "string",
          "linkedinUrl": "https://example.com",
          "domain": "example.com"
        },
        "location": "string",
        "postedAt": "2026-09-23T15:02:11Z",
        "url": "https://example.com",
        "easyApply": true,
        "fewApplicants": true,
        "applicants": 1,
        "description": "string"
      }
    ],
    "nextCursor": "eyJpZCI6ODE1fQ",
    "creditsCharged": 0.5,
    "createdAt": "2026-09-23T15:02:11Z"
  }
}
```

## Get a LinkedIn job search

`GET /v1/linkedin-job-searches/{linkedInJobSearchId}` - operationId `linkedin-job-searches.get`

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

One search of this workspace, kept 24 hours. While `status` is `running` each read checks the provider
once and answers 202; when it is ready the rows are merged in, charged once, and it answers 200
`completed`. Another workspace's id, or an expired one, is 404 `not_found`.

Needs the `linkedin_job_search` 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/linkedin-job-searches/GET/v1/linkedin-job-searches/%7BlinkedInJobSearchId%7D)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `linkedInJobSearchId` | path | string | yes |  |
| `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

Also answers `202`. `data` is a `LinkedInJobSearch`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | string | `ljs_` and 32 hex digits. Kept for 24 hours. |
| `status` | string | `completed`, `running` (Kenso is still collecting the data: read it again with get) or `failed` (the read failed; rows hold the ken-jobs rows and nothing was charged). |
| `via` | string | `seat` (your own LinkedIn seat, free), `social_data` (charged per delivered row) or `ken_jobs_only`. |
| `rows` | array of LinkedInJobSearchRow | LinkedIn rows first, then ken-jobs rows that are not the same job. |
| `nextCursor` | string | Only on a seat search with more rows: send it as `cursor` with the same filters. |
| `creditsCharged` | number (double) | Credits charged for the rows Kenso's data provider delivered (0.15 a row, free on the workspace's own provider key). On create, the credits charged so far: 0 for an answer from the cache. On get, the credits the search charged. 0 on the seat, on ken-jobs and on the workspace's own provider key. A workspace exempt from billing sees what the rows cost at list price, though nothing is debited. |
| `createdAt` | string (date-time) |  |

### Request

```bash
curl -X GET "https://api.ken.so/v1/linkedin-job-searches/01JC8Z3K6Q2W4M7N9P5R1T3V5X" \
  -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": "ljs_2bX9kq4LmR7tW3vY",
    "status": "string",
    "via": "string",
    "rows": [
      {
        "source": "linkedin",
        "id": "string",
        "title": "string",
        "company": {
          "name": "string",
          "linkedinUrl": "https://example.com",
          "domain": "example.com"
        },
        "location": "string",
        "postedAt": "2026-09-23T15:02:11Z",
        "url": "https://example.com",
        "easyApply": true,
        "fewApplicants": true,
        "applicants": 1,
        "description": "string"
      }
    ],
    "nextCursor": "eyJpZCI6ODE1fQ",
    "creditsCharged": 0.5,
    "createdAt": "2026-09-23T15:02:11Z"
  }
}
```

## Types

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

### LinkedInJobSearchRow

One job row.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `source` | string | no | `linkedin` or `ken_jobs`. |
| `id` | string | no | A LinkedIn job id on a linkedin row (open it with `linkedin-jobs.get`), the ken-jobs id otherwise. |
| `title` | string | no |  |
| `company` | LinkedInJobCompany | no |  |
| `location` | string | no |  |
| `postedAt` | string (date-time) | no |  |
| `url` | string | no |  |
| `easyApply` | boolean | no |  |
| `fewApplicants` | boolean | no |  |
| `applicants` | integer (int32) | no | Rows from Kenso's data provider only. |
| `description` | string | no | Rows from Kenso's data provider only; a seat row's description is `linkedin-jobs.get`. |

### LinkedInJobCompany

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | no |  |
| `linkedinUrl` | string | no |  |
| `domain` | string | no |  |

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