02Jobs · LinkedIn Jobs API
LinkedIn Jobs API — getting LinkedIn postings without the partner gate
LinkedIn's own Jobs API exists, but only for approved partners going through LinkedIn's review process. This page covers the alternative most developers actually use: reading LinkedIn's public job listing pages through a collection API, field-mapped and priced per posting.
Prices verified 17 August 2026. Last updated September 2026.
LinkedIn's official Jobs API — partner approval required
RankFabrik reads the logged-out listing channel
Pay per posting returned — empty runs cost nothing
What a LinkedIn listing row looks like
Every posting returns the same shape whether it came from LinkedIn, Indeed or Glassdoor — no per-source field gymnastics to write yourself:
GET /offres?metier=data+engineer&lieu=London
{
"id": "4446697394",
"title": "Senior Data Engineer",
"company": "Example Ltd",
"companySlug": "example-ltd",
"companyUrl": "https://www.linkedin.com/company/example-ltd",
"location": "London, England, United Kingdom",
"city": "London",
"region": "England",
"country": "United Kingdom",
"published": "2026-09-01",
"salary": null,
"logo": "https://media.licdn.com/...",
"url": "https://www.linkedin.com/jobs/view/4446697394"
}
Salary is returned when the posting publishes one, null otherwise — never invented.
The response's completeness block tells you the real fill rate for your search before you commit
to volume.
Past the 1,000-result cap
Like most job sources, the public listing channel stops at roughly a thousand postings per
search. /balayer takes up to 20 cities in one call, and each city reopens its own
thousand-result budget — the response lists exactly what each city added, so the coverage number
is something you can reproduce, not a figure to take on faith.
Pricing, in plain units
job — posting
job-complete — posting + company
Pay per posting returned — you are charged only for events the actor actually returns, never for an empty run. Metered and billed by Apify; no separate RankFabrik account to open.
Run it on Apify — pay per posting returned → Compare pricing →
Questions
Does LinkedIn have an API for job postings?
LinkedIn operates a Jobs API, but it is gated to approved partners going through LinkedIn's own review — not a signup-and-query product for an individual developer. Most teams that need structured LinkedIn listings without that partnership turn to a collection API that reads the public, logged-out job listing pages instead.
Which API is best for job search?
It depends on which source you need: LinkedIn's own gated API if you already hold a partnership, a job-board aggregator if a handful of boards is enough, or a collection API like RankFabrik's if you want Indeed, LinkedIn and Glassdoor listings returned under one response shape with a measured completeness score per field.
Can you legally collect LinkedIn job postings?
Scraping public web pages sits in a legal gray area rather than a clean yes/no — courts and platforms have taken different positions over the years. What RankFabrik does is narrower than the general question: it reads pages that are publicly visible without logging in, does not bypass a login wall, CAPTCHA or other access control, and routes requests through a managed proxy layer to handle rate-limiting rather than to evade detection. That describes the collection method — it is not legal advice, and you remain responsible for how you use the data (re-publishing personal information, respecting a platform's terms of service, and your own jurisdiction's rules).
How do I get more than LinkedIn's own result cap?
The public listing channel stops at roughly a thousand postings per search, the same ceiling most job sources apply. <code>/balayer</code> segments the same query across up to 20 cities and reopens a fresh budget on each — on other roles that has taken a single-search count past 5,000 distinct postings.