JobsPipe

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 early accessCompare with scraping

In active development - join early access to get notified at launch.

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.

What you get

  • titleJob title
  • companyHiring company name
  • locationCity, country, remote flag
  • posted_atWhen the job went live
  • seniorityExperience level
  • employment_typeFull-time, contract, etc.
  • apply_urlLink to the LinkedIn posting
  • sourceAlways 'linkedin' - same schema as 30+ other sources

Example response

{
  "id": "li_3901774225",
  "source": "linkedin",
  "title": "Senior Backend Engineer",
  "company": "Northwind Labs",
  "location": { "city": "Berlin", "country": "DE", "remote": true },
  "posted_at": "2026-05-27T09:12:00Z",
  "seniority": "Senior",
  "employment_type": "Full-time",
  "apply_url": "https://www.linkedin.com/jobs/view/3901774225"
}

Illustrative example of the planned response shape.

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: title, company, location (city, country, remote flag), posted date, seniority, employment type and the apply 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.

When is it available?

The unified API including the LinkedIn source is in active development. Create a free account to join early access and be notified when the LinkedIn endpoint goes live.

Get LinkedIn jobs without the scraper

Join early access for the LinkedIn jobs endpoint and the rest of the unified jobs API. Free tier, no credit card.

Get early access