LinkedIn Job Details Scraper API - By URL or Job ID

The LinkedIn suite

• LinkedIn Scraper API — every public LinkedIn surface in one dataset
• LinkedIn Jobs Search Scraper API — keyword and location searches with filters re-checked on the posting
• LinkedIn Company Scraper API — company slugs or URLs in, exact counts and every office out
• LinkedIn Company Posts Scraper API — the newest posts on a company page with exact reaction and comment counts
• LinkedIn Post Scraper API — post share links in, the full post and its visible comments out
• LinkedIn Pulse Article Scraper API — Pulse article links in, full text and exact engagement out
• LinkedIn Company Jobs Scraper API — company pages in, their open jobs out, id resolved for you
• LinkedIn New Jobs Scraper API — put a search on a daily schedule and pay only for postings you have not seen
• LinkedIn Profile Scraper API — public profiles with experience, education and exact follower counts — about 7 in 10 are shown, the rest are free
• LinkedIn Profile Posts Scraper API — a person's recent public posts, each read in full with exact counts

Paste LinkedIn job links or ids and get each posting in full: description, seniority, employment type, function, industries, applicants and salary when stated. No login, no cookies, no proxy to configure — it reads the pages LinkedIn shows to anyone. Failures are free: a closed job, a missing page or a page only members can see costs nothing and returns a row saying which.

Exact numbers, not display numbers. LinkedIn's page says "3M followers" or "10,001+ employees"; the rows carry 2,789,187 and 232,762.

Quick start

1. Press Start — the defaults are a working run.
2. Replace them with your own job links or ids (/jobs/view/... links, currentJobId= links and bare ids all work).
3. Take the dataset as JSON, CSV or Excel, or via the API. Every row has a type; the free coverage row says what was asked for and what arrived.

What people use it for

• Hiring-market intelligence. Which companies are hiring for which roles, where, at what seniority, and since when — with the full posting text for a keyword or an LLM pipeline.
• Lead lists from job postings. A company hiring three data engineers is a company buying data tooling this quarter. Turn searches into a list of companies, then add their company pages in the same run.
• Job-board and alert products. Put searches on a schedule with Monitor on and receive only postings you have not seen, with the exact posted date.
• Feeding an AI agent or workflow. One flat schema, a type on every row, and a free coverage row that says what was asked for and what arrived.

What the rows look like

A job row

{
  "type": "job",
  "id": "4370823981",
  "url": "https://www.linkedin.com/jobs/view/sr-data-engineer-at-accenture-federal-services-4370823981",
  "title": "Sr. Data Engineer",
  "companyName": "Accenture Federal Services",
  "company": { "name": "Accenture Federal Services", "url": "https://www.linkedin.com/company/accenturefederalservices", "slug": "accenturefederalservices" },
  "location": "Washington, DC",
  "postedAt": "2026-08-26",
  "applicants": { "count": 200, "text": "Over 200 applicants", "isEarly": false },
  "salary": { "text": "$116,900—$243,100", "min": 116900, "max": 243100, "currency": "USD", "period": null, "source": "description" },
  "seniorityLevel": "Mid-Senior level",
  "employmentType": "Full-time",
  "jobFunction": "Information Technology",
  "industries": ["IT Services and IT Consulting"],
  "description": { "text": "At Accenture Federal Services, nothing matters more than ...", "html": "<p>At Accenture Federal Services, ...</p>" },
  "searchQuery": "data engineer | United States"
}

postedAt is the exact date from LinkedIn's listing, not a "1 week ago" estimate. salary is filled only when the posting states one (source says whether it came from a salary element or the description text). applicants.count is null when LinkedIn only says "Be among the first 25 applicants".

What it costs

You pay for	Price
Each job you name by URL or id, delivered with its full posting (one request per row)	$4.00 per 1,000 jobs

Free, always: a job that has closed, a company, post or article that does not exist, a page LinkedIn only shows to signed-in members, a malformed URL, every error row, the coverage row and the run summary, a job skipped by your title filters or id list, and a posting whose stated seniority or job type does not match the filter you set. A run that reads nothing costs nothing.

On a one-off run a search is billed only when it delivered at least one job. With Monitor on, every search LinkedIn answered is billed, because that check is the work you scheduled — so a day with no new postings costs $2.00 per 1,000 searches and nothing else. A query LinkedIn cannot match (it returns unrelated "similar" jobs) is detected, delivers nothing and costs nothing. Searches never count against your result cap.

