# LinkedIn Jobs Scraper — No Login or Cookies (`automation_craft/linkedin-jobs-scraper`) Actor

Scrape LinkedIn public job search without login: title, company, location, REAL posted dates, salary when shown, and full descriptions. Duplicates never double-charged. Honest about LinkedIn limits.

- **URL**: https://apify.com/automation\_craft/linkedin-jobs-scraper.md
- **Developed by:** [Automation Craft](https://apify.com/automation_craft) (community)
- **Categories:** Jobs
- **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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## LinkedIn Jobs Scraper — No Login, Real Dates, No Duplicate Charges

Scrape LinkedIn's **public job search** — the listings anyone can see without an account — into clean structured data: title, company (with company page link), location, the **real posted date** from the listing, salary when LinkedIn shows one, and optionally the **full job description** with seniority, employment type, job function, industries, applicant count, and the external apply URL when the company uses one.

No LinkedIn account, no cookies, no session to get banned. Built to fix the complaints that fill this category's reviews.

### What makes this one different

| Common complaint about LinkedIn job scrapers | How this Actor handles it |
|---|---|
| "Lots of duplicates — charged 3× for the same job" | Jobs are deduplicated by job ID within the run. **A duplicate is never charged.** The status record even tells you how many were skipped free. |
| "Irrelevant results, keywords not respected" | LinkedIn's public search matches broadly by design — and when nothing matches, it substitutes generic jobs with no warning. The **strict title filter** keeps only jobs whose title contains all your keywords; filtered jobs cost nothing. |
| "24-hour filter returned 2-week-old jobs with today's date" | Date filters are passed to LinkedIn as-is, and every job carries the **real `postedAt` date** from the listing markup. Dates are never synthesized. |
| "Empty output, still charged" | Zero results = zero job charges, plus a status record explaining what happened. |
| "No company name / no job type / no apply URL" | Cards always include company + link; the details mode adds employment type, seniority, function, industries, applicant count, and the external apply URL when public. |
| "Missing most results" | LinkedIn itself caps any public search at **~1,000 results**. We say so up front and tell you the workaround (slice by date range or location) instead of silently truncating. |

### How to use it

1. Enter **keywords** and a **location** (or a numeric LinkedIn `geoId` for precision) — or paste complete **LinkedIn search URLs**, whose keywords, location, and filters are honored exactly.
2. Pick filters: date posted, on-site/remote/hybrid, job type, experience level.
3. Optionally enable **full job details** and the **strict title filter**.
4. Set **max jobs** — an exact cap, so cost is bounded before you start.

### Output example

```json
{
  "type": "job",
  "jobId": "4425881907",
  "title": "Data Engineer",
  "company": "MegazoneCloud US",
  "companyUrl": "https://www.linkedin.com/company/megazonecloud-us",
  "location": "Rochester, NY",
  "postedAt": "2026-06-09",
  "postedText": "2 months ago",
  "salary": null,
  "url": "https://www.linkedin.com/jobs/view/data-engineer-at-megazonecloud-us-4425881907",
  "detail": {
    "seniorityLevel": "Not Applicable",
    "employmentType": "Full-time",
    "jobFunction": "Information Technology",
    "industries": "Technology, Information and Internet",
    "applicantsText": "Over 200 applicants",
    "externalApplyUrl": null,
    "descriptionHtml": "<p>…</p>",
    "descriptionText": "…"
  }
}
```

### Pricing — what a run actually costs

| Event | Price |
|---|---|
| Actor start | $0.005 |
| Unique job record | $0.002 |
| Full details (only when actually delivered) | +$0.003 per job |

Worked examples: 100 jobs = **$0.205**. 100 jobs with full descriptions = **$0.505**. Duplicates, filtered-out jobs, and empty searches cost **nothing**.

### What this Actor does NOT do

- ❌ No logged-in scraping: no profiles, no recruiter data, no "Easy Apply" internals, no connections — public job listings only.
- ❌ No bypassing LinkedIn's ~1,000-result public search cap — split your search by date range, location, or job type to cover more ground.
- ❌ No guessed data: if LinkedIn doesn't show a salary or an external apply URL, you get `null`, not an estimate.
- ❌ Applicant counts are the public text ("Over 200 applicants"), not exact numbers.

### Reliability

Requests run through rotating residential IPs with automatic retry on a fresh session, validated to a 100%-pass live test suite across the US, India, UK, Germany, and the Netherlands. Job pages occasionally fail even with retries; those jobs are delivered as cards without the detail block — and the detail charge is skipped.

### Fair-use & compliance

This Actor accesses only publicly available job listings — the same pages any logged-out visitor sees — at a polite request rate, and collects no personal data. Job seekers, researchers, and recruiters use this data every day; you are responsible for complying with applicable laws and terms in your jurisdiction and use case.

***

*Something missing? Open an issue on the Actor's Issues tab — the roadmap is complaint-driven.*

### More data tools by Automation Craft

- [ATS Job Scraper](https://apify.com/automation_craft/ats-jobs-scraper) — jobs straight from Greenhouse, Lever, Ashby, Workable & SmartRecruiters career boards, one unified schema.
- [Substack Scraper](https://apify.com/automation_craft/substack-scraper) — posts, Notes, profiles & leaderboards.
- [US Building Permits Scraper](https://apify.com/automation_craft/us-building-permits-scraper) — contractor lead feeds from official city data.

# Actor input Schema

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

What to search for, e.g. `data engineer`. LinkedIn matches broadly; turn on the strict title filter below if you only want jobs whose title contains your words.

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

Free-text location, e.g. `United States`, `Bengaluru, India`, `Berlin`. For precise targeting you can pass a LinkedIn geoId instead.

## `geoId` (type: `string`):

Numeric LinkedIn geo id (from a LinkedIn jobs URL, e.g. `103644278` for the US). Overrides ambiguous location text.

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

Paste complete LinkedIn job-search URLs (`https://www.linkedin.com/jobs/search?keywords=…`). Their keywords, location, geoId, and filters are honored exactly.

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

Time window filter, passed to LinkedIn as-is. Every job also carries the REAL posted date from the listing so you can verify.

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

Filter by on-site / remote / hybrid.

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

Filter by employment type.

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

Filter by seniority.

## `strictTitleFilter` (type: `boolean`):

Keep only jobs whose TITLE contains every word of your keywords. Fixes LinkedIn's broad matching; filtered-out jobs are never charged.

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

Fetch each job's detail page: full description (HTML + text), seniority level, employment type, job function, industries, applicant count, and the external apply URL when the company uses one. One extra request per job.

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

Cap on charged unique job records. Honored exactly. Note: LinkedIn itself caps any public search at ~1,000 results — narrow by date/location to cover more ground.

## Actor input object example

```json
{
  "keywords": "software engineer",
  "location": "United States",
  "maxJobs": 50
}
```

# Actor output Schema

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

No description

# 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": "software engineer",
    "location": "United States",
    "maxJobs": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("automation_craft/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": "software engineer",
    "location": "United States",
    "maxJobs": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("automation_craft/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": "software engineer",
  "location": "United States",
  "maxJobs": 50
}' |
apify call automation_craft/linkedin-jobs-scraper --silent --output-dataset

```

## MCP server setup

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