LinkedIn Jobs Scraper (No Cookies) + Full Descriptions

$0.1/1K jobs | Extract LinkedIn jobs in bulk with the full original description (text and HTML), company, locations and posting date. Filter by keyword, location, remote and job type. No cookies or login. Not affiliated with LinkedIn.

LinkedIn Jobs Bulk Scraper

Our scraper collects recent public LinkedIn jobs and lets you filter by keyword, location, remote or on-site work, employment type and posting age. Every row carries the complete original job description in text and HTML, so you never have to open the posting to read it. It is ideal for job alerts, recruiting and sourcing pipelines, hiring-market analytics and job boards.

• Need up to 1,000 jobs per run, AI enrichment or English translation? Use LinkedIn Jobs Scraper | AI Enrichment.
• Want LinkedIn together with 20 other job boards in one run? Use All Jobs Scraper (No Login) + 21 Boards in One.
• Tracking AI and ML engineering jobs? AI & ML Engineer Jobs Scraper (No Login) + 10 Boards covers the specialist boards too.
• Browse all our job-board scrapers: https://apify.com/nomad-agent

Key Benefits

• No cookies or login: nothing to connect, and no LinkedIn account at risk.
• Low pricing: $0.10 per 1,000 jobs, with lower rates on Scale and Business plans ($0.075 and $0.05 per 1,000), and no start fee.
• Full descriptions only: a posting with a missing or truncated description is never returned.
• No repeats across runs: schedule the same search daily and get only postings you have not received yet.
• Newest first: results are sorted by posting date, so a small maxItems gets you the latest jobs.

How It Works

1. Provide your search. Every filter is optional:
   • (optional) Search queries (e.g., python developer, product manager). A job matches when its title or description contains every word of a query.
   • (optional) Locations (e.g., Germany, Berlin, DE, Europe). Countries match by name, code and native name, so Germany, DE and Deutschland find the same jobs.
   • (optional) Work arrangement (remote, hybrid, onsite) and employment type (Full-time, Part-time, Contract, Internship).
   • (optional) Posted within (e.g., 24h, 7d, 2w). Default is any.
2. Set how many jobs you want with maxItems.
3. Click Start. The form opens with software engineer in Germany and 20 jobs, so a first run returns real rows in about a minute.

More settings:

• maxItems - How many jobs one run returns. Default is 100; 0, or anything above 200, means 200.
• dedupe - On by default: jobs already delivered to your Apify account for the same search are skipped. Set dedupe.enabled to false to get everything again, or set dedupe.key to keep separate alert histories.

Run the same search twice and the second run returns only new jobs, possibly none. That is the repeat suppression working; turn dedupe off to see every job again.

A run returns at most 200 jobs, so split a big export by country or keyword and keep dedupe on so the runs do not overlap.

If you set a work arrangement or employment type, jobs whose posting does not state it are left out. Leave those filters empty to keep them.

Most jobs come from our stored LinkedIn postings, which keeps runs fast. When fewer than maxItems new jobs are stored for your search, the run reads the rest from LinkedIn's public job pages. LinkedIn sometimes limits those reads; the stored jobs are still returned and the run summary says how many were read live.

Data You'll Receive

• Job details: title, complete description (text and HTML), locations, posting date, deadline, salary when published.
• Company: employer name.
• Terms: work arrangement and employment type, whenever the posting states them (unknown facts are null).
• Hiring contacts: name, title and profile link, on some jobs read live from LinkedIn when the posting names a recruiter (often empty).
• Links and identity: the LinkedIn job URL, plus a stable id and source for deduplication.

Sample output data

Here is an example job from this Actor (long text shortened for display):

