LinkedIn Job Details Scraper by ID or URL

Give it LinkedIn job links or bare job ids and get one row per posting: the full description, company and company page, location, seniority level, employment type, industries and the applicant count. It reads the public page LinkedIn shows to a signed-out visitor, so there is no login, no cookie and no account of yours involved.

What it does

This is the "I already have the job ids" actor. You hold a list of ids or links (from a job-alert email, an ATS export, a CRM, a scraper you ran earlier) and you want the full posting behind each one. One id is one request and one row. It does not search: to find postings by keyword and location, use LinkedIn Jobs Search first and feed the ids it returns into this actor.

A miss (a removed posting, a wrong id, a LinkedIn block) comes back as a row with "found": false and a plain-English reason, and is never charged.

Example input

{ "jobs": ["https://www.linkedin.com/jobs/view/4483715889", "4481462474"] }

Example row (shortened)

{
  "query": "4483715889", "found": true, "status": "OK",
  "jobId": "4483715889",
  "url": "https://www.linkedin.com/jobs/view/4483715889",
  "title": "<job title>", "company": "<company>", "companyUrl": "https://www.linkedin.com/company/<slug>",
  "location": "<city, region>", "postedAt": "2026-10-23", "postedAgo": "5 days ago",
  "applicants": 34, "seniority": "Mid-Senior level", "employmentType": "Full-time",
  "industries": "<industry>",
  "description": "<the whole description, paragraphs kept>"
}

Fields

Field	What it is
jobId, url	The LinkedIn job id and its public /jobs/view/ link
title, company, companyUrl, location	From the top card of the posting
postedAt, postedAgo	LinkedIn only prints "5 days ago". postedAgo is that text; postedAt is a date worked out from it, as precise as the text ("2 months ago" is about 60 days, give or take a month)
applicants, applicantsText	The count when LinkedIn prints one ("34 applicants"); null for the early-applicant badge ("Be among the first 25 applicants"), whose 25 is a cap, not a count. applicantsText is always the raw caption
seniority, employmentType, industries	The criteria LinkedIn lists under the description (null on a posting that omits one). LinkedIn's "Job function" criterion is not offered: it did not come back on any posting in the live check
description	The whole description as plain text
checkedAt	When this run read the page

Not on the page, so not offered: an exact posting date, a separate pay field (pay appears only as prose inside description), an offsite apply link (the Apply button opens a sign-up modal), and any recruiter or poster name (a signed-out page does not show one, and this actor does not look for one).

How to use

1. In the Apify Console. Open the actor page and click Start — the jobs field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. Via the API. Call it directly with a POST request — no Console needed once you have an API token:

   curl "https://api.apify.com/v2/acts/accountable_eel~linkedin-job-details-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"jobs":["4483715889","4481462474","4483737697"]}'
   

3. On a schedule. Save this actor as an Apify Task with the input you want, then add a Schedule (hourly, daily, weekly) so it runs on its own — no server of your own required.

Input

{
  "jobs": [
    "4483715889",
    "4481462474",
    "4483737697"
  ]
}

One job per line. Paste the LinkedIn job link or just the job id (the number at the end of linkedin.com/jobs/view/...). Accepted formats: https://www.linkedin.com/jobs/view/4483715889, https://www.linkedin.com/jobs/view/marketing-manager-at-1-hotels-4481462474, 4483737697.

Accepted forms: https://www.linkedin.com/jobs/view/4483715889, a link with the title in it (.../jobs/view/marketing-manager-at-acme-4483715889?trk=...), a collections link carrying currentJobId=4483715889, or the bare id. One dataset row is returned per input line; rows with "found": false are never charged.

Output

One row per job, for example:

query	found	status	jobId	url	title	company	companyUrl	location	postedAt	postedAgo	applicants	applicantsText	seniority	employmentType	industries	description	checkedAt	scrapedAt
4483715889	true	OK							<posted (approx. date)>	<posted (as linkedin shows it)>		<applicants (as linkedin shows it)>						1970-01-01T00:00:00.000Z

A miss comes back as a row with "found": false and is never charged. The status tells you why: NOT_FOUND (removed posting or wrong id), BLOCKED (LinkedIn answered a rate limit or a sign-in wall; run those ids again with a lower concurrency), BAD_FORMAT (not a job link or id) or PARSE_CHANGED (LinkedIn changed the page; nothing charged, please report it).

Enrich a list of job ids in 3 steps

1. Collect the ids. Paste the links or ids into the jobs field, one per line, or send them as a JSON array through the API. A column of ids from a sheet, an n8n node or a Clay table works the same way; links and bare ids can be mixed.
2. Run it. Start the actor, or call the run-sync-get-dataset-items endpoint shown under "How to use". Turn on "Hide rows with no result" if you only want the postings that were read.
3. Join on jobId. Every row carries jobId and query (your input line), so the output joins straight back onto your list. Open the dataset as CSV, JSON or Excel, or pull it into Google Sheets, n8n, Make or Clay.

Example runs

Three saved runs you can copy:

• Get a LinkedIn job description by job id. { "jobs": ["4483715889"] }, then read the description field.
• LinkedIn job details bulk export. { "jobs": ["4483715889", "4481462474", "4483737697"] }, open the dataset as CSV or send it to Google Sheets.
• Enrich LinkedIn job ids in n8n. An HTTP Request node posting { "jobs": ["{{ $json.jobId }}"] } to the run-sync-get-dataset-items endpoint, with the returned seniority, industries and description merged back by jobId.

Limits and cost

• Guest page only. It reads what LinkedIn shows a signed-out visitor. A posting LinkedIn has taken down, or one that is no longer accepting applications and shows no description, comes back as a free NOT_FOUND miss; a closed posting that still shows its description is returned.
• Proxy. The default is the Apify Residential proxy, the route these pages were measured on. Measured cost on it: about $0.159 per 1,000 descriptions in proxy traffic (25 descriptions moved 0.000498 GB at $8/GB, README of LinkedIn Jobs Search, 2026-08-24); the live check of this actor re-measures it.
• Pace. The default is 3 postings at once. LinkedIn rate-limits fast runs; if ids come back BLOCKED, lower "Max concurrency" and run those ids again.
• No monitoring mode. A posting fetched by id does not change in a way worth watching run over run, so there is no "only new" switch. To watch a search for new postings, use LinkedIn Jobs Search.

Pricing

Pay-per-event. A flat per-run fee covers session/proxy warmup; you're billed per item only when data is actually found and returned — see .actor/pay_per_event.json for exact prices. A miss is never charged.

Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

curl "https://api.apify.com/v2/acts/accountable_eel~linkedin-job-details-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jobs":["4483715889","4481462474","4483737697"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~linkedin-job-details-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"jobs":["4483715889","4481462474","4483737697"]} (swap in an expression from an earlier node for a real value).

Clay. Add an "HTTP API" column: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~linkedin-job-details-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"jobs":["{{job posting}}"]}, mapping the row's job posting into the jobs array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "LinkedIn Job Details Scraper: Bulk by Job ID or URL" — the agent will find and run this actor.