LinkedIn jobs
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.
Headers
The endpoints on this page take these headers. Each endpoint's curl shows the ones it sends.
| Name | In | Type | Required | Description |
|---|---|---|---|---|
Ken-Version | header | string, one of: 2026-11-02, 1.1 | optional | 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 date that is not a version answers 400 unsupported_version; any other value that is not a version is treated as legacy. |
X-Ken-Workspace-Id | header | integer (int64) | optional | 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. |
Get a LinkedIn job's detail
/v1/linkedin-jobs/{linkedInJobId}linkedin-jobs.get- Permission
- Search view
- Rate limit
- 240 requests a minute per API key
linkedin_job_search feature on your workspace. Until it is on, calls answer 404.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.
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
linkedInJobId | path | string | required |
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"Response 200
data is a LinkedInJob.
Show the 10 response fields and an example
The fields and an example are also on this endpoint's Markdown page.
More in Prospecting data:People and company searchSaved searchesSaved listsSaved list membersSaved list invitesEmail finderFunding roundsJob postingsJob post searchLinkedIn job searchWeb scrapingSocial data lookupsSocial data searchesSocial profile resolutionSocial data recordsSignalsAll resources