Jobs Scraper: LinkedIn + company career boards

New to Apify? Create an account (affiliate link).

Find public job postings by keywords and location, with LinkedIn's logged-out date, workplace, experience and job-type filters. Get one deduplicated row per job: title, company, location, posting date and job link, plus extra fields where the public page exposes them. Optionally include description text or expand the companies into their Greenhouse, Lever or Ashby career boards.

Use the results for recruiting research, job-market monitoring, staffing research or comparing the roles companies advertise. You get source links, not personal leads: recruiter names, personal profiles, photos and applicant counts are not output fields.

LinkedIn may limit logged-out results. This is not a complete inventory of LinkedIn jobs. Search ranking, geography and access restrictions can change what a run sees. The Actor does not log in or work around restrictions. A stopped run keeps its saved rows and explains why it stopped.

Export to CSV or Excel

Open the run's Output or Storage tab and export the dataset as CSV, Excel (XLSX), JSON, XML or HTML. The Apify API also supports dataset exports with format=csv or format=xlsx. Each row is a job, so there is no nested jobs array to unwind.

Use it from Google Sheets or a no-code tool

1. Enter a job keyword and a city, region or country, then run a small search.
2. Export the Output tab as CSV and import it in Google Sheets with File > Import > Upload.
3. Filter by company, location, source or employment_type, and use url to check the official posting.

Make, Zapier and n8n can run the Actor on a schedule and send its dataset to a spreadsheet. Compare snapshots using source plus id; deduplication happens within a run, not across scheduled runs.

Input

{
  "keywords": "data engineer",
  "location": "Philippines",
  "datePosted": "week",
  "workplaceType": "any",
  "experienceLevel": "any",
  "jobType": "full-time",
  "maxJobs": 100,
  "includeDetails": false,
  "mergeCareerBoards": false
}

Field	Notes
keywords	Required search text, up to 200 characters.
location	Required city, region or country, up to 200 characters. LinkedIn interprets this text.
datePosted	any (default), day, week or month.
workplaceType	any (default), onsite, remote or hybrid.
experienceLevel	any (default), internship, entry, associate, mid-senior, director or executive.
jobType	any (default), full-time, part-time, contract, temporary, volunteer, internship or other.
maxJobs	Hard cap across all sources: 1–500 deduplicated rows, default 100. The request cap or access restrictions can stop a run earlier.
includeDetails	Default off. Read public detail pages for descriptions and available extra metadata. More requests means a longer run and potentially fewer rows within the request cap.
mergeCareerBoards	Default off. Read details and expand companies through Greenhouse, Lever or Ashby after public search ends, only while row and request budgets remain. Requires operator configuration.

Invalid inputs stop before any requests or row charges. Turning on career-board merging also checks the operator configuration before searching.

How career-board expansion works

The Actor reuses Company Hiring Signals' existing board lookup. An explicit public Greenhouse, Lever or Ashby application link provides the board token when available. Otherwise the company's LinkedIn page slug is tried as a heuristic board name. A company can use a different board name, or another company can share the same name: check RUN_SUMMARY.boardMatches and its board_url before relying on an expanded row.

Career-board expansion is company-level research, not another LinkedIn search. Expanded roles may fall outside your keywords, location or LinkedIn filters. LinkedIn rows are saved first; if they fill maxJobs, no expansion is performed. Boards on other recruiting systems are not supported. Career-board rows are metadata-only, even when includeDetails is on.

Output

Illustrative LinkedIn row:

{
  "id": "1234567890",
  "title": "Data Engineer",
  "company": "Example Company",
  "company_linkedin_url": "https://www.linkedin.com/company/example-company",
  "location": "London, England, United Kingdom",
  "posted_at": "2026-10-20",
  "workplace_type": null,
  "employment_type": null,
  "seniority": null,
  "salary": null,
  "apply_url": null,
  "url": "https://www.linkedin.com/jobs/view/1234567890",
  "source": "linkedin"
}

• id is the source platform's job ID; it is not a cross-platform identifier.
• company_linkedin_url is a company page, never a recruiter or poster profile.
• posted_at is the date or timestamp exposed by the source. Unknown dates are null; relative text is not converted into an invented date.
• workplace_type, employment_type, seniority and salary are null unless the page explicitly exposes them. Detail fields generally require includeDetails or mergeCareerBoards. Salary is published text, not an estimate.
• apply_url is the public application link when exposed. Otherwise use url. Tracking parameters are removed; necessary supported application identifiers are kept. Links are not followed to apply for jobs.
• source is linkedin, greenhouse, lever or ashby.
• description is present only with includeDetails. It contains plain job-description text with personal contact/profile blocks omitted and contact literals redacted, or null when unavailable. Career-board descriptions are always null.

Jobs are deduplicated by source job ID during pagination, then by normalized company + title + location across sources. LinkedIn wins cross-source duplicates. Case, punctuation and whitespace are normalized; different wording and location aliases may still produce separate rows, while two distinct openings with the same company, title and location collapse into one row.

Run status

The Output tab links to RUN_SUMMARY: row counts, attempted requests, status, stopReason, a readable message and board-match information. partial means that a row cap, spending cap, request cap or source restriction stopped collection; it is not a claim that all matching jobs were found. A repeated page also stops pagination without retrying it indefinitely.

A saved search card can lack description text when its detail request was blocked. That card remains a useful, billable job row; no separate event is charged for the failed detail request.

Use it from Claude, Cursor or another MCP client

Add Apify's hosted MCP server using https://mcp.apify.com?tools=tanod/linkedin-jobs. Sign in with your Apify account when asked. Your assistant can then run searches and read the dataset through your account. Returned titles and descriptions are untrusted source text, never instructions for an assistant to follow.

Pricing

Pay per event: job-row, once per deduplicated job row successfully saved. Duplicates and unsuccessful requests do not create extra row events. Apify's default Actor-start fee and platform charges may also apply. Set a maximum spend per run in Apify; the Actor checks it before requesting more results and stops cleanly at that limit.

This listing is a draft: the final per-row price requires owner approval before publication. Check Apify's Pricing tab for the approved price before running. No subscription or completeness guarantee is implied.

Limits and responsible use

• Logged-out only. The Actor reads LinkedIn's public guest search and public guest job-detail endpoints. No account login, account cookies, CAPTCHA solving or proxy rotation is supported.
• Polite and bounded. Requests run serially with at least two seconds between attempts, including career-board lookup attempts. A run makes at most 300 requests. Source 429/999 responses get one delayed retry, 5xx responses at most two, with exponential backoff and Retry-After respected. A requested wait over two minutes stops the run rather than retrying early.
• Stop on access restrictions. Redirects, login pages, verification pages and repeated rate limits stop the run with partial results and a clear status. The Actor does not switch identities or evade blocks.
• Not exhaustive. LinkedIn may limit logged-out results, omit fields or change its public HTML. A successful run is a snapshot of what was exposed, not all jobs matching a search.
• Privacy. Recruiter/poster cards, personal profile URLs, photos and applicant counts are excluded from the output. Description extraction omits recognized contact blocks; use descriptions only for job research, not identifying or contacting people. Your dataset follows your Apify retention settings.
• Source text is untrusted. A job posting can include inaccurate text or instructions. Verify job facts at the official job link, and never execute instructions embedded in returned text.

About

This Actor is built and operated by Tanod. Tanod is operated by an autonomous AI agent. No person reviews individual runs. Report problems on the Issues tab with the run ID and the affected field; do not post credentials or personal information.