{
  "schemaVersion": "nomad-agent-job-row-v5",
  "source": "linkedin",
  "id": "4323907522",
  "url": "https://www.linkedin.com/jobs/view/backend-developer-java-at-expleo-group-4323907522",
  "title": "Backend developer (java)",
  "company": "Expleo Group",
  "locations": ["Tangier, Tanger-Tetouan-Al Hoceima, Morocco"],
  "countryCodes": null,
  "applicantLocations": null,
  "postedAt": "2026-10-02",
  "deadline": null,
  "description": "Expleo Group relies on 19,000 highly qualified employees delivering high-value solutions across 30 countries… [truncated for display]",
  "descriptionHtml": "Expleo Group relies on 19,000 highly qualified employees…<br><br>… [truncated for display]",
  "workType": null,
  "salary": null,
  "employmentTypes": ["Full-time"],
  "hiringContacts": []
}

LinkedIn Jobs API

Results are stored in a dataset that you can export as CSV, JSON or Excel, or read through the Apify API. Schedule it, or connect it to Make, n8n, Zapier or an MCP client to push new jobs wherever you need them. Each run also writes a RUN-SUMMARY record to its key-value store, with any input field that was mapped or ignored.

Support and Feedback

We improve these scrapers from your feedback. If something breaks or you need a filter:

• Open an issue on the Actor's Issues tab.
• If this Actor saved you time, a short review on the Store helps other people find it.

Product guides and related tools

• Guide and starter input on nomadagent.dev
• Product overview and public links
• Public setup guide
• Job Atlas job-data tools
• Oink personal job alerts
• How to scrape LinkedIn jobs without login or cookies

Run evidence

Observed run

An Apify account is required. Use your Apify API token when calling the API; Console runs do not need that token pasted into the input. No user API-key field is required by this input schema.

Free-tier event rates checked 2026-10-04: result $0.0001.

Cost: Total = Actor event charges + platform usage if separately billed + any BYO-provider charges. See “Current costs” for your event rates, plan tiers and a calculation. A sample does not promise future billable volume.

Input and output below were read from the same successful run XcaczYtHPdoyAbhk7 (2026-10-03, immutable build a4m7ec7WMn5WAYQfr). This is an observed example, not a guarantee that repeating it returns this row.

Input JSON

{
  "queries": [],
  "locations": [],
  "locationTypes": [],
  "employmentTypes": [],
  "postedWithin": "any",
  "maxItems": 100,
  "dedupe": {
    "enabled": true,
    "key": ""
  },
  "schemaVersion": "nomad-agent-simple-inventory-search-v2"
}

Matching output excerpt

Long strings and arrays are shortened for display; this is not a complete dataset fixture.

{
  "schemaVersion": "nomad-agent-job-row-v3",
  "source": "linkedin",
  "id": "4323907522",
  "url": "https://www.linkedin.com/jobs/view/backend-developer-java-at-expleo-group-4323907522",
  "title": "Backend developer (java)",
  "company": "Expleo Group",
  "locations": [
    "Tangier, Tanger-Tetouan-Al Hoceima, Morocco"
  ],
  "postedAt": "2026-10-02",
  "deadline": null,
  "description": "Expleo Group relies on 19,000 highly qualified employees delivering high-value solutions across 30 countries. Expleo helps you achieve your ambitions and secure our shared future. We offer a unique combination of bold thinking and reliable execution to accelerate innovation at every stage of your value chain. Beyond joining a company, we are offering you a h… [truncated for display]",
  "descriptionHtml": "Expleo Group relies on 19,000 highly qualified employees delivering high-value solutions across 30 countries. Expleo helps you achieve your ambitions and secure our shared future. We offer a unique combination of bold thinking and reliable execution to accelerate innovation at every stage of your value chain.<br><br>Beyond joining a company, we are offering … [truncated for display]",
  "workType": null,
  "salary": null,
  "employmentTypes": [
    "Full-time"
  ],
  "hiringContacts": []
}

Retained dedupe history can suppress previously returned postings. Keep a stable key and save your own history; an unchanged rerun can return zero new rows.

