# LinkedIn Jobs API

LinkedIn Jobs API searches LinkedIn's logged-out public job pages and returns one row per unique job: jobId, jobUrl, title, companyName, companyUrl, location, postedAt, postedText, salaryText when shown, isPromoted and benefits. With includeDetails on it adds descriptionText, seniorityLevel, employmentType, industries, applicantsText and applyType. It costs $0.0005 per job ($0.50 per 1,000) plus $0.0012 per job with details, and needs no login or cookies.

## Key facts

- Price: from $0.0005 per job listing, $0.5 per 1,000, down to $0.00025 on higher Apify plans
- Pricing model: Pay per event
- Output: JSON, CSV, Excel, XML, RSS via Apify datasets
- Access: Apify Console, REST API, Python and JS clients, MCP tool linkedin_jobs
- Version: Updated Nov 2026, build 0.1.5
- Usage: 96.4% successful runs (30 days)
- Actor: subimpact/linkedin-jobs-api

## Who it is for

- Recruiters and talent teams tracking competitor job openings
- Job boards and aggregators needing first-party listing data
- Analysts measuring hiring demand by role and city
- Sales teams watching account hiring signals

## Use cases

### Build a market job list

Set searches to a keyword and location pair such as data engineer in Malaysia, and maxTotalJobs to the number of rows you will pay for. Each row carries title, companyName, location, postedAt and postedText, plus the search that produced it in searchKeywords and searchLocation. The same job found by two searches is delivered once, keyed on jobId.

### Apply LinkedIn's own filters

Set postedWithin to 24h, week or month, workplaceType to remote, hybrid or onsite, jobType to full-time, contract or internship, and experienceLevel to mid-senior or entry. These are sent as LinkedIn's own parameters, so the result set is what a person sees after clicking the same filter. sortByDate gives newest first.

### Read the full posting

Turn on includeDetails and each row gains descriptionText and descriptionHtml plus seniorityLevel, employmentType, jobFunction, industries and applicantsText. That is what you need to classify a role by skill or to judge how competitive a posting is. Details cost one extra request per job, fetched detailConcurrency at a time, six by default.

### Track hiring on target accounts

Run a keyword search per role and follow companyName across weeks, storing jobId so a reposted role is not counted twice. postedAt and postedText give the age, and isPromoted marks cards LinkedIn boosted, which keeps an ad from reading as organic demand. benefits badges such as Actively Hiring add a second signal on urgency.

### Reuse a filtered search URL

Copy a LinkedIn jobs search URL from your browser into searchUrls, filters and all, and the keywords, location and the f_TPR, f_WT, f_JT, f_E and sortBy parameters are read from it. A filter in a pasted URL wins over the run-level filter of the same name, so a saved search reproduces exactly what you set up on the site.

## Price events

- Job listing (`job`): $0.0005, lowest tier $0.00025. One unique job listing row delivered to the dataset (job id, title, company, location, posting date, search context). Platform usage included.
- Job details (`job-details`): $0.0012, lowest tier $0.0007. Extra charge per job row delivered with its public detail fields: full description, seniority, employment type, job function, industries and applicant count. Platform usage included.

Prices from the Apify Store. Apify shows the final price before each run.

## How it compares with other Apify actors

Price per 1,000 jobs at Apify Store list prices, checked 20 Nov 2026.

