LinkedIn hub

LinkedIn Job API

Look up public LinkedIn job postings by URL and get structured JSON — title, company, pay, description, apply links — without scraping login-walled job pages yourself.

GET /v1/linkedin/jobs

2 credits per job URL requested. Up to 50 jobs per request (100 credits max).

About this endpoint

Talent intel and hiring-market tools often already have a `/jobs/view/…` link from a recruiter Slack, a CRM note, or a prior search pass. You need the public posting card as JSON you can store and compare, not another headless browser session that dies on a checkpoint.

`GET /v1/linkedin/jobs` takes one or more public LinkedIn job URLs (`url` query param, repeatable). Each URL must include a `/jobs/view/` path. The response uses the shared Social Fetch envelope with a `results` array and a `summary` of `requestedUrls`, `found`, `notFound`, and `errored`. Branch on each row's `lookupStatus` (`found`, `not_found`, or `error`) before you write. When found, `job` holds the listing fields LinkedIn shows publicly — id, url, title, company name/id/URL/logo, location, summary, seniority, function, employment type, industries, pay range text and structured base salary, posted labels/dates, applicant count, poster info, Easy Apply / apply link, description HTML/text, and country code when available.

Pricing is 2 credits per job URL requested, up to 50 URLs per call (100 credits max). Trust `meta.creditsCharged`. This route is URL lookup, not keyword search — use `GET /v1/linkedin/jobs/search` when you have a keyword and location instead of posting URLs. Company pages stay on `GET /v1/linkedin/companies`; people stay on `GET /v1/linkedin/profiles`.

LinkedIn Job API FAQ

How do I fetch a LinkedIn job posting via API?

Call `GET /v1/linkedin/jobs` with your Social Fetch API key (`x-api-key`) and a public LinkedIn job `url` query param that includes `/jobs/view/` (for example `https://www.linkedin.com/jobs/view/…`). Read `data.results[].lookupStatus` and the `job` object in the JSON response. Full parameters are in the API docs.

How much does the LinkedIn Job API cost?

2 credits per job URL requested. You can send up to 50 URLs in one request (100 credits max). Always trust `meta.creditsCharged` on the response over a spreadsheet estimate.

Can I look up multiple LinkedIn jobs in one request?

Yes. Pass multiple `url` query values on the same `GET /v1/linkedin/jobs` call, up to 50. The response returns a `results` array plus a `summary` of found, notFound, and errored counts.

What fields does each LinkedIn job result include?

When `lookupStatus` is `found`, the `job` object can include id, url, title, company name/id/URL/logo, location, summary, seniority, function, employment type, industries, pay range text and structured base salary, posted labels/dates, applicant count, poster info, Easy Apply / apply link, description HTML/text, and country code. Coverage follows what is publicly visible on the posting.

LinkedIn job GET by URL vs job search?

Use `GET /v1/linkedin/jobs` when you already have one or more `/jobs/view/…` URLs and want those postings directly. Use `GET /v1/linkedin/jobs/search` when you have a keyword and location and need candidate listings first.

What happens when a LinkedIn job URL is not found?

The batch still returns HTTP 200 with per-URL rows. Check each result's `lookupStatus`. Only upsert when status is `found`. Keep `meta.requestId` (and any per-row `error`) so you can retry or escalate failed enrichment rows.

Do I need LinkedIn partner API access for job lookups?

No. Social Fetch returns public LinkedIn job posting data for enrichment-style lookups. LinkedIn's official partner APIs are separate and require LinkedIn's access programs and authorization.