Set Cost ceiling (USD) to stop any run before it passes a number you choose; the free summary row reports what the run actually spent.

FAQ

Do I need a LinkedIn login, cookies or a proxy?

No. This Actor reads the pages LinkedIn shows to anyone without an account, and it never signs in, never sends a cookie and never uses a session. Everything is handled for you and there is nothing to buy on top. Measured 2026-09-02: a full default run read 25 pages from an ordinary IP with no proxy traffic at all.

Do the job filters actually work?

The date window, job type, Easy Apply, under-10-applicants and company filters change LinkedIn's results reliably (each was checked on three queries on 2026-09-02). Since LinkedIn's August 2026 search change, its experience-level and workplace filters are applied on some queries and ignored on others. So seniority and job type are re-checked against what the posting itself states, and a posting that does not match is neither delivered nor billed. Workplace (remote / hybrid / on-site) is passed to LinkedIn as its own filter and is not re-checked, because the public posting carries no structured workplace field.

How many jobs can one search return?

LinkedIn's public search stops at about 1,000 results per query. To go deeper, add locations, split keywords, or use a shorter date window — each combination is its own search with its own 1,000.

Why did I get jobs that do not match my keyword?

LinkedIn returns "similar" postings when a query has few exact matches and does not mark them. Use Title must contain and Title must not contain: they are applied before a posting is opened, and skipped jobs are never billed.

What happens to a job that closed or a page that does not exist?

It costs nothing. You get a free error row that says which (closed, not found, or only visible to members), and the run keeps going.

Does a run fail if everything I asked for is gone?

No. "All of these have closed" is a correct answer, not a failure, so the run succeeds and returns free rows explaining each one. Only LinkedIn actually refusing us fails a run.

Can I put this on a schedule without paying twice for the same data?

Yes. Turn Monitor on. Job ids delivered for each search are remembered for 60 days and never billed again; a day with no new postings bills only the search itself. A company, post or article whose numbers have not moved is a free row marked unchanged.

Will I be charged twice if the same thing appears twice in my input?

No. A post reached through a share link and again from a company page, or a job returned by two searches, is one row and one charge.

Limits, stated plainly

LinkedIn shows its search results (people, companies, content), employee lists, reaction lists and Sales Navigator only to signed-in members, and serves member profiles to visitors only at its own discretion (measured 2026-09-02 from Apify's own exits: 35 of 50 ordinary profiles, and the refused ones stay refused). This Actor reads public pages only and never signs in, so it sells none of those — and says so here rather than on your invoice.

The external "Apply" link and the hiring team are behind LinkedIn's sign-in and are not sold. Salary is delivered when the posting states it.

Use it from n8n, MCP, the API or a schedule

Built to be called by a workflow, not only from the Store form. The Actor is vonsensey/linkedin-job-details-scraper-api; every snippet below sends {}, which runs the defaults shown on the form — replace it with your own input.

n8n

Install the Apify community node (@apify/n8n-nodes-apify under Settings → Community Nodes, or search "Apify" on n8n Cloud). Add Apify → Run Actor with Actor vonsensey/linkedin-job-details-scraper-api and your input JSON, then Apify → Get Dataset Items on the run's defaultDatasetId and pipe the rows anywhere. For scheduled runs, the On new Apify Event trigger fires when a run of this Actor finishes.

MCP (Claude, Cursor, VS Code, any MCP client)

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=vonsensey/linkedin-job-details-scraper-api",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

Your agent then calls vonsensey/linkedin-job-details-scraper-api as a tool with the same input the form takes and reads the dataset back.

REST API (one call, rows in the response)

curl -X POST "https://api.apify.com/v2/acts/vonsensey~linkedin-job-details-scraper-api/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" -d '{}'

Python

from apify_client import ApifyClient
client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("vonsensey/linkedin-job-details-scraper-api").call(run_input={})
for row in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(row)

JavaScript

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('vonsensey/linkedin-job-details-scraper-api').call({});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Make, Zapier, LangChain, CrewAI

The Apify app in Make and Zapier has a Run an Actor module: pick vonsensey/linkedin-job-details-scraper-api. In LangChain and CrewAI the Apify tool wrappers take the same Actor id. A daily schedule needs nothing but the Console: Schedules → Create → this Actor → cron, and the dataset fills on its own.