Datapika / Jobs & hiring
LinkedIn Jobs Scraper
Public jobs by keyword, company and location. Job identifiers, titles, companies, locations and source URLs; salary and direct-apply fields depend on availability and options.
Apify store response · 2026-10-14. Usage counts do not measure output accuracy.
· Build 1.0.9 · 12 rows reviewed. Previewing 5 below.
Swipe the table to inspect more fields →
| title | company | location | is_remote | date_posted |
|---|---|---|---|---|
| Product Manager - Appoint | Modernize | Austin, TX | false | 2026-08-14 |
| Global Product Manager, Hardware | Cricut | South Jordan, UT | false | 2026-08-12 |
| Product Manager | ArcSite | Grand Rapids, MI | false | 2026-08-04 |
| Product Manager | Property Meld | Rapid City, SD | false | 2026-07-16 |
| Product Manager | Standard Bots | New York, NY | false | 2026-07-14 |
Selected public fields from one recorded run. Text may be shortened to 20 words and non-HTTPS links are omitted. Missing values are preserved; this sample does not establish complete source coverage. Downloads contain all reviewed rows and selected fields. CSV text cells are escaped for spreadsheet safety.
Inspect the first JSON record
{
"title": "Product Manager - Appoint",
"company": "Modernize",
"location": "Austin, TX",
"is_remote": false,
"date_posted": "2026-08-14",
"job_url": "https://www.linkedin.com/jobs/view/4453722093",
"site": "linkedin",
"scraped_at": "2026-08-15T19:48:11.746436+00:00"
}02 / Run your own query
From a console, code or agent.
Use Apify's input form, or start a run with your own API token. The small starter input below was checked against build 1.0.11's published input schema on September 9, 2026. Recorded samples can use different inputs or older builds.
curl -X POST \
"https://api.apify.com/v2/acts/openclawai~linkedin-jobs-scraper/runs?maxTotalChargeUsd=1" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"searchTerm":"data engineer","location":"London","maxResults":5}'This starts an asynchronous paid run with a $1 total run cap. Use the returned defaultDatasetId to retrieve results after the run succeeds. Never put your API token in public frontend code.
03 / Field reference
Plan your data model.
Selected documented fields from build 1.0.11, reviewed September 9, 2026. Availability varies by mode and source. Missing and null values stay visible in the recorded samples.
| Field | Type | Meaning |
|---|---|---|
| title | string | Job title as posted on LinkedIn |
| company | string | Hiring company name |
| location | string | City, state and country of the job |
| is_remote | boolean | True when the listing is a remote position |
| date_posted | string | Posting date in ISO 8601 format |
| job_url | string | URL to the LinkedIn job posting |
| site | string | Source job board, always linkedin |
| scraped_at | string | UTC timestamp of when the run scraped this job |
04 / Know before you run
Coverage, without the guesswork.
Not a member-profile, applicant-data or Easy Apply submission API. It is not an official LinkedIn API.
How much does it cost to scrape LinkedIn job listings?
The pricing schedule checked September 9, 2026 lists $0.50 per 1,000 primary job events before September 11, 2026 at 19:10 UTC, and $5 per 1,000 from that time. Start, dataset and platform charges may also apply, including when a search returns no jobs. Confirm the effective pricing on Apify and set a total run spending cap.
Do I need a LinkedIn account or API key to scrape jobs?
No. The scraper reads public job listings the same way a logged-out browser does, so there is no LinkedIn login, cookie, or API key involved. You only need an Apify account, and the actor can be called from the REST API, Python and JavaScript clients, or as an MCP tool for AI agents.