# LinkedIn Jobs API & Job Scraper - Live Job Search (`jobspipe/linkedin-jobs-scraper`) Actor

LinkedIn jobs API and job scraper: search LinkedIn jobs by keyword, location and date, fetched live. Clean JSON with company, salary, seniority and full description. Pay only for jobs delivered.

- **URL**: https://apify.com/jobspipe/linkedin-jobs-scraper.md
- **Developed by:** [JobsPipe](https://apify.com/jobspipe) (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

$2.00 / 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.

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 API & Job Scraper - Live Job Search

**A LinkedIn jobs API and LinkedIn job scraper in one: search LinkedIn jobs by keyword and location, fetched live when your run starts.** LinkedIn is the largest professional network and job board, with postings from employers and recruiters in every country. Enter what you are looking for and get matching jobs as clean JSON, CSV or Excel.

- **Live, not a stale database.** Each run searches at run time, so you get what is listed right now.
- **Same schema as the [JobsPipe API](https://docs.jobspipe.dev).** Every row is the exact job object the JobsPipe API returns: normalized title, seniority, location, salary in USD and full description, so LinkedIn data drops straight into the same pipeline as every other source.
- **Pay only for jobs delivered.** An empty or failed search costs nothing. If a search fails part-way, the jobs already delivered are kept (and charged) and the run status says why it stopped.

Also searched as: `linkedin jobs api`, `linkedin job scraper`, `linkedin job api`, `linkedin jobs scraper`, `scrape linkedin jobs`.

### Input

| Field | What it does |
|---|---|
| **Job title or keywords** (`keywords`) | What to search for (required) |
| **Location** (`location`) | City, region or country; blank for everywhere |
| **Posted within (days)** (`postedWithinDays`) | Only jobs posted in the last N days |
| **Remote jobs only** (`remote`) | Only remote jobs |
| **Max jobs** (`maxJobs`) | Stop after this many jobs (default 100, up to 1,000) |

Popular searches on LinkedIn: `data engineer`, `software engineer`, `product manager`, `account executive`.

```json
{
  "keywords": "data engineer",
  "location": "Berlin, Germany",
  "postedWithinDays": 7,
  "maxJobs": 100
}
```

Another example, software engineer jobs from the last week:

```json
{
  "keywords": "software engineer",
  "postedWithinDays": 7,
  "maxJobs": 100
}
```

### Output

One dataset item per job. The **Jobs**, **Salaries**, **Companies hiring** and **Recruiter contacts** tabs show different columns of the same data. Main fields:

| Field | Description |
|---|---|
| `id` | Stable JobsPipe job id, the same one the JobsPipe API returns |
| `job_title` | Title as posted |
| `company` / `company_domain` | Employer name and website domain where known |
| `url` | Link to the posting a person can open |
| `location` / `country_code` / `cities` | Location as posted, ISO country code and parsed cities |
| `remote` / `work_arrangement` | Remote flag and remote / hybrid / on-site where stated |
| `date_posted` | Posting date (YYYY-MM-DD) |
| `seniority` / `employment_statuses` | Normalized seniority and employment type |
| `salary_string` | Pay as written in the posting |
| `min_annual_salary_usd` / `max_annual_salary_usd` | Posted pay converted to annual USD |
| `estimated_min_annual_salary_usd` / `estimated_max_annual_salary_usd` | Benchmark pay estimate when the posting has none |
| `description` | Full job description |
| `skills` / `benefits` / `visa_sponsorship` | Skills, benefits and visa stance read from the posting |
| `recruiter_emails` | Recruiter emails, only where the posting publishes them |
| `sources` | The board this job was fetched from |

Fields a posting does not publish are `null`. The full field list is in the [JobsPipe API docs](https://docs.jobspipe.dev).

**History fields are null on live results.** `closed_at` and `ghost_score` need a posting's history over time (when it closed, how long it has been reposted), which a live fetch cannot know. Use the [JobsPipe API](https://docs.jobspipe.dev) if you need them.

### Pricing

**$2.00 per 1,000 jobs** ($0.20 per 100). You pay only for jobs delivered to your dataset; error rows and empty runs are free. The run stops at your job limit or your spending limit, whichever comes first. Apify bills the platform usage of the run separately; at 256 MB that is a few cents at most.

### Integrations

- **Apify API and SDKs**: start runs and read datasets from any language (see the **API** tab).
- **n8n, Make, Zapier, Clay, Google Sheets, Slack, webhooks**: send new jobs wherever you need them.
- **AI agents**: available through the [Apify MCP server](https://mcp.apify.com).

### More JobsPipe Actors

Every JobsPipe Actor returns the same job schema, so you can combine sources in one pipeline.

**Other job boards, searched live:**

- [Indeed Scraper & Jobs API - Live Indeed Job Search](https://apify.com/jobspipe/indeed-jobs-scraper)

**Company career sites, fetched live:**

- [Workday Jobs API & Scraper - Live myworkdayjobs.com](https://apify.com/jobspipe/workday-jobs-scraper)
- [Greenhouse Job Board API & Jobs Scraper - Live Data](https://apify.com/jobspipe/greenhouse-jobs-scraper)
- [Lever Jobs API & Scraper - Live jobs.lever.co Postings](https://apify.com/jobspipe/lever-jobs-scraper)

**Search every source at once:** [Jobs Scraper API: LinkedIn, Indeed & 30+ Job Boards](https://apify.com/jobspipe/jobspipe-job-search) searches all of them in one run, with salary, seniority and visa filters and duplicates removed.

See every JobsPipe Actor on the [JobsPipe profile](https://apify.com/jobspipe), or use the same data through the [JobsPipe API](https://docs.jobspipe.dev).

### FAQ

**Is there a LinkedIn jobs API?** LinkedIn does not offer a public API for searching its job listings; its job APIs are for approved partners that post jobs. This Actor works as an API for LinkedIn jobs: start it from the Apify API (or any integration) with your keywords and location and read the matching jobs back as JSON, in the same JobsPipe schema as every other source.

**How do I scrape LinkedIn jobs?** Enter a job title or keywords (for example `data engineer`) and, if you like, a location, then start the run. Matching jobs arrive as dataset rows you can download as JSON, CSV or Excel or read through the Apify API. Schedule the Actor to collect new LinkedIn jobs every day.

**How fresh is the data?** Live. Every run fetches the jobs when it starts, so you get what is listed at that moment, not a copy from days ago.

**Is it legal?** The Actor reads publicly listed job postings. It does not log in anywhere or collect private profiles. Make sure your use of the data complies with the laws that apply to you, such as GDPR.

**Something is wrong or missing?** Open an issue in the **Issues** tab and we will look into it.

# Actor input Schema

## `keywords` (type: `string`):

What to search LinkedIn for, e.g. "data engineer", "software engineer", "product manager".

## `location` (type: `string`):

City, region or country. Leave blank to search everywhere.

## `postedWithinDays` (type: `integer`):

Only jobs posted in the last N days. Leave blank for any date.

## `remote` (type: `boolean`):

Only jobs that can be done remotely.

## `maxJobs` (type: `integer`):

Stop after this many jobs. You pay only for jobs delivered.

## Actor input object example

```json
{
  "keywords": "data engineer",
  "location": "Berlin, Germany",
  "postedWithinDays": 7,
  "remote": false,
  "maxJobs": 100
}
```

# Actor output Schema

## `jobs` (type: `string`):

One item per job posting, with the full record.

## `salaries` (type: `string`):

Posted and estimated pay per job.

## `companies` (type: `string`):

Employers and roles, for lead generation.

## `contacts` (type: `string`):

Postings that list a recruiter email.

## `summary` (type: `string`):

Jobs delivered and why the run stopped.

# 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",
    "location": "Berlin, Germany",
    "postedWithinDays": 7
};

// Run the Actor and wait for it to finish
const run = await client.actor("jobspipe/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",
    "location": "Berlin, Germany",
    "postedWithinDays": 7,
}

# Run the Actor and wait for it to finish
run = client.actor("jobspipe/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",
  "location": "Berlin, Germany",
  "postedWithinDays": 7
}' |
apify call jobspipe/linkedin-jobs-scraper --silent --output-dataset

```

## MCP server setup

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