| Actor | Price per 1,000 jobs (Free plan) | Higher plans (Gold) | Start fee per run | Platform usage | Users | Rating | Last build |
| --- | --- | --- | --- | --- | --- | --- | --- |
| LinkedIn Jobs Scraper: Public Job Listings, No Login (this API) | $0.5 | $0.25 | None | Included | 2 | No reviews yet | 18 Nov 2026 |
| [Linkedin Jobs Scraper](https://apify.com/curious_coder/linkedin-jobs-scraper) | $2.00 | $1.00 | $0.00005 | Included | 183,156 | 4.5 (144 reviews) | 7 Nov 2026 |
| [🏆 LinkedIn Jobs Scraper](https://apify.com/valig/linkedin-jobs-scraper) | $0.4 | $0.28 | $0.001 | Included | 43,459 | 4.7 (27 reviews) | 18 Nov 2026 |
| [🔥 LinkedIn Jobs Scraper](https://apify.com/bebity/linkedin-jobs-scraper) | $1.50 | $1.00 | $0.00005 | Included | 49,853 | 4.5 (74 reviews) | 6 Nov 2026 |
| [LinkedIn Jobs Scraper | Remove Duplicate Jobs | Pay Per Result](https://apify.com/cheap_scraper/linkedin-job-scraper) | $0.7 | $0.35 | $0.005 | Included | 58,136 | 4.4 (42 reviews) | 12 Nov 2026 |
| [Linkedin Jobs Scraper](https://apify.com/worldunboxer/rapid-linkedin-scraper) | $0.1 | $0.1 | $0.00005 | Included | 16,342 | 4.2 (31 reviews) | 19 Nov 2026 |

### Where Linkedin Jobs Scraper is stronger

- Far larger user base and a long review history on the Apify Store
- Accepts LinkedIn search URLs as well as keyword and geo filters
- Filters include posting date and an under ten applicants option

### Where this API is stronger

- Detail fields are charged per row only when they are switched on
- Output includes ATS platform and apply type for each listing
- No Actor start fee on top of the per job price

Full comparison: Linkedin Jobs Scraper vs this API: https://subimpact.net/apis/alternatives/curious-coder-linkedin-jobs-scraper/

### Where 🏆 LinkedIn Jobs Scraper is stronger

- Very large user base with many runs each month
- Filters cover easy apply, company and applicant count

### Where this API is stronger

- Optional detail fields add seniority, employment type and industries per job
- Output includes salary text and benefits fields
- No separate start fee on top of the per job price

### Where 🔥 LinkedIn Jobs Scraper is stronger

- Can add company and hiring contact insights to each job
- Output includes recruiter name and profile URL
- Very large user base and more recent runs than ours

### Where this API is stronger

- Company website and hiring contact data are not separate add-ons here
- Output includes ATS platform and apply type for each job
- One detail event covers description, seniority, function and applicant count

### Where LinkedIn Jobs Scraper | Remove Duplicate Jobs | Pay Per Result is stronger

- Removes duplicate jobs across searches and can filter with AI questions
- Can attach company details to each job row
- Very large user base with frequent runs on the Apify Store

### Where this API is stronger

- Output includes ATS platform, apply type and posted text fields
- The detail event applies only when details are enabled
- No Actor start fee in the listing

### Where Linkedin Jobs Scraper is stronger

- Advertises a very low per job price with optional company enrichment
- Returns hiring badge and early applicant flags
- Accepts keywords, search URLs and locations as starting points

### Where this API is stronger

- Output includes seniority level, job function and industries per row
- Detail fields are charged per row only when enabled
- No separate Actor start fee on top of the per job price

Every actor here returns public LinkedIn job rows with similar core fields, so filters, enrichment and price shape decide the choice. The larger actors offer AI filtering, recruiter data and duplicate removal for broad research. Buyers who mainly need clean listing rows with optional detail fields and no start fee will find this actor a straightforward fit.

Prices are Apify Store list prices, checked 20 Nov 2026. Platform usage 'Paid separately' means Apify bills compute on top of the event price. Check each listing before you buy.

## Input

- `searches` (array, optional): Keyword and location pairs. Each pair is one LinkedIn job search. Example: [{"keywords":"data engineer","location":"Malaysia"}]. Use either this or searchUrls. With neither, the prefilled demo search runs and nothing else.
- `searchUrls` (array, optional): LinkedIn jobs search URLs copied from your browser, for example https://www.linkedin.com/jobs/search/?keywords=data%20engineer&location=Malaysia&f_WT=2. keywords, location and the f_TPR, f_WT, f_JT, f_E, sortBy and geoId filters are read...
- `maxJobsPerSearch` (integer, optional): Cap on delivered jobs per search (1 to 1000). LinkedIn's guest endpoint stops returning cards around start=990, so a search yields at most about 1,000 jobs.
- `maxTotalJobs` (integer, optional): Global cap across every search in one run. This is the hard cost ceiling. Set 0 for no limit.
- `includeDetails` (boolean, optional): Fetch each job's public detail page for the full description, seniority level, employment type, job function, industries, applicant count and the apply type. Adds one request and one extra charge per job.
- `detailConcurrency` (integer, optional): How many detail pages to fetch in parallel when includeDetails is on. Rows are still delivered and charged one at a time, in listing order. Higher is faster, lower is gentler on LinkedIn.
- `postedWithin` (string, optional): Keep jobs posted in the last 24 hours, week or month. LinkedIn applies this as the f_TPR filter.
- `workplaceType` (array, optional): On-site, remote or hybrid. Leave empty for all.
- `jobType` (array, optional): Full-time, part-time, contract, temporary or internship. Leave empty for all.
- `experienceLevel` (array, optional): Internship through executive. Leave empty for all.
- `sortByDate` (boolean, optional): Ask LinkedIn to sort by posting date instead of relevance.
- `proxyCountry` (string, optional): Two-letter country for the residential proxy session, for example US or MY. LinkedIn throttles datacenter IPs, so the Actor always runs through Apify residential proxy.

### Example input

```json
{
  "searches": [
    {
      "keywords": "data engineer",
      "location": "Malaysia"
    }
  ],
  "maxJobsPerSearch": 20,
  "maxTotalJobs": 50
}
```

## Output fields

- `jobId` (string/null): LinkedIn posting id (numeric string). Null on error rows.
- `jobUrl` (string/null): Public LinkedIn job view URL, https://www.linkedin.com/jobs/view/<id>.
- `title` (string/null): Job title as shown on the public posting.
- `companyName` (string/null): Hiring company name.
- `companyUrl` (string/null): LinkedIn company page link when the card shows one.
- `location` (string/null): Location text as published by the employer.
- `postedAt` (string/null): Posting date from the card's time datetime attribute (YYYY-MM-DD).
- `postedText` (string/null): Relative posting age exactly as LinkedIn shows it, for example 3 days ago.
- `salaryText` (string/null): Salary text when LinkedIn shows one on the card.
- `isPromoted` (boolean): True when the card is marked as promoted.
- `benefits` (array/null): Badge texts on the card, for example Actively Hiring.
- `searchKeywords` (string/null): Keywords of the search that produced the row.
- `searchLocation` (string/null): Location of the search that produced the row.
- `scrapedAt` (string): ISO timestamp of when the search page was fetched.
- `error` (string/null): Why this row is an error row, null on job rows. Error rows are never charged.
- `inputValue` (string/null): The raw search entry that could not be read, on error rows only.
- `descriptionText` (string/null): Full plain-text job description. Requires includeDetails.
- `descriptionHtml` (string/null): Full HTML job description. Requires includeDetails.
- `seniorityLevel` (string/null): LinkedIn job criteria: seniority level.
- `employmentType` (string/null): LinkedIn job criteria: employment type.
- `jobFunction` (string/null): LinkedIn job criteria: job function.
- `industries` (string/null): LinkedIn job criteria: industries.
- `applicantsText` (string/null): Applicant caption as shown, for example 60 applicants or Over 200 applicants.
- `applyUrl` (string/null): Filled only when LinkedIn shows the external apply link to logged-out visitors (rare); null otherwise. applyType still tells offsite from Easy Apply.
- `applyType` (string/null): offsite, easy_apply or unknown. Set on every detail page; the reliable signal for how a posting is applied to.
- `atsPlatform` (string/null): Filled only when applyUrl is visible and points at a known hiring platform: greenhouse, lever, ashby, workday, smartrecruiters, personio or ukg. Null when LinkedIn hides the external apply link (the common case).

## Sample output

Trimmed from one of our own test runs. Personal data is redacted.

```json
[
  {
    "jobId": "4483152382",
    "jobUrl": "https://www.linkedin.com/jobs/view/4483152382",
    "title": "Software Engineer III - Java, Database, AWS",
    "companyName": "JPMorganChase",
    "companyUrl": "https://www.linkedin.com/company/jpmorganchase",
    "location": "Singapore, Singapore",
    "postedAt": "2026-11-14",
    "postedText": "5 days ago",
    "salaryText": null,
    "isPromoted": false,
    "benefits": [
      "Actively Hiring"
    ],
    "searchKeywords": "software engineer",
    "searchLocation": "Singapore",
    "scrapedAt": "2026-11-20T02:49:06.287Z",
    "error": null,
    "inputValue": null,
    "descriptionText": "Job Description\nWe have an exciting and rewarding opportunity for you to take your software engineering career to the next level.\nAs a Software Engineer III at JPMorganChase within the Commercial & Investment Bank's Payments Technology g...",
    "seniorityLevel": "Not Applicable",
    "employmentType": "Full-time",
    "jobFunction": null,
    "industries": "Financial Services",
    "applicantsText": "162 applicants",
    "applyUrl": null,
    "applyType": "offsite",
    "atsPlatform": null
  },
  {
    "jobId": "4465811104",
    "jobUrl": "https://www.linkedin.com/jobs/view/4465811104",
    "title": "Software Engineer III, Java",
    "companyName": "JPMorganChase",
    "companyUrl": "https://www.linkedin.com/company/jpmorganchase",
    "location": "Singapore, Singapore",
    "postedAt": "2026-11-15",
    "postedText": "4 days ago",
    "salaryText": null,
    "isPromoted": false,
    "benefits": [
      "Actively Hiring"
    ],
    "searchKeywords": "software engineer",
    "searchLocation": "Singapore",
    "scrapedAt": "2026-11-20T02:49:06.287Z",
    "error": null,
    "inputValue": null,
    "descriptionText": "Job Description\nWe have an exciting and rewarding opportunity for you to take your software engineering career to the next level.\nAs a Software Engineer III at JPMorganChase within the Asset Wealth Management, you serve as a seasoned mem...",
    "seniorityLevel": "Not Applicable",
    "employmentType": "Full-time",
    "jobFunction": null,
    "industries": "Financial Services",
    "applicantsText": "Over 200 applicants",
    "applyUrl": null,
    "applyType": "offsite",
    "atsPlatform": null
  }
]
```

## How to run it

1. Add a search object to searches, for example {"keywords": "data engineer", "location": "Malaysia"}, or paste a LinkedIn jobs URL into searchUrls.
2. Set maxJobsPerSearch, 50 by default, and maxTotalJobs, 200 by default, which is the hard cost ceiling for the run.
3. Turn includeDetails on if you need the full description and criteria; leave it off for a cheaper large list.
4. Optional: set postedWithin, workplaceType, jobType, experienceLevel and sortByDate, or let a pasted URL carry them.
5. Start the run in the Apify Console; rows stream in listing order and errors arrive as free rows.
6. Export as JSON, CSV or Excel, and read the OUTPUT record in the key-value store for run counters.

### cURL

```bash
curl -X POST "https://api.apify.com/v2/acts/subimpact~linkedin-jobs-api/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searches":[{"keywords":"data engineer","location":"Malaysia"}],"maxJobsPerSearch":20,"maxTotalJobs":50}'
```

### Python

```python
from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("subimpact/linkedin-jobs-api").call(run_input={
      "searches": [
        {
          "keywords": "data engineer",
          "location": "Malaysia"
        }
      ],
      "maxJobsPerSearch": 20,
      "maxTotalJobs": 50
    })

for item in client.dataset(run["default_dataset_id"]).iterate_items():
    print(item)
```

### JavaScript

```javascript
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('subimpact/linkedin-jobs-api').call({
  "searches": [
    {
      "keywords": "data engineer",
      "location": "Malaysia"
    }
  ],
  "maxJobsPerSearch": 20,
  "maxTotalJobs": 50
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

console.log(items);
```

### MCP

```bash
claude mcp add subimpact-data -e APIFY_TOKEN=<YOUR_APIFY_TOKEN> -- npx -y @subimpact/data-mcp

# Then ask your agent to use the linkedin_jobs tool.
```

### n8n

Use the Apify node (Run an Actor).
Actor ID: subimpact/linkedin-jobs-api
Input JSON: paste the example input below.

## Limits

- Public logged-out pages only: anything a signed-out visitor cannot see is not returned.
- One search yields at most about 1,000 jobs, because LinkedIn stops serving cards around start=990.
- Offsite apply URLs are rarely visible without a session, so applyUrl is often null even when applyType says offsite.
- Details add one request per job, at roughly 63 KB per job against 29 KB per page of ten cards.

## FAQ

### What does a job cost?

$0.0005 per delivered listing, which is $0.50 per 1,000 jobs on the Free plan and $0.25 per 1,000 on Gold and above. Details add $0.0012 per job, or $0.70 per 1,000 on Gold. The job event is charged only after the row is pushed, and error rows are free.

### Do I need a LinkedIn login or cookies?

No, and there is no input for them. The Actor reads LinkedIn's logged-out guest job pages, so it sees exactly what a visitor without an account sees. It does not open profiles or collect people data, and recruiter or poster names are never extracted.

### How many jobs can one search return?

LinkedIn's guest search returns 10 cards per request and stops around start=990, so roughly 1,000 jobs per search is the practical ceiling. maxJobsPerSearch takes 1 to 1000, and adding more searches is how you widen coverage.

### Why are some detail fields empty?

Detail fields are filled from the public job page, and employers do not always publish them: jobFunction is often missing, and salaryText only appears when LinkedIn shows a salary on the card. applyUrl is rarely visible to a logged-out visitor, though applyType is always set.

### Is a proxy included?

Yes. LinkedIn throttles datacenter IPs immediately, so the Actor always runs through the residential proxy included in its price, with a fresh session on every retry, up to four attempts per URL. proxyCountry sets the two-letter country for that session.

### What does the run do with a search that fails?

A failed search becomes one error row explaining why, with the job fields null and no charge, and the rest of the run continues. A search with no results returns no rows and is reported in the run summary alongside the counters.

### Can I see whether a job is Easy Apply or offsite?

applyType is set on every detail page as offsite, easy_apply or unknown, and it is the reliable signal for how an application is submitted. When LinkedIn exposes an external apply link, applyUrl is filled and atsPlatform names the system for known hosts such as Greenhouse, Lever, Ashby, Workday, SmartRecruiters, Personio and UKG.

## Links

- Page: https://subimpact.net/apis/linkedin-jobs-api/
- Category: https://subimpact.net/apis/category/jobs/
- Run on Apify: https://apify.com/subimpact/linkedin-jobs-api
- All data APIs: https://subimpact.net/apis/
- Catalogue JSON: https://subimpact.net/apis/catalogue.json