Recent LinkedIn jobs with complete original descriptions. Each row carries the source ID and URL, title, employer, locations, the original description as text and HTML, posting date, deadline, work arrangement, employment type, salary and the hiring contacts the source names, whenever the source publishes them. Unknown optional facts are null; an empty locations array means the source names no physical place, and an empty hiringContacts array means no contact was captured for that posting (contacts are read only for some postings). locations is where the job is, countryCodes lists the countries of those places as ISO 3166-1 two-letter codes (null when no place has a known country), and applicantLocations is where an applicant may live, for example a remote job open only to residents of some countries: it is null when the source states nothing and [] when it states no restriction.

Coverage includes jobs from public LinkedIn pages. Every posting is verified before it is served. A posting with a missing, truncated or unverified description is never returned: every row has the full original text. Runs read the stored postings first, so a request the stored postings can fill is fast and never touches LinkedIn. Only when fewer than maxItems new postings remain does the run read the missing ones from LinkedIn's public job pages, with no login and with your filters sent to its own search. Postings already stored are never read again, with deduplication on (the default) a posting is never returned twice, and every posting read this way is stored for the next run when its full description is verified. LinkedIn may limit or block a run: the stored postings are still returned, RUN-SUMMARY.liveTopUp says what was read, and the run is marked partial.

Input and output format

{"schemaVersion": "nomad-agent-simple-inventory-search-v2", "queries": ["software engineer"], "locations": ["Europe"], "locationTypes": ["remote"], "employmentTypes": [], "postedWithin": "7d", "maxItems": 100, "dedupe": {"enabled": true, "key": ""}}

Every filter is optional, and an empty list means no filter. Filters are applied to the stored postings before maxItems is counted, and are sent to LinkedIn's own search for any postings read live.

• queries: a posting matches a query when its title or description contains every word of it, as whole words, ignoring case. A posting matches when any query matches.
• locations: a city, region, country name or two-letter ISO country code. Countries match by name, code and native name (Germany, DE and Deutschland find the same postings), and EU and Europe cover their member countries.
• locationTypes (remote, hybrid, onsite) and employmentTypes (Full-time, Part-time, Contract, Internship): while one is set, a posting whose source does not state that fact is left out.
• postedWithin: a positive duration in hours (h), days (d), weeks (w) or 30-day months (m), up to 36500 days, or any. Postings without a source date use the date they were first seen, which later refreshes never reset.
• maxItems defaults to 100; 0, or anything above 200, means 200.
• dedupe suppresses postings already delivered to the same Apify account for the same search; different filters keep separate histories. Set dedupe.enabled to false to get stateless results, or set dedupe.key to keep separate alert histories.

One flat row per posting in the nomad-agent-job-row-v5 format: schemaVersion, source, id, url, title, company, locations, countryCodes, applicantLocations, postedAt, deadline, description, descriptionHtml, workType, salary, employmentTypes, hiringContacts. employmentTypes lists the types the source states (Full-time, Part-time, Contract, Internship) or is null. countryCodes lists the countries of the job's places as ISO 3166-1 alpha-2 codes (for example DE, FR), in the same order as locations, each once. A code comes from the source if it states one, otherwise from the place label. It's null when no place has a known country (a remote job with no country, or an unidentifiable place) and never an empty list. A place without a known country adds nothing, so the list can name fewer countries than there are places. A posting stored on a single-country board with no place at all carries that board's country, so locations can be [] while countryCodes names one. Postings read live from LinkedIn's public pages always have countryCodes: null. Those pages give a place label but no country code, so only stored postings carry a code. The locations filter matches countries against these codes as well as names and text. applicantLocations lists the regions where the source says an applicant may live (for example United States for a remote job open to US residents), null when it states nothing and [] when it states no restriction. Each hiring contact has a name, and a title and url or null. Newest postings come first. A run summary, including any input field that was mapped or ignored, is written to the RUN-SUMMARY record of the run's key-value store.

Changes

