Skip to Content
Prospecting data

LinkedIn job search

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 data2 endpointsKen-Version: 2026-11-02AuthenticationWorkspacesErrors
MarkdownOpenAPI

Headers

The endpoints on this page take these headers. Each endpoint's curl shows the ones it sends.

NameInTypeRequiredDescription
Ken-Versionheaderstring, one of: 2026-11-02, 1.1optionalThe 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-Idheaderinteger (int64)optionalThe 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.

Search LinkedIn jobs

POST/v1/linkedin-job-searcheslinkedin-job-searches.create
Permission
Search edit
Credits
Spends credits, price not on the rate card yet (social_data_record)
Rate limit
25 requests a day per workspace
Needs the linkedin_job_search feature on your workspace. Until it is on, calls answer 404.

Try it on developer.ken.so

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.

Request body

application/json, optional.

FieldTypeRequiredDescription
keywordsstringrequiredRequired. The job title or words to search, at most 200 characters: sdr, account executive.
locationstringoptionalFree text, at most 200 characters: Germany, Berlin, San Francisco Bay Area.
companiesarray of stringoptionalUp to 10 company names, or LinkedIn company ids (digits) on the seat path.
datePostedstringoptionalpast_day, past_week or past_month.
workplaceTypearray of stringoptionalon_site, remote, hybrid.
seniorityarray of stringoptionalinternship, entry_level, associate, mid_senior_level, director, executive.
limitinteger (int32)optionalLinkedIn rows to read, 1 to 100. Default 25.
cursorstringoptionalThe nextCursor of an earlier seat search with the same filters.
Request
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"
}'

Response 201

Also answers 202. data is a LinkedInJobSearch.

Show the 7 response fields and an example

The fields and an example are also on this endpoint's Markdown page.

Get a LinkedIn job search

GET/v1/linkedin-job-searches/{linkedInJobSearchId}linkedin-job-searches.get
Permission
Search view
Rate limit
12,000 requests a minute per API key
Needs the linkedin_job_search feature on your workspace. Until it is on, calls answer 404.

Try it on developer.ken.so

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.

Parameters

NameInTypeRequiredDescription
linkedInJobSearchIdpathstringrequired
Request
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"

Response 200

Also answers 202. data is a LinkedInJobSearch.

Show the 7 response fields and an example

The fields and an example are also on this endpoint's Markdown page.


On this page