# LinkedIn Jobs Scraper (`devilscrapes/linkedin-jobs-scraper`) Actor

Export LinkedIn job postings by keyword and location from LinkedIn's public guest jobs search — title, company, location, posting date, job URL. Batch multiple keyword/location searches in one run, fault-isolated. JSON/CSV export.

- **URL**: https://apify.com/devilscrapes/linkedin-jobs-scraper.md
- **Developed by:** [DevilScrapes](https://apify.com/devilscrapes) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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/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

<div align="center">
  <img src=".actor/icon.svg" width="160" alt="Devil Scrapes mark" />

## LinkedIn Jobs Scraper

**💰 $3.20 / 1 000 results**  ·  pay only for results  ·  no credit card to try

*We do the dirty work so your dataset stays clean.* 😈

Export LinkedIn job postings by keyword and location — job title, company, location, posting date, and job URL. Batch multiple keyword/location searches in one run, fault-isolated per search. JSON/CSV export.

</div>

***

### 🎯 What this scrapes

Point this Actor at one or more job-title keywords and one or more locations, and it runs the full cross product as independent searches against LinkedIn's public guest jobs search. Each search unit walks the result pages until it reaches the end of that search's job list or a safety cap you set. Every job card is parsed into a typed row — title, company name and LinkedIn URL, the job's own location, a cleaned job URL, posting date, and an optional benefit/status label. Multiple keyword/location pairs run in the same batch, and one pair's error never sinks the others.

### 🔥 What we handle for you

- 🛡️ **Browser fingerprint rotation** — `curl-cffi` replays a real browser's TLS handshake (Chrome and Firefox profiles), rotated per request.
- 🔁 **Retries with exponential backoff** on `408 / 429 / 503` and network errors — up to 5 attempts, `Retry-After` honoured.
- 🧱 **Per-search fault isolation** — a failed or empty keyword/location pair is logged and skipped; every other pair in the batch still runs.
- 🧊 **Clean, typed dataset rows** — Pydantic-validated, deduplicated by job id, ISO-8601 timestamps, JSON / CSV / Excel export straight from the Apify Console.
- 💰 **Pay-Per-Event pricing** — you only pay for job rows that land in your dataset. No data, no charge.

### 💡 Use cases

- **Talent sourcing** — pull fresh postings for a role/location combo to see which companies are hiring right now.
- **Market and salary research** — batch a role across multiple cities or countries to gauge hiring volume and posting cadence.
- **Recruiting agency lead gen** — find companies actively posting a given role as warm outreach targets.
- **Job board aggregation** — feed a clean, typed dataset of LinkedIn postings into your own job board or alert pipeline.

### ⚙️ How to use it

1. Click **Try for free** at the top of the page.
2. Add one or more job-title keywords to `keywords`; add one or more locations to `locations` — most other fields have sensible defaults.
3. Click **Start**. Rows stream into the run's dataset as each keyword/location pair is searched.
4. Export from **Storage → Dataset** as JSON, CSV, or Excel — or fetch via the API.

### 📥 Input

| Field | Type | Required | Default | Notes |
|---|---|:--:|---|---|
| `keywords` | `array` | **yes** | `["python developer", "data engineer"]` | Job-title/keyword searches — one guest jobs search per item, run against every location. |
| `locations` | `array` | no | `["United States"]` | Locations to search. The Actor runs the full keywords x locations cross product. |
| `maxPagesPerSearch` | `integer` | no | `10` | Safety cap on the offset-walk depth (10 job cards per page) for one search unit. |
| `maxJobsPerSearch` | `integer` | no | `100` | Cap on job rows collected for a single search unit before its walk stops early. |
| `maxTotalResults` | `integer` | no | `500` | Cap on total job rows emitted across the whole run. |
| `maxRunSeconds` | `integer` | no | `600` | Wall-clock budget across all search units; the run ships whatever it collected so far. Capped at 3 480s, below the platform's own hard limit. |
| `proxyConfiguration` | `object` | no | `{"useApifyProxy": true}` | Apify Proxy config — defaults to a bare flag (DATACENTER); every probe of this specific endpoint cleared direct and unproxied. |

#### Example input

```json
{
  "keywords": ["python developer", "data engineer"],
  "locations": ["United States", "United Kingdom"],
  "maxJobsPerSearch": 100,
  "maxTotalResults": 500,
  "maxRunSeconds": 600,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

### 📤 Output

Every row is one parsed job posting.

| Field | Type | Notes |
|---|---|---|
| `search_keyword` | `string` | The input keyword searched (echoed, not re-parsed). |
| `search_location` | `string` | The input location searched (echoed, not re-parsed). |
| `job_id` | `string` | Numeric job id parsed from the card's `data-entity-urn`. |
| `title` | `string` | Job title. |
| `company_name` | `string \| null` | Hiring company name. |
| `company_url` | `string \| null` | Company's LinkedIn URL, when present. |
| `location` | `string \| null` | The job's own location string (may differ from the search's input location). |
| `job_url` | `string \| null` | Cleaned canonical job URL — tracking query params stripped. |
| `posted_at` | `string \| null` | ISO calendar date (`YYYY-MM-DD`) the job was listed. |
| `posted_text` | `string \| null` | Human-readable posting age, e.g. `"2 months ago"`. |
| `benefit_label` | `string \| null` | Optional benefit/status label LinkedIn shows on the card (e.g. `"Actively Hiring"`). |
| `page_number` | `integer` | 1-based page within this search unit's offset walk. |
| `scraped_at` | `string` | ISO-8601 UTC timestamp at parse time. |

#### Example output

```json
{
  "search_keyword": "data engineer",
  "search_location": "United States",
  "job_id": "3812345678",
  "title": "Senior Data Engineer",
  "company_name": "Acme Corp",
  "company_url": "https://www.linkedin.com/company/acme-corp",
  "location": "Austin, TX",
  "job_url": "https://www.linkedin.com/jobs/view/3812345678",
  "posted_at": "2026-09-10",
  "posted_text": "1 week ago",
  "benefit_label": "Actively Hiring",
  "page_number": 1,
  "scraped_at": "2026-09-17T14:03:22.104Z"
}
```

### 💰 Pricing

Pay-Per-Event — you pay only when these events fire:

| Event | USD | What it is |
|---|---:|---|
| `actor-start` | **$0.20** | Base fee, once per run (warm-up, proxy resolution) |
| `job-result` | **$0.003** | Per job-posting row written to the dataset |

Example: 1 000 job rows in one run ≈ **$3.20** ($0.20 + 1 000 × $0.003). No subscription, no minimum — Apify gives every new account free trial credit.

### 🚧 Limitations

- **Real page size is 10 job cards per response**, not 50 — size `maxJobsPerSearch` / `maxPagesPerSearch` with that in mind.
- **Default proxy tier is DATACENTER**, not RESIDENTIAL — a bare `{"useApifyProxy": true}`. Every probe of this specific guest endpoint (both browser profiles, multiple pagination offsets, both stop-condition signals) cleared direct and unproxied with no anti-bot signal observed. Add `apifyProxyGroups: ["RESIDENTIAL"]` yourself if you ever see blocking on your account.
- **A broad or nonsense keyword can still return generic matches instead of zero results.** That's LinkedIn's own guest-search fallback behavior — this Actor doesn't add or remove client-side relevance filtering, so a very loose search may return jobs you didn't expect.
- When a search unit's walk stops early, the run's status message is prefixed `[TRUNCATED]` instead of `[COMPLETE]`, so you always know whether you got everything or hit a cap.
- No login or session persistence — every request is anonymous, reading only what LinkedIn's guest jobs search already serves to a public visitor.

### ❓ FAQ

**Is this legal?**

We only fetch what LinkedIn's public guest jobs search already serves to anonymous visitors — no login, no session cookies, no credential harvesting. Respect LinkedIn's terms of service before using output commercially.

**What if a keyword/location pair has no jobs?**

The run still succeeds. That pair's rows are simply zero, and the status message says so — a real zero-match result is never treated as a failure.

**Why does my run say `[TRUNCATED]` instead of `[COMPLETE]`?**

`[TRUNCATED]` means at least one search unit's walk stopped before reaching the end of its result list — a safety cap (`maxJobsPerSearch`, `maxPagesPerSearch`, `maxTotalResults`, or `maxRunSeconds`) was hit first. This Actor bills per row, so we never let a partial run's status message read the same as a finished one. Raise the relevant cap and re-run for the rest.

**Why are some fields null?**

LinkedIn's guest-search markup doesn't guarantee every field on every card — for example, not every posting carries a benefit/status label. We never fabricate a value — unconfirmed fields come back null rather than a guess.

**Can I track new postings over time?**

Each run is a single snapshot. Schedule the Actor daily/weekly in Apify Console and diff successive dataset exports to catch new listings.

### 💬 Your feedback

Spotted a bug, hit a weird edge case, or need a new field? Open an
issue on the Actor's **Issues** tab on Apify Console — we ship
fixes weekly and we read every report.

***

<div align="center">

Built by **[Devil Scrapes](https://apify.com/DevilScrapes)** 😈 — a small fleet of
opinionated public-data Actors. Honest pricing, real engineering, zero fine print.

</div>

# Changelog

This Actor's version history is a separate document: https://apify.com/devilscrapes/linkedin-jobs-scraper/changelog.md

# Actor input Schema

## `keywords` (type: `array`):

Job-title/keyword searches (e.g. "python developer") — one LinkedIn guest jobs search per item, run against every location below.

## `locations` (type: `array`):

Locations to search (e.g. "United States"). The Actor runs the full keywords x locations cross product as independent, fault-isolated search units.

## `maxPagesPerSearch` (type: `integer`):

Safety cap on the offset-walk depth (steps of 10 job cards per page) for one keyword/location search unit, independent of the empty-body/offset-ceiling stop conditions.

## `maxJobsPerSearch` (type: `integer`):

Cap on job rows collected for a single keyword/location search unit before its walk stops early.

## `maxTotalResults` (type: `integer`):

Cap on total job rows emitted across the whole run (cost/safety cap).

## `maxRunSeconds` (type: `integer`):

Wall-clock budget across all search units; the run ships whatever it collected so far rather than timing out ungracefully. Capped below the platform's 3600s hard kill by a 120s safety margin.

## `proxyConfiguration` (type: `object`):

Apify Proxy routing. Defaults to a bare `{"useApifyProxy": true}` (no group set), which Apify resolves to DATACENTER — every probe of this specific guest endpoint (both browser impersonation profiles, all pagination offsets, both stop-condition signals) cleared direct and unproxied, with no anti-bot signal observed. Override to add `apifyProxyGroups: ["RESIDENTIAL"]` if you see blocking.

## Actor input object example

```json
{
  "keywords": [
    "python developer",
    "data engineer"
  ],
  "locations": [
    "United States",
    "United Kingdom"
  ],
  "maxPagesPerSearch": 10,
  "maxJobsPerSearch": 100,
  "maxTotalResults": 500,
  "maxRunSeconds": 600,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `datasetItems` (type: `string`):

All dataset items as JSON.

## `datasetItemsCsv` (type: `string`):

Same data exported to CSV.

## `datasetView` (type: `string`):

Open the run dataset in the Console.

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "python developer",
        "data engineer"
    ],
    "locations": [
        "United States",
        "United Kingdom"
    ],
    "maxPagesPerSearch": 10,
    "maxJobsPerSearch": 100,
    "maxTotalResults": 500,
    "maxRunSeconds": 600,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("devilscrapes/linkedin-jobs-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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": [
        "python developer",
        "data engineer",
    ],
    "locations": [
        "United States",
        "United Kingdom",
    ],
    "maxPagesPerSearch": 10,
    "maxJobsPerSearch": 100,
    "maxTotalResults": 500,
    "maxRunSeconds": 600,
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("devilscrapes/linkedin-jobs-scraper").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 '{
  "keywords": [
    "python developer",
    "data engineer"
  ],
  "locations": [
    "United States",
    "United Kingdom"
  ],
  "maxPagesPerSearch": 10,
  "maxJobsPerSearch": 100,
  "maxTotalResults": 500,
  "maxRunSeconds": 600,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call devilscrapes/linkedin-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,devilscrapes/linkedin-jobs-scraper"
        }
    }
}
```

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 <APIFY_API_TOKEN>` 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/un7NlqsPuzDTozQ8d/builds/UnumLnJB3aJ2Jw7C1/openapi.json