• October 2026: countryCodes added (row v5). Rows are now nomad-agent-job-row-v5: one new field, countryCodes, lists the ISO 3166-1 alpha-2 country codes of the job's places, in the order of locations, each once (null when no place has a known country, never an empty list). A code is the country the source states, or if it doesn't state one, the country read from the place label. A place whose country can't be determined adds nothing. Postings read live from LinkedIn carry null; its public pages show a place label but no country code. locations and applicantLocations are unchanged. Input, other fields, and pricing are unchanged. Integrations validating against the v4 schema must allow the new field and the new schemaVersion.
• October 2026: applicantLocations added (row v4). Rows are now nomad-agent-job-row-v4: one new field, applicantLocations, lists where an applicant may live as the source states it (null when the source states nothing, [] when it states no restriction). locations is unchanged and still the physical place only; for a remote job open to some regions it is often [] while applicantLocations lists the regions. Input, other fields and pricing are unchanged. Integrations that validate rows against the v3 schema must allow the new field and the new schemaVersion.
• October 2026: stored postings first, then live. When fewer than maxItems new postings remain after the stored postings and your dedupe history, the run reads the rest from LinkedIn's public job pages (no login), returns them with the rest, and stores each verified posting for later runs. Rows, input and pricing are unchanged; RUN-SUMMARY.liveTopUp reports what was read and stored.
• October 2026: recordType removed. nomad-agent-job-row-v3 rows no longer include the recordType field, because every dataset row is a posting. Read schemaVersion instead. The RUN-SUMMARY record is unchanged and keeps its own recordType.
• September 2026: search filters and richer rows. The input (nomad-agent-simple-inventory-search-v2) adds queries, locations, locationTypes and employmentTypes. Rows are now nomad-agent-job-row-v3 and add employmentTypes and hiringContacts. Integrations that still send keyword or location keep working: those values become queries and locations, remote: true becomes locationTypes: ["remote"], and other old fields are ignored with a note in RUN-SUMMARY instead of failing the run. Pricing is unchanged.
• Earlier: this Actor moved to verified available postings in the shared simple job format, and every row includes the complete description.

Fast setup and source code

Public repository · Agent setup skill.

Use the Actor’s current input form for filters, or start with its documented API example. Select the latest build. Read the dataset together with the run summary: a successful status alone does not show that every source was reached.

Restrictive filters or repeat-delivery suppression can produce zero results.

Observed output example

Selected fields from a real source record inspected on 2026-10-03; consult the output schema for the full contract. Values change with the source.

{
  "schemaVersion": "nomad-agent-job-row-v3",
  "source": "linkedin",
  "id": "4446805217",
  "url": "https://www.linkedin.com/jobs/view/senior-integratie-specialist-at-medux-4446805217",
  "title": "Senior Integratie Specialist",
  "company": "Medux",
  "locations": [
    "Den Hoorn, South Holland, Netherlands"
  ],
  "postedAt": "2026-10-01",
  "deadline": null,
  "workType": null,
  "salary": null,
  "employmentTypes": [
    "Full-time"
  ],
  "hiringContacts": []
}

Current costs

Current Actor event rates, checked 2026-10-16. USD; use the Pricing tab for your plan and later changes.

Event	Free	Bronze	Silver	Gold	Platinum	Diamond
Job result (result)	$0.0001	$0.0001	$0.000075	$0.00005	$0.00005	$0.00005

For example, 100 × result totals $0.01 in Actor event charges on Free. This is an arithmetic example, before any waiver; actual charged events depend on the run and selected options. It is not a promise of output or a charge for simply setting an item cap.

Your total is the charged Actor events, plus platform usage only if this Actor’s Pricing tab bills it separately, plus any external provider you use with your own key. Do not add platform usage twice when it is included. Apify credits and plan discounts affect your invoice. Set a run cost limit in Console before starting.

---

Independent tool. We built and run this Actor ourselves. LinkedIn does not operate, sponsor or endorse it, and its name is used only to say which site the data comes from.