> 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-jobs/openapi.json](/docs/api/linkedin-jobs/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# LinkedIn jobs

> **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 LinkedIn job's detail through the caller's own LinkedIn seat. 404 unless the workspace has `linkedin_job_search` on. Same access as job postings, and never a Client seat.

Prospecting data. 1 endpoint 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-jobs/openapi.json](/docs/api/linkedin-jobs/openapi.json).

- `GET /v1/linkedin-jobs/{linkedInJobId}` - Get a LinkedIn job's detail (`linkedin-jobs.get`): [/docs/api/linkedin-jobs/get.md](/docs/api/linkedin-jobs/get.md)

## Get a LinkedIn job's detail

`GET /v1/linkedin-jobs/{linkedInJobId}` - operationId `linkedin-jobs.get`

| Permission | Rate limit |
| --- | --- |
| Search view | 240 requests a minute per API key |

The description, applicant and view counts, state and apply page of one LinkedIn job (the `id` of a
`linkedin` row), read on your own connected LinkedIn seat: free, one read of the seat's daily budget. Errors:
`409 linkedin_seat_required` when you have no seat that can read now (rows from Kenso's data provider already
carry the description), `429 rate_limited` while the seat paces its reads, `404 not_found` when LinkedIn
has no such job, `503 service_unavailable` when LinkedIn did not answer.

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-jobs/GET/v1/linkedin-jobs/%7BlinkedInJobId%7D)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `linkedInJobId` | 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

`data` is a `LinkedInJob`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | string |  |
| `title` | string |  |
| `companyName` | string |  |
| `location` | string |  |
| `state` | string | LinkedIn's state in lower case: `open`, `closed`, ... |
| `description` | string |  |
| `applicantCount` | integer (int32) |  |
| `viewCount` | integer (int32) |  |
| `postedAt` | string (date-time) |  |
| `applyUrl` | string | The employer's own apply page, when the job has one. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/linkedin-jobs/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": "string",
    "title": "string",
    "companyName": "Acme",
    "location": "string",
    "state": "string",
    "description": "string",
    "applicantCount": 1,
    "viewCount": 1,
    "postedAt": "2026-09-23T15:02:11Z",
    "applyUrl": "https://example.com"
  }
}
```

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