# LinkedIn Jobs Scraper — No Login, Delta Mode | Pay Per Result (`nomad-agent/linkedin-scraper`) Actor LinkedIn jobs scraper — no login, no cookies, no proxy, no start fee. Search by keyword, location, remote & posting age; clean JSON: title, company, apply URL, description, seniority & industry. Delta mode bills only unseen postings — ideal for job alerts. Honest ~200 jobs/run. - **URL**: https://apify.com/nomad-agent/linkedin-scraper.md - **Developed by:** [Nomad.Dev](https://apify.com/nomad-agent) (community) - **Categories:** Jobs - **Stats:** 7 total users, 3 monthly users, 88.8% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing $0.90 / 1,000 job results This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows. 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. Actors are written with capital "A". ## 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. The best way to integrate Actors is as follows. - **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use). - **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`. - **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`. - **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`. - **Any other language** — the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## LinkedIn Jobs Scraper — No Login, Delta Mode | Pay Per Result > **Claude / Codex skill to describe and setup this actor: [SKILL.md](https://github.com/Exdenta/OinkAIJobSearch/blob/main/skill/linkedin-scraper/SKILL.md)** Extract live job postings from LinkedIn's public job search — no account, no cookies, no browser, **no start fee**. Filter by keyword, location, remote-only and posting age, and receive one clean JSON record per job. Built for **scheduled monitoring and job-alert bots**: turn on delta mode, run it on a cron, and pay only for postings you haven't seen before — a run that finds nothing new costs $0. ### Why this scraper | | This Actor | Typical alternatives | |---|---|---| | Price per 1,000 jobs | **$0.90** | $0.40–$10.00 | | Start fee per run | **$0** | up to $0.005–$0.05 — adds up fast on scheduled runs | | Cross-run dedup (delta mode) | **Built in, unseen-only billing** | mostly absent | | Login / cookies / proxy | **None needed** | some require cookies or proxies | | Zero-result runs | **Free + diagnostic row** | often billed or fail silently | | Max jobs per run | ~200 (honest guest-API limit) | up to 1,000 for bulk scrapers | If you need 1,000+ postings in one bulk pull, a large-scale scraper serves you better. If you poll LinkedIn every hour and want only what's new — this is the cheapest way to do it: no start fee × delta mode means a quiet hour costs literally nothing. ### What LinkedIn jobs data does this scraper extract? Each result is one flat JSON record per job posting: | Field | Meaning | |---|---| | `id` | Numeric LinkedIn job posting id, extracted from the posting URL (`null` if it couldn't be parsed) | | `title` | Job title as posted | | `company` | Hiring company / organisation | | `location` | Location / duty station (may include remote hints) | | `postedAt` | Posting date (`YYYY-MM-DD`) read from the search card, when LinkedIn includes it (`null` otherwise) | | `url` | Direct link to the posting | | `source` | Always `"linkedin"` | | `description` | Full plain-text job description (empty string if `includeDescription` is off or the fetch failed) | | `snippet` | Alias of `description`, same value — kept for compatibility with other scrapers in this collection | | `employmentType` | Employment type, e.g. `Full-time` (only when `includeCompanyInfo` is on; `null` otherwise) | | `seniorityLevel` | Seniority / experience level, e.g. `Mid-Senior level` (only when `includeCompanyInfo` is on) | | `jobFunction` | Job function, e.g. `Engineering and Information Technology` (only when `includeCompanyInfo` is on) | | `industries` | Company industry, e.g. `Software Development` (only when `includeCompanyInfo` is on) | | `applicantsCount` | Applicant-count caption, e.g. `Over 200 applicants` — best-effort, often hidden by LinkedIn (only when `includeCompanyInfo` is on) | | `hiringContactName` | Person LinkedIn names as the job poster, e.g. `Paula Guijarro` (only when `includeHiringContact` is on; `null` otherwise) | | `hiringContactTitle` | That person's headline, e.g. `Talent Acquisition at Acme` (only when `includeHiringContact` is on) | | `hiringContactUrl` | Their LinkedIn profile URL (only when `includeHiringContact` is on) | | `isNew` | `true` when delta mode (`onlyNewSinceLastRun`) emitted this posting as unseen on a previous flagged run (absent on normal runs) | The `employmentType` / `seniorityLevel` / `jobFunction` / `industries` / `applicantsCount` fields are read straight from each posting's job-criteria list — any value LinkedIn doesn't expose stays `null`; nothing is guessed. The `hiringContact*` fields come from the posting's "Meet the hiring team" block — the recruiter or hiring manager to write to. LinkedIn only names a poster on roughly a quarter of postings; on the rest the fields stay `null` rather than being guessed at. LinkedIn's guest cards never carry salary data, so no `salary` field is emitted — we don't fabricate one. A run that returns zero postings (or hits an unexpected error) still finishes **successfully** and pushes a single non-billed diagnostic row with a `warnings` field explaining why — so an empty result is never a silent failure. ### How to scrape LinkedIn jobs with this Actor 1. Click **Try for free** / **Run** — no login to the target site, no cookies, no proxies to configure. 2. Adjust the input (keyword, filters, `maxItems`) or keep the defaults. 3. Run it and export the dataset as JSON, CSV or Excel, or read it over the [API](https://docs.apify.com/api/v2). Run it from your own code: ```python from apify_client import ApifyClient client = ApifyClient("") run = client.actor("nomad-agent/linkedin-scraper").call(run_input={"maxItems": 50}) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item["title"], "—", item["company"], item["url"]) ``` Or a single HTTP call that runs the Actor and returns items in one response: ```bash curl -X POST \ "https://api.apify.com/v2/acts/nomad-agent~linkedin-scraper/run-sync-get-dataset-items?token=" \ -H "Content-Type: application/json" \ -d '{"maxItems": 50}' ``` ### Input | Field | Type | Default | Notes | |---|---|---|---| | `keyword` | string | `""` | Job title, skill or role to search for (e.g. "software engineer", "product manager react"). Leave empty to… | | `location` | string | `""` | City, region or country to filter by (e.g. "Spain", "London", "European Union"). Leave empty for worldwide… | | `remote` | boolean | `false` | When enabled, restricts results to remote-eligible postings. | | `timeFilter` | string | `"r86400"` | Restrict to postings published within the chosen window. | | `maxItems` | integer | `100` | Maximum number of job postings to return. **Hard ceiling: ~200 per run** — LinkedIn's guest search endpoint stops paginating past that offset no matter what you set here (0 = "no limit" still caps at ~200). | | `includeDescription` | boolean | `true` | Fetch and include the full plain-text job description for each posting. Disabling this makes runs faster… | | `includeCompanyInfo` | boolean | `false` | Also read structured job details (`employmentType`, `seniorityLevel`, `jobFunction`, `industries`, `applicantsCount`) from each posting. Reuses the description request — no extra requests when `includeDescription` is already on. | | `includeHiringContact` | boolean | `false` | Also read the job poster (`hiringContactName`, `hiringContactTitle`, `hiringContactUrl`) from each posting — who to contact about the role. Reuses the description request — no extra requests when `includeDescription` is already on. Present on ~25% of postings. | | `onlyNewSinceLastRun` | boolean | `false` | **Delta mode.** Only output postings not seen on a previous run that also had this flag on. Already-seen postings are dropped before push (**not billed**) — the cheapest way to poll on a schedule. See *Delta mode / monitoring* below. | | `skipJobId` | array of strings | `[]` | Explicit dedup list — drop any posting whose numeric job id is in this array. Use it to skip ids you already have, in a single call. | | `postedSince` | integer | `0` | Drop results whose posting date is older than this many days. Items without a known posting date are **not** filtered out. Set 0 to disable. | | `titleExclude` | array of strings | `[]` | Drop a result if its title contains any of these words or phrases (case-insensitive). | | `companyExclude` | array of strings | `[]` | Drop a result if its company name contains any of these words or phrases (case-insensitive). | | `cacheTtlSeconds` | integer | `1800` | Reuses the last fetch for this many seconds so rapid re-runs don't hit LinkedIn again. Set 0 to always fetch live. | Every filter and the two dedup modes default to off/empty, so existing integrations see no behavior change unless you opt in. ### Delta mode / monitoring Turn on `onlyNewSinceLastRun` to poll LinkedIn on a schedule and only pay for **genuinely new** postings. The Actor remembers the job ids it emitted on previous flagged runs in a dedicated per-Actor key-value store; on the next run it drops anything already seen *before* pushing (so those rows are never billed) and stamps each surviving record `isNew: true`. - Perfect for job-alert bots and cron-scheduled runs — a repeat run that finds nothing new pushes one non-billed diagnostic row instead of re-charging you. - Because LinkedIn's guest search is a windowed query (newest ~200 in your time filter), delta mode detects only **new** postings — it does **not** try to report "closed" postings (an absent posting may simply have scrolled past the window). - `skipJobId` does the same job for a one-off call: pass the ids you already have and they're skipped without touching the delta store. The delta store is best-effort: if it can't be read, the run degrades to "everything is new" rather than failing. ### Output example ```json { "id": "4429472960", "title": "Senior Frontend Engineer (React)", "company": "Acme Software", "location": "Berlin, Germany (Remote)", "postedAt": "2026-06-30", "url": "https://www.linkedin.com/jobs/view/4429472960", "source": "linkedin", "description": "We are hiring a Senior Frontend Engineer...", "snippet": "We are hiring a Senior Frontend Engineer..." } ``` `id` and `postedAt` are `null` on the rare card where LinkedIn's markup doesn't include them — the rest of the record is unaffected. ### Pricing **$0.0009 per job returned — and nothing else.** No start fee, no subscription, no rental. 100 jobs ≈ $0.09. In delta mode, already-seen postings are never billed, so a scheduled run that finds nothing new costs $0. ### Integrations Export results as JSON, CSV or Excel; connect via Make, Zapier or n8n; call directly with `run-sync-get-dataset-items`; or plug into AI agents through the Apify MCP server. ### Use cases - Job-alert bots and job boards that need fresh LinkedIn postings - Recruiting and sourcing pipelines tracking who is hiring - Salary and hiring-market research by role or region - AI agents that match candidates to live openings ### FAQ **Is it legal to scrape LinkedIn jobs?** This Actor reads only publicly available job postings — data any visitor can see without logging in. No personal data behind authentication is touched. Review the target site's terms and your local regulations for your specific use case. **Do I need an account on the target site?** No. Postings are fetched from public pages/APIs — no login, cookies or session tokens. **How fresh is the data?** Every run fetches live listings. Results are cached for `cacheTtlSeconds` (default 30 min, set 0 to always hit the source live). **How many jobs can I get?** `maxItems` caps the run (set 0 where supported for no cap). Most sources paginate from newest to oldest. **Does it work without a LinkedIn account?** Yes. The scraper reads LinkedIn's public guest job-search endpoint, so no login, cookies or session tokens are needed. **Something broken or missing?** Open an issue on the Actor's **Issues** tab — it is monitored and reliability fixes ship fast. **Is this Actor useful to you?** A quick ⭐ review on the Actor's **Reviews** tab helps other job-alert and recruiting users find it — and tells us what to build next. ### Related Actors - [Web Developer Jobs Scraper — 10 Boards in One](https://apify.com/nomad-agent/web-dev-bundle) - [AI & ML Engineer Jobs Scraper — 8 Boards in One](https://apify.com/nomad-agent/ml-ai-dev-bundle) - [Research & Academic Jobs Scraper — 10 Sources](https://apify.com/nomad-agent/researcher-bundle) - [Remote Jobs Scraper — RemoteOK Remotive WWR](https://apify.com/nomad-agent/remote-boards-scraper) *** **From the maker of [Oink](https://github.com/Exdenta/OinkAIJobSearch)** — an open-source, AI-powered job-search bot for Telegram that runs on these Actors. [Try the free bot](https://t.me/job_search_everyday_bot), get a managed instance at [oinkjobsearch.com](https://oinkjobsearch.com), or browse the [full catalog of 50+ Actors](https://apify.com/nomad-agent). # Actor input Schema ## `keyword` (type: `string`): Job title, skill or role to search for (e.g. software engineer, product manager react). Leave empty to search all recent postings for the given location. ## `location` (type: `string`): City, region or country to filter by (e.g. Spain, London, European Union). Leave empty for worldwide results. ## `remote` (type: `boolean`): When enabled, restricts results to remote-eligible postings. ## `timeFilter` (type: `string`): Restrict to postings published within the chosen window. ## `maxItems` (type: `integer`): Maximum number of job postings to return. Hard ceiling: LinkedIn's guest search endpoint only paginates to ~200 postings per run regardless of this setting (its offset stops returning new results past that point) — set higher than 200, or 0 for no limit, and you still get at most ~200. ## `includeDescription` (type: `boolean`): Fetch and include the full plain-text job description for each posting. Disabling this makes runs faster and uses fewer requests. ## `includeCompanyInfo` (type: `boolean`): Read structured attributes from each posting's job-criteria list into employmentType, seniorityLevel, jobFunction, industries and (best-effort) applicantsCount. Uses the same detail request as the description (no extra requests when Include full description is already on). Any field LinkedIn doesn't expose stays null — values are never guessed. ## `includeHiringContact` (type: `boolean`): Read the person LinkedIn names as the job poster into hiringContactName, hiringContactTitle and hiringContactUrl (their LinkedIn profile) — the recruiter or hiring manager to write to. Comes from the same detail request as the description (no extra requests when Include full description is already on). LinkedIn only names a poster on roughly a quarter of postings; the fields stay null on the rest and are never guessed. ## `postedSince` (type: `integer`): Drop results whose posting date is older than this many days. Items without a known posting date are not filtered out. Set 0 to disable. ## `titleExclude` (type: `array`): Drop a result if its title contains any of these words or phrases (case-insensitive). ## `companyExclude` (type: `array`): Drop a result if its company name contains any of these words or phrases (case-insensitive). ## `onlyNewSinceLastRun` (type: `boolean`): Delta / monitoring mode: only output postings not already seen on a previous run that also had this flag on. Already-seen postings are dropped before push (not billed), so this is the cheapest way to run this Actor on a cron schedule and only pay for genuinely new postings — ideal for job-alert bots. State is tracked per Actor in a dedicated key-value store, keyed by each posting's job id. Note: because guest search is a windowed query (not a full enumeration), this detects only NEW postings, never closed ones. See README “Delta mode / monitoring”. ## `skipJobId` (type: `array`): Explicit dedup list: drop any posting whose numeric LinkedIn job id is in this array (exact match). Complements onlyNewSinceLastRun — use this to skip ids you already have from a prior run/dataset in a single call, without the per-Actor delta store. ## `cacheTtlSeconds` (type: `integer`): Reuses the last fetch for this many seconds so rapid re-runs don't hit LinkedIn again. Set 0 to always fetch live. ## Actor input object example ```json { "keyword": "frontend developer typescript", "location": "Germany", "remote": false, "timeFilter": "r86400", "maxItems": 100, "includeDescription": true, "includeCompanyInfo": false, "includeHiringContact": false, "postedSince": 0, "titleExclude": [], "companyExclude": [], "onlyNewSinceLastRun": false, "skipJobId": [], "cacheTtlSeconds": 1800 } ``` # Actor output Schema ## `dataset` (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 = {}; // Run the Actor and wait for it to finish const run = await client.actor("nomad-agent/linkedin-scraper").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 = {} # Run the Actor and wait for it to finish run = client.actor("nomad-agent/linkedin-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{}' | apify call nomad-agent/linkedin-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=nomad-agent/linkedin-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/acts/GGGJOOdpf4hgT6FbH/builds/oih89wV4Grjhxx2F6/openapi.json