# LinkedIn Job Details Scraper by ID or URL, No Login (`accountable_eel/linkedin-job-details-lookup`) Actor LinkedIn job details scraper without login: paste job links or ids, get one row per posting with the full description, company, location, seniority, employment type, industries and applicants. Built for enriching job ids in n8n, Make or Clay. Misses are never charged. - **URL**: https://apify.com/accountable_eel/linkedin-job-details-lookup.md - **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community) - **Categories:** Jobs, Lead generation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $3.04 / 1,000 job posting returneds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## 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](https://apify.com/accountable_eel/linkedin-jobs-search-lookup) 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** ```json { "jobs": ["https://www.linkedin.com/jobs/view/4483715889", "4481462474"] } ``` **Example row** (shortened) ```json { "query": "4483715889", "found": true, "status": "OK", "jobId": "4483715889", "url": "https://www.linkedin.com/jobs/view/4483715889", "title": "", "company": "", "companyUrl": "https://www.linkedin.com/company/", "location": "", "postedAt": "2026-10-23", "postedAgo": "5 days ago", "applicants": 34, "seniority": "Mid-Senior level", "employmentType": "Full-time", "industries": "", "description": "" } ``` ### 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: ```bash curl "https://api.apify.com/v2/acts/accountable_eel~linkedin-job-details-lookup/run-sync-get-dataset-items?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 ```json { "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 | | | | | | | \ | \ | | \ | | | | | | 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. ```bash curl "https://api.apify.com/v2/acts/accountable_eel~linkedin-job-details-lookup/run-sync-get-dataset-items?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=`, 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=`, 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. # Actor input Schema ## `jobs` (type: `array`): 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. You're only charged for the ones we actually find — a miss costs nothing. ## `testRun` (type: `boolean`): Turn this on to test your input on a small sample before running the full list. Turn it off to process everything. ## `onlyFound` (type: `boolean`): Only keep rows where something was actually found. Misses are always free, whether or not you show them here. ## `includeKeywords` (type: `array`): Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything. ## `excludeKeywords` (type: `array`): Optional. Drop any result that mentions one of these words. Leave empty to skip nothing. ## `maxResults` (type: `integer`): Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit. ## `columns` (type: `array`): Choose which pieces of information to include in each result row. All are included by default. ## `maxConcurrency` (type: `integer`): Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady. ## `proxyConfiguration` (type: `object`): Apify Proxy config. Residential recommended for anti-bot-sensitive targets. ## Actor input object example ```json { "jobs": [ "4483715889", "4481462474", "4483737697" ], "testRun": false, "onlyFound": false, "includeKeywords": [], "excludeKeywords": [], "columns": [ "jobId", "url", "title", "company", "companyUrl", "location", "postedAt", "postedAgo", "applicants", "applicantsText", "seniority", "employmentType", "industries", "description", "checkedAt" ], "maxConcurrency": 3, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } } ``` # Actor output Schema ## `results` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "jobs": [ "4483715889", "4481462474", "4483737697" ], "includeKeywords": [], "excludeKeywords": [] }; // Run the Actor and wait for it to finish const run = await client.actor("accountable_eel/linkedin-job-details-lookup").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "jobs": [ "4483715889", "4481462474", "4483737697", ], "includeKeywords": [], "excludeKeywords": [], } # Run the Actor and wait for it to finish run = client.actor("accountable_eel/linkedin-job-details-lookup").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "jobs": [ "4483715889", "4481462474", "4483737697" ], "includeKeywords": [], "excludeKeywords": [] }' | apify call accountable_eel/linkedin-job-details-lookup --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/linkedin-job-details-lookup" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/QezlfQ6P9Hmg5s4F1/builds/9L3kcWPZCTXfWSa1y/openapi.json