NewSearch millions of jobs from your AI agent with MCP

LinkedIn jobs API.

Public LinkedIn job postings as normalized JSON - title, company, location, posted date and apply URL - through one endpoint, with no scraping to maintain. Built on public guest data, never profile data.

Get a free API key Compare with scraping

Live now, and the largest source in the index. New postings land every day.

Why not just use LinkedIn’s official API?

LinkedIn’s official Jobs/Talent API is gated to approved ATS and talent-solutions partners and is designed for posting and syncing jobs, not open job-search extraction. Search “LinkedIn jobs API” and the top result is LinkedIn’s partner catalog, not a usable endpoint. JobsPipe fills that gap from the public side.

Built on LinkedIn's public, logged-out job listings - the same postings any visitor sees, never authenticated profile data.

One normalized JSON schema shared with Workday, Greenhouse, Lever, Ashby and 30+ other sources, so LinkedIn is just another source flag.

No proxies, headless browsers or anti-bot maintenance for you to run and babysit.

LinkedIn is the largest source in the index and is collected continuously, so a query for the last seven days returns the last seven days.

What you get

job_titleJob title
companyHiring company name
cities / country_codeWhere the role is based
date_postedWhen the job went live (YYYY-MM-DD)
employment_statusesFULL_TIME, PART_TIME, CONTRACT and so on
technology_slugsNormalized skills and tools named in the posting
min_annual_salary_usdSalary floor in USD when the posting states one
final_urlThe LinkedIn posting, after redirects

One record

{
  "id": "3ce30e65490909ec",
  "job_title": "Senior Software Engineer - Distributed Systems",
  "company": "NeuroSpark AI",
  "cities": ["California"],
  "country_code": "US",
  "seniority": "senior",
  "employment_statuses": ["FULL_TIME"],
  "min_annual_salary_usd": 170000,
  "max_annual_salary_usd": 350000,
  "date_posted": "2026-08-03",
  "technology_slugs": [
    "system-design", "llm", "rust", "c++", "kubernetes"
  ],
  "occupation_code": "2512",
  "occupation_label": "Software Developers",
  "final_url": "https://www.linkedin.com/jobs/view/senior-software-engineer-distributed-systems-at-neurospark-ai-4448119707"
}

A real posting collected on 3 August 2026, abridged to the fields most people use. The full record carries about fifty.

Try it without a key

The sandbox endpoint takes the same filters as the live one and needs no authentication, so you can check the request shape before signing up. It answers with sample records rather than live postings; swap in /v1/jobs/search and an API key to get the real index.

curl -s -X POST https://api.jobspipe.dev/v1/sandbox/jobs/search \
  -H 'content-type: application/json' \
  -d '{
    "source_or": ["linkedin"],
    "posted_at_max_age_days": 7,
    "limit": 10
  }'

source_or is what makes this a LinkedIn query. Drop it and the same request searches every source at once. See the sandbox for the full filter list.

Part of one unified API

LinkedIn is one source among 30+. Query it alongside the rest through a single normalized endpoint - see the jobs API overview and the LinkedIn source details.

LinkedIn jobs API: frequently asked questions

Does LinkedIn have a jobs API?

LinkedIn's official Jobs/Talent API exists but is gated to approved ATS and talent-solutions partners and is built around posting and syncing jobs, not open job-search extraction. That is why most developers searching for a 'LinkedIn jobs API' use a third-party API built on LinkedIn's public guest data instead.

Is this legal? How is it different from scraping LinkedIn?

It reads only LinkedIn's public job listings - the logged-out pages anyone can view - and never logs in or touches profile data. Public-data access was affirmed in the hiQ v. LinkedIn case, and staying on guest job postings avoids the riskier authenticated-scraping territory. It is the cleaner posture than running your own profile scraper.

What data does the LinkedIn jobs API return?

Per posting: job_title, company, cities and country_code, date_posted, employment_statuses, technology_slugs, salary range in USD when the posting states one, and final_url - returned in the same normalized JSON shape as every other JobsPipe source, so you can query LinkedIn alongside Greenhouse, Lever, Workday and others through one endpoint. Coverage varies by field because it varies in the source: employment_statuses is present on 99% of live LinkedIn postings and technology_slugs on 83%, while a stated salary appears on 23% and company_domain is not published on LinkedIn postings at all.

How much does the LinkedIn jobs API cost?

The same as every other source, because LinkedIn is not priced separately. One credit is one job returned. The free tier is 1,000 jobs, Builder is 25,000 for $49/mo and Scale is 300,000 for $349/mo, which works out at $1.16 per 1,000 against $1.50 at TheirStack. A fuller breakdown, including how that compares to the rest of the market, is in the LinkedIn API cost guide.

LinkedIn API cost guide

Should I use this or write my own LinkedIn scraper?

A scraper is cheaper on day one and more expensive every day after, because the cost is not the code but the proxies, the headless browsers and the layout changes you have to keep chasing. This API is the same public guest data with that maintenance already absorbed. If you want to see the tradeoff written out before deciding, the scraping comparison walks through what each approach actually costs to run.

API versus scraping, compared

Get LinkedIn jobs without the scraper

The LinkedIn endpoint and the rest of the unified jobs API, on one key. The free tier is 1,000 jobs a month, and one credit is one job returned.

Get a free API key