# 🌟LinkedIn Jobs Scraper – Multi Title × Location (`databuddy/linkedin-jobs-scraper-multi-title-x-location`) Actor

Scrape LinkedIn jobs for many titles and locations in one run. Full details, applicants, salary, deduplicated. No login needed.

- **URL**: https://apify.com/databuddy/linkedin-jobs-scraper-multi-title-x-location.md
- **Developed by:** [Sarthak](https://apify.com/databuddy) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 2 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $2.00 / 1,000 job with full details

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

## LinkedIn Jobs Scraper – Multi Title × Multi Location (Full Details)

Scrape LinkedIn jobs for **many job titles across many locations in one run**, with the **full job page** for every result. No login, no cookies.

### Why this scraper

| | This actor | Typical scrapers |
|---|---|---|
| Titles × locations in one run | ✅ every title in every location | often one at a time |
| Paste LinkedIn search URLs | ✅ keeps all URL filters | ❌ |
| Full job description (HTML + clean text) | ✅ | partial |
| Seniority, employment type, industries, job function | ✅ | partial |
| Applicant count (number) | ✅ | text only |
| Recruiter name, title, profile | ✅ when shown | ❌ |
| Emails found in the description | ✅ | ❌ |
| Easy Apply vs External detection | ✅ | ✅ |
| Cross-search deduplication | ✅ a job appears once per run | ❌ duplicates billed |
| Exclude titles / companies (e.g. agencies) | ✅ | ❌ |
| Per-search and total result caps | ✅ predictable cost | per search only |
| Fast listing-only mode | ✅ | ❌ |
| Exact job-title matching ("AI Engineer" never returns "Electrical Engineer") | ✅ | ❌ LinkedIn's fuzzy search |
| Verified work type (on-site / remote / hybrid) with the exact proof phrase | ✅ | ❌ trusts LinkedIn's filter |
| Survives throttling | ✅ session rotation + exponential backoff, falls back to card data | ❌ |

### Input

```json
{
  "jobTitles": ["Software Engineer", "Data Analyst"],
  "locations": ["London", "New York", "Berlin"],
  "postedWithin": "week",
  "workTypes": ["remote", "hybrid"],
  "experienceLevels": ["entry", "associate"],
  "maxResultsPerSearch": 200,
  "maxResultsTotal": 1000,
  "excludeCompanies": ["Jobot", "Hays"],
  "scrapeJobDetails": true
}
```

Filters: date posted (1h / 24h / week / month), work type, job type, experience level, Easy Apply only, under 10 applicants, company IDs, distance, sort order.

### Output (one row per unique job)

Every record has the **same 42 fields in the same order on every run** (`schemaVersion: 2`). Missing values are `null`; `jobId` is a stable string for deduplication.

| Field | Values |
|---|---|
| `jobId` | LinkedIn job ID (string) |
| `workType` | always `remote`, `hybrid`, `on-site` or `unknown` (never null) |
| `isRemoteAllowed` | `true` for remote or hybrid, otherwise `false` |
| `workTypeSource` / `workTypeEvidence` | `title`, `location`, `description` or `none`, plus the exact phrase used |
| `postedAt` / `postedDate` | ISO 8601 timestamp / `YYYY-MM-DD` |
| `salary`, `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryPeriod` | from LinkedIn's salary box, else a pay range in the description; period is `year`, `month`, `week`, `day` or `hour` |
| `salarySource` | `linkedin`, `description` or `none` |

Also included: title, company, location, applicants, benefits, contract type, experience level, sector, job function, apply type and URL, job URL, company URL, poster name and profile URL, emails in the description, description (text and HTML), promoted/closed flags, `hasFullDetails`, and the search that found the job.

**Why work type can be `unknown`:** LinkedIn hides its On-site / Hybrid / Remote tag from logged-out visitors, so the actor reads the job post itself. This covers LinkedIn workplace hashtags, statements such as "As a hybrid employee" or "3 days a week in the office", and negations such as "No hybrid or remote". When a post never states it, the answer is `unknown`, never a guess.

### Exact job titles

LinkedIn's keyword search is fuzzy: "AI Engineer" also returns "Electrical Engineer" and "Machine Learning Engineer". This actor checks every job title against your keyword before opening the job, so mismatches are skipped and **never charged**.

- **Exact phrase** (default): the title must contain your whole keyword, words in order. "AI Engineer" keeps "Senior AI Engineer" and "Applied AI Engineer", and skips "AI Software Engineer".
- **All words, any order**: every word must be in the title. "AI Engineer" also keeps "AI Software Engineer" and "Engineer, AI Platform".
- **Off**: keep everything LinkedIn returns.
- Spelling variants count as the same: Full-Stack = Fullstack = Full Stack, A.I. = AI = Artificial Intelligence, ML = Machine Learning, Sr = Senior.
- Boolean keywords such as `python AND django` require every term; queries with `OR` / `NOT` are left as you wrote them.

### Accurate work type, experience level and job type

LinkedIn **ignores the work type, experience level and job type filters for logged-out visitors**, so most scrapers return "remote" jobs that are really on-site. This actor checks every job itself:

- **Work type** is read from the job's own post, in this order: the job title, LinkedIn workplace tags (`#LI-Remote`, `#LI-Hybrid`, `#LI-Onsite`), statements about the role ("This position is remote within the US", "hybrid, 3 days a week in the office"), then general wording in the post. `workTypeEvidence` shows the exact phrase used.
- If a post never states it, `workType` is empty. It is never guessed.
- **Experience level** and **job type** are checked against what the job page shows.
- Jobs that don't match are **skipped and not charged**, and the actor keeps searching until each search reaches your requested number.
- Turn on **Include jobs that don't state it** to also get posts that don't state the detail (many employers leave seniority as "Not Applicable").
- With a single work type selected, that word is added to the LinkedIn keyword search to find matching posts faster.

### Daily scheduled runs without repeats

Turn on **Skip jobs from previous runs** and schedule the actor daily. Jobs delivered by an earlier run are skipped and not charged, so each run returns only new jobs. This lets you search **Past week** every day and still get no repeats. Use a different **History name** for each separate scheduled search.

#### Notes

- `applyUrl` is filled when LinkedIn shows the external link to logged-out visitors; most jobs keep it behind sign-in, so `applyType` (`external` / `easy_apply`) and `jobUrl` are always provided.
- LinkedIn shows at most ~1,000 results per search. Split broad searches by location or date for more.
- Residential proxies give the best reliability at high volume.

### Pricing

Pay only for the jobs you get:

| Event | When it is charged |
|---|---|
| Actor start | Once per run |
| Job with full details | Each unique job saved with `scrapeJobDetails: true` |
| Job listing | Each unique job saved in fast listing-only mode |

- Duplicates and excluded jobs are **never charged**.
- Set **Max cost per run** and the actor stops cleanly when it is reached, keeping everything scraped so far.

# Actor input Schema

## `jobTitles` (type: `array`):

One search per title. Boolean operators work (e.g. "python AND django").

## `titleMatch` (type: `string`):

LinkedIn's search is fuzzy ("AI Engineer" also returns "Electrical Engineer"). Exact phrase (default): the job title must contain your whole keyword, words in order ("Senior AI Engineer" yes, "AI Software Engineer" no). All words: every word of your keyword must be in the title, any order. Off: keep everything LinkedIn returns. Spelling variants count as the same (Full-Stack = Fullstack, A.I. = AI = Artificial Intelligence). Non-matching jobs are skipped and never charged.

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

Every title is searched in every location. Use "Worldwide" for no location filter.

## `searchUrls` (type: `array`):

Paste linkedin.com/jobs/search URLs directly. Their own filters are kept. Runs in addition to titles × locations.

## `maxResultsPerSearch` (type: `integer`):

Limit per title × location combination. LinkedIn exposes up to ~1,000 per search.

## `maxResultsTotal` (type: `integer`):

Hard cap for the whole run (0 = no cap). Controls your cost.

## `postedWithin` (type: `string`):

Only return jobs posted within this time window.

## `workTypes` (type: `array`):

On-site, remote and/or hybrid. LinkedIn hides its workplace tag from logged-out visitors and ignores this filter, so each job is checked against its own title and description. Output workType is always 'remote', 'hybrid', 'on-site' or 'unknown'; workTypeEvidence shows the exact phrase used. Non-matching jobs are skipped and not charged.

## `includeUnclearJobs` (type: `boolean`):

Off (default, recommended): with a work type filter, only jobs whose post clearly states remote / hybrid / on-site are saved, so the Work Type column is never blank. With experience or job type filters, only jobs that state them are saved. On: also save jobs where the detail is not stated (Work Type left blank).

## `jobTypes` (type: `array`):

Full-time, contract, internship, etc. Verified against the employment type shown on each job page; non-matching jobs are skipped and not charged.

## `experienceLevels` (type: `array`):

Seniority levels to include. Verified against the seniority shown on each job page; non-matching jobs are skipped and not charged.

## `easyApplyOnly` (type: `boolean`):

Only return jobs that use LinkedIn Easy Apply.

## `under10Applicants` (type: `boolean`):

Only jobs with fewer than 10 applicants (early-bird jobs).

## `companyIds` (type: `array`):

Restrict to LinkedIn numeric company IDs (e.g. 1441 for Google).

## `distanceMiles` (type: `integer`):

Radius around each location. Leave empty for LinkedIn default.

## `sortBy` (type: `string`):

Most recent first, or LinkedIn relevance order.

## `scrapeJobDetails` (type: `boolean`):

Full description, salary, seniority, industries, applicants, apply type, recruiter. Turn off for a fast, cheaper listing-only run. Always on when work type, experience level or job type filters are used.

## `excludeKeywords` (type: `array`):

Case-insensitive. E.g. "Senior", "Lead".

## `excludeCompanies` (type: `array`):

Case-insensitive company names to skip (e.g. recruiting agencies).

## `skipPreviouslyScraped` (type: `boolean`):

For scheduled daily runs: jobs already delivered by an earlier run (with the same history name) are skipped and not charged, so every run gives only new jobs. Lets you search a wider window such as "Past week" every day without repeats. History is kept for 90 days.

## `historyName` (type: `string`):

Name of the key-value store in your account that remembers delivered jobs. Use a different name for each separate search you schedule.

## `maxConcurrency` (type: `integer`):

Parallel requests. Higher is faster; with residential proxies 25 is a good default.

## `maxRequestsPerMinute` (type: `integer`):

Throttle for LinkedIn requests. Leave empty for automatic: 400/min with a proxy, 60/min without.

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

Residential proxies give the most reliable results on LinkedIn.

## Actor input object example

```json
{
  "jobTitles": [
    "Software Engineer",
    "Data Analyst"
  ],
  "titleMatch": "exact",
  "locations": [
    "London",
    "New York"
  ],
  "maxResultsPerSearch": 100,
  "maxResultsTotal": 0,
  "postedWithin": "any",
  "workTypes": [],
  "includeUnclearJobs": false,
  "jobTypes": [],
  "experienceLevels": [],
  "easyApplyOnly": false,
  "under10Applicants": false,
  "sortBy": "recent",
  "scrapeJobDetails": true,
  "skipPreviouslyScraped": false,
  "historyName": "linkedin-jobs-history",
  "maxConcurrency": 25,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `results` (type: `string`):

All scraped jobs shown in the Overview table view.

## `runSummary` (type: `string`):

Number of jobs saved per search, unique jobs found and jobs excluded by filters.

# 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 = {
    "jobTitles": [
        "Software Engineer",
        "Data Analyst"
    ],
    "locations": [
        "London",
        "New York"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("databuddy/linkedin-jobs-scraper-multi-title-x-location").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 = {
    "jobTitles": [
        "Software Engineer",
        "Data Analyst",
    ],
    "locations": [
        "London",
        "New York",
    ],
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("databuddy/linkedin-jobs-scraper-multi-title-x-location").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 '{
  "jobTitles": [
    "Software Engineer",
    "Data Analyst"
  ],
  "locations": [
    "London",
    "New York"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call databuddy/linkedin-jobs-scraper-multi-title-x-location --silent --output-dataset

```

## MCP server setup

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

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/dZJo4GcASfOzHtauz/builds/17SWEP3yKqV7E7x1v/openapi.json