# LinkedIn Jobs Scraper - No Login, Fast & Cheap (`aolmo/linkedin-jobs`) Actor

Public LinkedIn job postings for any keyword and location, filtered by date, remote, job type and experience: title, company, location, date, salary when shown, full description, seniority and apply link. No login, no cookies, no browser. $0.0005 per job; new jobs flagged on scheduled runs.

- **URL**: https://apify.com/aolmo/linkedin-jobs.md
- **Developed by:** [Antonio del Olmo Tena](https://apify.com/aolmo) (community)
- **Categories:** Jobs
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 job scrapeds

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

Get public LinkedIn job postings for any keyword and location as clean, structured rows. Type the searches you would run on LinkedIn Jobs, or paste search URLs from your browser, and the Actor returns one row per job with title, company, location, posting date, salary when LinkedIn shows it, the full description, seniority, employment type, job function, industries, applicant count and the external apply link. Filter by date posted, remote or hybrid, job type and experience level. Schedule it and every run flags the jobs that are new since the previous one.

No LinkedIn account, no cookies, no browser: the Actor reads the same public endpoints LinkedIn serves to visitors who are not logged in, so it is fast, cheap and does not put any account at risk. You pay $0.0005 per job returned.

### What you get

One Dataset row per job:

- `title`, `url`, `id`, `company`, `companyUrl`, `companyLogo`, `location`.
- `postedAt` (`YYYY-MM-DD`) and `postedText` (`6 days ago`), `salary` and `benefits` when LinkedIn shows them.
- With **Include full description** (default on): `description` as plain text, `seniority`, `employmentType`, `jobFunction`, `industries`, `applicants` and `applyUrl` (the company's own application page when the job applies outside LinkedIn).
- `search`, `keywords`, `searchLocation`: where the row comes from.
- `isNew`: `true` when the job was not in the previous run of that search.

A search with no results returns no rows and is not charged. A search that cannot be read gives a single row with an `error` field, also free.

### How to use it

1. Open the **Input** tab.
2. In **Keywords** type one search per line, for example `python developer` or `marketing manager`, and set **Location** (`Madrid, Spain`, `United States`, `London Area, United Kingdom`...). Or paste **Search URLs** copied from LinkedIn Jobs; their own filters apply.
3. Optionally filter by **Date posted**, **Workplace** (on-site, remote, hybrid), **Job type** and **Experience level**, and choose **Sort by** relevance or most recent.
4. Set **Max jobs per search** (default 100, up to 1,000) and leave **Include full description** on unless you only need the list.
5. Click **Start**. Read the rows in **Output** or export them as JSON, CSV or Excel.
6. To monitor openings, schedule the Actor (hourly or daily) with **Sort by** set to most recent and **Date posted** to the past 24 hours. New jobs come with `isNew: true`; connect a webhook or an email integration to be notified.

### Input

```json
{
  "keywords": ["python developer"],
  "location": "Spain",
  "datePosted": "week",
  "workplace": "remote",
  "sortBy": "date",
  "maxJobs": 100,
  "includeDescription": true
}
```

| Field                | Description |
|----------------------|-------------|
| `keywords`           | Searches, one per line. Up to 50 searches per run (keywords plus URLs). |
| `location`           | City, region or country as LinkedIn names it. Applies to every keyword. |
| `searchUrls`         | LinkedIn job search URLs with their own filters. |
| `datePosted`         | `day`, `week` or `month`. Empty for any time. |
| `workplace`          | `on-site`, `remote` or `hybrid`. |
| `jobType`            | `full-time`, `part-time`, `contract`, `temporary`, `internship`, `volunteer`, `other`. |
| `experience`         | `internship`, `entry`, `associate`, `mid-senior`, `director`, `executive`. |
| `sortBy`             | `relevance` (default) or `date`. |
| `maxJobs`            | Per search, 1 to 1,000. Default 100. |
| `includeDescription` | Fetch each job page for the description and details. Default on. |

### Output example

```json
{
  "search": "https://www.linkedin.com/jobs/search/?keywords=python+developer&location=Spain&f_TPR=r604800&f_WT=2&sortBy=DD",
  "keywords": "python developer",
  "searchLocation": "Spain",
  "id": "4472703950",
  "url": "https://es.linkedin.com/jobs/view/fullstack-software-engineer-net-angular-at-julius-baer-4472703950",
  "title": "FullStack Software Engineer .Net Angular - 100% (f/m/d)",
  "company": "Julius Baer",
  "companyUrl": "https://ch.linkedin.com/company/julius-baer",
  "companyLogo": "https://media.licdn.com/dms/image/v2/.../company-logo_100_100/...",
  "location": "Madrid, Community of Madrid, Spain",
  "postedAt": "2026-09-28",
  "postedText": "6 days ago",
  "salary": null,
  "benefits": null,
  "description": "At Julius Baer, we celebrate and value the individual qualities you bring...",
  "seniority": "Not Applicable",
  "employmentType": "Full-time",
  "jobFunction": "Engineering and Information Technology",
  "industries": "Banking",
  "applicants": "38 applicants",
  "applyUrl": "https://jobs.juliusbaer.com/job/123",
  "isNew": false,
  "timestamp": "2026-10-04T18:00:00.000Z"
}
```

### Pricing

Pay per event, no subscription:

- **Job scraped**: $0.0005 per job row. 1,000 jobs with full descriptions cost $0.50.
- **New job**: $0.002 per job flagged as new in a scheduled run. Runs with nothing new only pay for the rows.

Searches that cannot be read or return nothing are free. Compare with typical LinkedIn job scrapers at $1 to $3 per 1,000 jobs.

### Use it as an API

Run it from your code with the Apify API or client libraries:

```bash
curl -X POST "https://api.apify.com/v2/acts/aolmo~linkedin-jobs/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"keywords": ["data engineer"], "location": "Germany", "datePosted": "day", "maxJobs": 50}'
```

The response is the list of job rows. You can also call it from AI agents through the Apify MCP server. For jobs published on company career pages (Greenhouse, Lever, Ashby...) use the companion Actor `aolmo/jobs-ats`.

### FAQ

**Does it need my LinkedIn account?** No. It only reads what LinkedIn shows to visitors who are not logged in, so there is no account to ban and no cookies to maintain.

**How many jobs can one search return?** Up to 1,000, which is LinkedIn's own limit per search. Split broad searches by location or keyword to cover more.

**Why is `salary` often empty?** LinkedIn only shows a salary when the company publishes it. The description frequently contains it anyway.

**What is in `applyUrl`?** The company's application page when the job redirects outside LinkedIn. For Easy Apply jobs it is empty: those are applied to inside LinkedIn.

**How fresh is the data?** Live: every run queries LinkedIn at that moment. `postedAt` is the date LinkedIn reports for the posting.

**Where is the data stored between runs?** In a Key-Value Store of your account named `micro-saas-state-linkedin-jobs`, one key per search. Delete it to start fresh.

# Actor input Schema

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

One search per line, as you would type it in LinkedIn Jobs, e.g. python developer.

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

City, region or country as LinkedIn names it, e.g. Madrid, Spain or United States. Applies to every keyword.

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

Optional. LinkedIn job search URLs copied from your browser (https://www.linkedin.com/jobs/search/?keywords=...\&location=...). Their own filters are used.

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

Only jobs posted in the last day, week or month. Empty for any time.

## `workplace` (type: `string`):

On-site, remote or hybrid. Empty for all.

## `jobType` (type: `string`):

Empty for all.

## `experience` (type: `string`):

Empty for all.

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

LinkedIn's relevance ranking or most recent first. Use date to monitor new jobs.

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

LinkedIn serves up to 1,000 jobs per search. Also caps what you pay per search.

## `includeDescription` (type: `boolean`):

Fetches each job page for the description, seniority, employment type, job function, industries, applicants and apply link (one extra request per job).

## `product` (type: `string`):

Internal. Leave as is.

## Actor input object example

```json
{
  "keywords": [
    "python developer"
  ],
  "location": "Spain",
  "sortBy": "relevance",
  "maxJobs": 100,
  "includeDescription": true,
  "product": "linkedin-jobs"
}
```

# Actor output Schema

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

Dataset items: url, changed, events, data, timestamp and error (when the target failed).

# 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"
    ],
    "location": "Spain"
};

// Run the Actor and wait for it to finish
const run = await client.actor("aolmo/linkedin-jobs").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"],
    "location": "Spain",
}

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

```

## MCP server setup

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

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/T5bjfOeeMNPSCW7IT/builds/Er7cEuyP850F9fb6T/openapi.json