# LinkedIn Jobs Scraper - Salaries & Descriptions, No Login (`get_anything/linkedin-jobs-scraper`) Actor

Scrape public LinkedIn job listings in any country by keyword and location or search URL. Filter by date, job type, experience, remote/hybrid. Get company, salary, full description, seniority, employment type, industries and applicant count. Monitor mode returns only new jobs. No login or cookies.

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

## Pricing

from $0.84 / 1,000 jobs

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 - Listings, Salaries & Descriptions (No Login)

Scrape **public LinkedIn job listings in any country**. Search by keyword and location, or paste a LinkedIn job search URL. Each job comes with title, company, location, posted date, salary (when listed), and, optionally, the **full description, seniority level, employment type, job function, industries and applicant count**.

Filter by **date posted, job type, experience level, on-site/remote/hybrid** and Easy Apply. Turn on **Monitor mode** and schedule it to get only **new jobs** on each run, which works well for job alerts.

No login, no cookies, no LinkedIn account needed. The Actor only reads LinkedIn's public guest job pages. It never touches personal profiles.

### What you can do with it

- **Job market and salary research:** pull thousands of postings for a role and compare salaries, seniority and demand by city.
- **Recruiting and sales leads:** find companies that are hiring for a role right now (hiring = budget).
- **Job alerts and job boards:** schedule Monitor mode hourly or daily and send new jobs to Slack, email, Sheets or your site.
- **AI agents (ChatGPT, Claude, Cursor via Apify MCP):** "Find remote senior Python jobs posted in the last 24 hours." Output is small and clean by default.

### Input

| Field | Description |
|---|---|
| `keywords` | Job titles or skills (`data engineer`, `nurse`). Each keyword runs in each location. |
| `locations` | `United States`, `London`, `Dubai`, `Germany`, `Remote`... Empty = worldwide. |
| `searchUrls` | Optional LinkedIn search URLs (linkedin.com/jobs/search?...) with filters already set. |
| `maxJobsPerSearch` | Jobs per keyword x location (default 25). `0` = as many as LinkedIn shows (up to ~1,000). |
| `datePosted` | `any`, `24h`, `week`, `month`. |
| `jobTypes` | full-time, part-time, contract, temporary, internship, volunteer, other. |
| `experienceLevels` | internship, entry, associate, mid-senior, director, executive. |
| `workplaceTypes` | on-site, remote, hybrid. |
| `sortBy` | `relevance` or `recent`. |
| `includeDetails` | Open each job for description, criteria and applicants (default on). |
| `onlyNewJobs` + `monitorKey` | Monitor mode: only jobs not returned in earlier runs. |

Example:

```json
{
  "keywords": ["data engineer", "analytics engineer"],
  "locations": ["United States", "London"],
  "datePosted": "week",
  "workplaceTypes": ["remote", "hybrid"],
  "maxJobsPerSearch": 50
}
```

### Output

```json
{
  "jobId": "4481843507",
  "title": "Data Engineer - Mid Level",
  "company": "USAA",
  "companyUrl": "https://www.linkedin.com/company/usaa",
  "location": "Phoenix, AZ",
  "postedAt": "2026-10-27",
  "postedAgo": "1 day ago",
  "salary": null,
  "salaryFromDescription": "$103,450 - $197,730",
  "insight": "Actively Hiring",
  "url": "https://www.linkedin.com/jobs/view/4481843507",
  "description": "Why USAA? ...",
  "seniorityLevel": "Not Applicable",
  "employmentType": "Full-time",
  "jobFunction": "Information Technology",
  "industries": "Financial Services",
  "applicantsCount": 66,
  "easyApply": false,
  "searchKeyword": "data engineer",
  "searchLocation": "United States"
}
```

- `salary` is LinkedIn's own salary field. When it's missing, `salaryFromDescription` holds a pay range found in the description text.
- Jobs are de-duplicated across all your searches in a run.

### Speed and proxies

LinkedIn rate-limits bursts from a single IP, so without a proxy the Actor paces itself (about 25 detailed jobs per minute). For big runs, enable Apify Proxy: the Actor rotates IPs and goes faster. Turning off `includeDetails` roughly halves the requests.

