# LinkedIn Jobs Scraper (Public Guest Search, No Login) (`mibedk/linkedin-jobs-public-search`) Actor

Scrapes LinkedIn job postings (title, company, location, description, posted date, apply link) from LinkedIn's public guest job-search pages. No login, no cookies, no account-ban risk — only data LinkedIn already serves to logged-out visitors.

- **URL**: https://apify.com/mibedk/linkedin-jobs-public-search.md
- **Developed by:** [Mikkel Bech-Hansen](https://apify.com/mibedk) (community)
- **Categories:** Jobs, Social media
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.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/platform/actors/running/actors-in-store#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 (Public Guest Search, No Login)

Searches LinkedIn job postings and returns title, company, location, full description,
posted date, and the apply link — using only the pages LinkedIn already serves to
logged-out visitors. There is no login field, no cookie input, and no session state
anywhere in this actor: it calls LinkedIn's public guest job-search endpoint
(`linkedin.com/jobs-guest/jobs/api/seeMoreJobPostings/search`), the same one LinkedIn's
own logged-out job search page uses. That means no account-ban risk and nothing to
configure before your first run — but it also means it can't return anything LinkedIn
hides from logged-out visitors (see Known limitations).

### Input

| Field | Type | Default | Notes |
|---|---|---|---|
| `keywords` | string | `"software engineer"` | Job title, skill, or company. Leave blank to browse all listings for the location. |
| `location` | string | `"United States"` | City, state, country, or region. Leave blank to search worldwide. |
| `datePosted` | enum | `"any"` | `any`, `past24Hours`, `pastWeek`, `pastMonth`, `past6Months`, `past12Months`. The 6/12-month windows aren't exposed in LinkedIn's own UI but work on the guest endpoint - verified against live results. |
| `workplaceType` | enum | `"any"` | `any`, `onSite`, `remote`, `hybrid`. |
| `maxItems` | integer | `50` | Stop after this many job listings (1-2000). Each listing is one billable unit. |
| `fetchFullDescription` | boolean | `true` | Visit each job's detail page for the full description, seniority level, employment type, job function, industries, and salary (when listed). Off = search-result fields only (title, company, location, posted date, apply link) — fewer requests, same price per listing. |
| `proxyConfiguration` | object | no proxy | The guest endpoint works without a proxy at the throttled request rate this actor uses by default. Turn on Apify Proxy if you plan to run many searches back to back. |

### Output

One dataset record per job listing:

```json
{
  "jobId": "4446240091",
  "title": "Software Engineer",
  "companyName": "Aroghia Group, LLC",
  "companyUrl": "https://www.linkedin.com/company/aroghia-group-llc",
  "location": "Beaverton, OR",
  "postedAt": "2026-08-03",
  "postedAgo": "1 week ago",
  "applyUrl": "https://www.linkedin.com/jobs/view/software-engineer-at-aroghia-group-llc-4446240091",
  "companyLogoUrl": "https://media.licdn.com/dms/image/v2/.../aroghia_group_llc_logo?...",
  "description": "2+ years software engineering experience (level dependent).\nStrong proficiency in Python, TypeScript or React...",
  "seniorityLevel": "Associate",
  "employmentType": "Contract",
  "jobFunction": "Information Technology",
  "industries": "IT Services and IT Consulting",
  "salary": null,
  "applicantCount": "Over 200 applicants",
  "searchKeywords": "software engineer",
  "searchLocation": "United States"
}
```

`description`, `seniorityLevel`, `employmentType`, `jobFunction`, `industries`,
`salary`, and `applicantCount` are `null` when `fetchFullDescription` is off, or when
the poster didn't provide that field (`salary` in particular is only present on a
minority of listings — LinkedIn doesn't require it).

### Cost guidance

Pay-per-event: **$0.005 per job listing delivered** (see `MONETIZATION.md`). A typical
run of 50 listings (the default `maxItems`) costs about **$0.25**. A 1,000-listing run
costs about **$5.00**. There is no charge for searches that match nothing.

### How it works

`keywords` + `location` are sent to LinkedIn's guest search endpoint, which returns an
HTML fragment of job cards (no JSON API, no auth). The actor paginates through result
pages, and — when `fetchFullDescription` is on — follows each card's own guest-accessible
detail page for the full description and criteria. Requests are deliberately throttled
to one at a time with a 2-second delay between requests to the same domain, which is
what keeps the default (no-proxy) configuration reliable — verified directly: an
earlier, un-throttled version of this actor hit LinkedIn's rate limit (HTTP 429) within
the first ~15 requests, while the throttled version completed 55/55 requests
successfully in testing. This makes runs slower (roughly one job listing every 1-2
seconds with `fetchFullDescription` on) but keeps them working without a proxy.

### Known limitations

- **No cookie-gated data, by design.** This actor never asks for or uses a LinkedIn
  session. It cannot return applicant lists, recruiter contact details, "people you may
  know," or any other field LinkedIn only shows to logged-in users. If you need those,
  you need a different (cookie-based) actor and accept the account-risk tradeoff that
  comes with it — this actor exists specifically so you don't have to.
- **Pagination is capped.** LinkedIn's guest endpoint itself stops returning results
  past a certain offset (observed around `start=1000-2000` depending on the query,
  returning HTTP 400) regardless of how many listings actually exist. In practice this
  means very broad searches (e.g. blank keywords in a huge market) won't surface every
  listing on LinkedIn, only the first page or so of them.
- **Low-signal queries can return loosely-related "filler" listings.** When a search
  matches very few or no real postings, LinkedIn's guest search sometimes fills the
  page with generic/unrelated listings rather than an empty result — this is LinkedIn's
  own behavior, not a bug in this actor. It's more common with obscure keyword/location
  combinations than with normal job searches.
- **No proxy is required by default, but heavy use may still get rate-limited.**
  Testing showed the default throttling (1 request at a time, 2s apart) runs cleanly
  for at least ~50-100 requests in a row. If you run this actor very frequently or in
  parallel, enable Apify Proxy in the `proxyConfiguration` input to reduce the chance of
  temporary blocks.
- **Undocumented endpoint.** `jobs-guest/jobs/api/seeMoreJobPostings/search` is
  LinkedIn's own internal endpoint, not a published API — its response shape or
  availability could change without notice.
- **Salary is rarely present.** Most listings don't include one; `salary` is `null` far
  more often than not (16 of 50 in one representative test run).

### Legal

This Actor is an independent, third-party tool. It is not affiliated with,
endorsed by, or sponsored by LinkedIn Corporation.

It retrieves data from LinkedIn's public, logged-out guest job-search pages,
never from a login-gated surface and never using a session cookie. Despite
that, LinkedIn's User Agreement (Section 8.2) restricts automated data
collection from the site regardless of whether the page requires login, and
LinkedIn has pursued this in practice - a well-known public-data-only LinkedIn
scraping API (Proxycurl) shut down in 2025 citing the cost of LinkedIn/
Microsoft's legal pressure. Using this Actor may not comply with LinkedIn's
terms. You are responsible for reviewing LinkedIn's terms and applicable law
before using this Actor, and for how you use the data it returns.

# Actor input Schema

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

Job title, skill, or company to search for. Leave blank to browse all currently listed jobs for the location.

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

City, state, country, or region to search in. Leave blank to search worldwide.

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

Only return jobs posted within this window.

## `workplaceType` (type: `string`):

Filter by on-site, remote, or hybrid.

## `maxItems` (type: `integer`):

Stop after collecting this many job listings. Each listing is one billable unit.

## `fetchFullDescription` (type: `boolean`):

Visit each job's detail page for the full description, seniority level, employment type, job function, industries, and salary (when listed). Turning this off returns only search-result fields (title, company, location, posted date, apply link) and runs faster/cheaper on requests, though billing is per listing either way.

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

Optional. The public guest endpoint works without a proxy at moderate volume. Enable Apify Proxy if you plan to scrape a large number of listings and want to reduce the chance of temporary rate-limiting.

## Actor input object example

```json
{
  "keywords": "software engineer",
  "location": "United States",
  "datePosted": "any",
  "workplaceType": "any",
  "maxItems": 50,
  "fetchFullDescription": true,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `jobListings` (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"
};

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

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

```

## MCP server setup

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

```

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/mtDVaUQKG2enUB5lW/builds/7wEBps8C9OS6dR9qY/openapi.json