# LinkedIn Jobs Scraper alternative: subimpact LinkedIn Jobs API

Both actors turn a LinkedIn jobs search into one row per job with title, company, location and posting date. curious_coder/linkedin-jobs-scraper lists $2.00 per 1,000 results on the Free plan and $1.00 per 1,000 on Gold, plus a start fee. Ours lists $0.50 per 1,000 jobs on Free and $0.25 per 1,000 on Gold, with platform usage included and detail fields charged only when switched on. Theirs accepts search URLs with the full LinkedIn filter set. Both run on the Apify Store.

## Key facts

| Fact | Linkedin Jobs Scraper | This API (LinkedIn Jobs Scraper: Public Job Listings, No Login) |
| --- | --- | --- |
| Price per 1,000 jobs (Free plan) | $2.00 | $0.5 |
| Higher plans (Gold) | $1.00 | $0.25 |
| Start fee per run | $0.00005 | None |
| Platform usage | Included | Included |
| Users on the Apify Store | 183,156 | 2 |
| Rating | 4.5 (144 reviews) | No reviews yet |
| Last build | 7 Nov 2026 | 18 Nov 2026 |
| Pricing model | Pay per event | Pay per event |

Store prices checked 20 Nov 2026. Platform usage 'Paid separately' means Apify bills compute on top of the event price.

## Head-to-head test

20 'data engineer' jobs in Malaysia

| Measure | Linkedin Jobs Scraper | This API |
| --- | --- | --- |
| Status | SUCCEEDED | SUCCEEDED |
| Items returned | 20 | 20 |
| Run time (seconds) | 13.9 | 4.7 |
| Average filled fields per item | 19.4 | 12.8 |
| Distinct fields | 25 | 26 |
| List price of the job | $0.04005 | $0.01 |
| Measured platform usage | $0.02405 included in the price | $0.00013 included in the price |

One run each on 20 Nov 2026, same input, default memory. Small samples; your results will vary with input.

## When to choose this API

- You want a lower per job event price for listing rows alone.
- You want detail fields such as the full description charged only when enabled.
- You want applyType and atsPlatform on every listing that carries a detail page.
- You want no start fee before the first job row is delivered.

## When to choose Linkedin Jobs Scraper

- You rely on LinkedIn search URLs with geo ids and company filters.
- You want an under ten applicants filter applied by the actor.
- You need company detail scraping in the same run as the job rows.
- You value their long review history when choosing a dependency.

## Switching from Linkedin Jobs Scraper

| Their input field | Our input field | Note |
| --- | --- | --- |
| `urls` | `searchUrls` | Search URLs copied from a browser go into searchUrls; keywords, location and the f_TPR, f_WT, f_JT, f_E, sortBy and geoId values are read from the URL. |
| `keywords` | `searches` | Same meaning, paired with a location inside searches rather than standing alone. |
| `location` | `searches` | Paired with keywords inside searches, which is one search per keyword and location pair. |
| `limitPerSource` | `maxJobsPerSearch` | Same per search cap under a different name, plus maxTotalJobs as a run wide ceiling. |
| `datePosted` | `postedWithin` | Maps to postedWithin with any, 24h, week or month. |
| `companyIds` | `(none)` | No company id filter; run one search per employer and filter on companyName. |
| `under10Applicants` | `(none)` | No applicant count filter, though applicantsText is returned when details are on. |
| `splitByLocation` | `(none)` | No city splitting input; one entry per location in searches does the same job. |
| `scrapeCompany` | `(none)` | No company profile scraping; rows carry companyName and companyUrl only. |

### Example input

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

Actor id: subimpact/linkedin-jobs-api. Run it at https://apify.com/subimpact/linkedin-jobs-api

## Where each one is stronger

### 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

## FAQ

### How do the prices compare per 1,000 jobs?

curious_coder lists $2.00 per 1,000 results on the Free plan and $1.00 per 1,000 on Gold, plus a $0.00005 start fee. Ours lists $0.50 per 1,000 jobs on Free and $0.25 per 1,000 on Gold, with platform usage included and no start fee. Detail fields add $0.0012 per job, which is $0.70 per 1,000 on Gold.

### Can I reuse my LinkedIn search URLs?

Yes. Paste them into searchUrls and the actor reads keywords, location and the f_TPR, f_WT, f_JT, f_E, sortBy and geoId values from the URL itself. If you prefer explicit inputs, put keyword and location pairs in searches instead.

### Does my existing pipeline read the same field names?

Not exactly. Our rows use jobId, jobUrl, title, companyName, location, postedAt, salaryText and searchKeywords, and add descriptionText, seniorityLevel, employmentType and applicantsText when details are on. Map the fields you read before switching, because the two schemas differ even though the underlying listings are the same public pages.

### 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 what a visitor without an account sees. It does not open personal profiles or collect people data, and recruiter names are never extracted.

### How many jobs can one search return?

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

### Why are some detail fields empty?

Detail fields come 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 when details are on.

### Is a proxy included in the price?

Yes. LinkedIn throttles datacenter addresses, so the actor runs through the residential proxy included in its per job price, and proxyCountry sets the two letter country for that session. Detail pages are fetched with a configurable concurrency so you can stay gentle on the site.

## Links

- Page: https://subimpact.net/apis/alternatives/curious-coder-linkedin-jobs-scraper/
- Our API page: https://subimpact.net/apis/linkedin-jobs-api/
- Competitor: https://apify.com/curious_coder/linkedin-jobs-scraper
- Run ours on Apify: https://apify.com/subimpact/linkedin-jobs-api
- All comparisons: https://subimpact.net/apis/alternatives/