### Use it from ChatGPT, Claude & AI agents

This Actor works as a tool for AI assistants through the **Apify MCP server**, and the inputs are designed so an agent can fill them in.

- **Claude (claude.ai / Desktop), ChatGPT, Cursor, VS Code, Windsurf:** add the MCP server URL below as a custom connector / MCP server and sign in with your Apify account:

  ```
  https://mcp.apify.com/?tools=get_anything/linkedin-jobs-scraper
  ```

- **Claude Desktop / Cursor config file:**

  ```json
  { "mcpServers": { "apify": { "url": "https://mcp.apify.com/?tools=get_anything/linkedin-jobs-scraper" } } }
  ```

- **Any LLM framework or GPT Action (REST):** one call runs the Actor and returns the results as JSON:

  ```
  POST https://api.apify.com/v2/acts/get_anything~linkedin-jobs-scraper/run-sync-get-dataset-items?token=YOUR_TOKEN
  ```

- **No-code:** Make, Zapier, n8n, LangChain and LlamaIndex have Apify integrations.

Then just ask, for example: *"Find remote senior Python jobs in Germany posted in the last 24 hours, with salaries."*

### Pricing

Pay per event: you pay per job returned. See the Pricing tab for current prices.

### FAQ

**Do I need a LinkedIn account or cookies?** No. Only public job pages that LinkedIn shows to logged-out visitors are used.

**Does it scrape people or profiles?** No. It collects job postings only.

**Why fewer jobs than LinkedIn's count?** LinkedIn's public search stops paginating at roughly 1,000 results per search. Split big searches by location or keyword.

**Is it legal?** It reads publicly available job listings. Use the data responsibly and follow applicable laws and LinkedIn's terms.

# Actor input Schema

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

Job titles or skills to search, e.g. 'data engineer', 'nurse', 'python'. Each keyword is searched in each location.

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

Countries, cities or regions as you'd type them on LinkedIn, e.g. 'United States', 'London', 'Dubai', 'Remote'. Leave empty for worldwide.

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

Optional. Paste search URLs from linkedin.com/jobs/search with any filters already applied.

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

Maximum jobs per keyword x location (or per URL). 0 = as many as LinkedIn shows (up to ~1,000).

## `datePosted` (type: `string`):

Only jobs posted within this time window.

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

Only these job types. Empty = all.

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

Only these experience levels. Empty = all.

## `workplaceTypes` (type: `array`):

Only on-site, remote or hybrid jobs. Empty = all.

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

Most relevant or most recent first.

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

Only jobs with LinkedIn Easy Apply.

## `includeDetails` (type: `boolean`):

Open each job for the full description, seniority, employment type, job function, industries and applicant count. Turn off for faster, list-only results.

## `includeDescriptionHtml` (type: `boolean`):

Also return the description as HTML.

## `onlyNewJobs` (type: `boolean`):

Remember job IDs between runs and return only jobs not seen before. Schedule it for job alerts.

## `monitorKey` (type: `string`):

Separate monitors keep separate memories, e.g. 'nyc-data-jobs'.

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

Optional. With a proxy the Actor rotates IPs and runs faster on big searches.

## Actor input object example

```json
{
  "keywords": [
    "data engineer"
  ],
  "locations": [
    "United States"
  ],
  "maxJobsPerSearch": 10,
  "datePosted": "any",
  "sortBy": "relevance",
  "easyApplyOnly": false,
  "includeDetails": true,
  "includeDescriptionHtml": false,
  "onlyNewJobs": false,
  "monitorKey": "default",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

Structured results in the default dataset - one item per job posting.

# 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": [
        "data engineer"
    ],
    "locations": [
        "United States"
    ],
    "maxJobsPerSearch": 10,
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("get_anything/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": ["data engineer"],
    "locations": ["United States"],
    "maxJobsPerSearch": 10,
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("get_anything/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": [
    "data engineer"
  ],
  "locations": [
    "United States"
  ],
  "maxJobsPerSearch": 10,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call get_anything/linkedin-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,get_anything/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/TrvNvgTYFZtHsJUdT/builds/MT5SeKDj8md7dLfBI/openapi.json
