LinkedIn Jobs Scraper — Simple Job Feed, No Login

Start with one input and output

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. It used an earlier build; current-build execution has not been proved by this example.

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 no usable location was published, and an empty hiringContacts array means the source names nobody.

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 available postings first, so a request the available 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 available postings are still returned, RUN-SUMMARY.liveTopUp says what was read, and the run is marked partial.

Input

{"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 available 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.

Output

One flat row per posting in the nomad-agent-job-row-v3 format: schemaVersion, source, id, url, title, company, locations, postedAt, deadline, description, descriptionHtml, workType, salary, employmentTypes, hiringContacts. employmentTypes lists the types the source states (Full-time, Part-time, Contract, Internship) or is null. 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: available postings first, then live. When fewer than maxItems new postings remain after the available 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 latest for linkedin-scraper and record the immutable build ID and number returned by your run. Inspect the dataset and any run summary the Actor documents together; a successful status alone does not establish complete source coverage.

Restrictive filters or repeat-delivery suppression can produce zero results. Diagnostics and demo records are not source records. Optional AI or translation stays explicit where supported.

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": []
}

Product guides and related tools

• 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

Current costs

Current Actor event rates, checked 2026-10-04. 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.0001	$0.0001	$0.0001	$0.0001

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.