LinkedIn Jobs Scraper

LinkedIn Jobs Scraper: public job postings by keyword, location, URL or ID

Search LinkedIn jobs without an account and get one row per posting: title, company, location, posting date, the canonical job URL and, when you ask for it, the full description, the seniority, the employment type and the applicant count.

The search itself works signed out because a job posting is a public page. What you get by default is the card, the same block of text you see in a results list. The description lives on the job's own page and is only fetched when you switch includeDetails on.

💼 What LinkedIn Jobs Scraper does

Give it job titles and places. Every query is run against every location, so three titles and four cities is twelve searches, and the results are pooled and deduplicated into one dataset. A job that two searches both find is written once and charged once.

Every filter here is LinkedIn's own, applied by LinkedIn before the results come back: date posted, companies, Easy Apply, under 10 applicants and distance. They narrow the search rather than just shrinking the output. Remote, job type, experience level and newest first are missing on purpose. LinkedIn ignores them on a public search, so offering them would only look like filtering.

You can also skip searching. Paste /jobs/view/ URLs or numeric job IDs and they are fetched directly, with their full detail pages, and merged with anything the searches found.

📥 What you give it

{
  "searchQueries": ["software engineer"],
  "locations": ["Toronto, Ontario"],
  "datePosted": "pastWeek",
  "includeDetails": true,
  "maxItems": 200
}

Switch includeDetails on if you want the job text. It is off out of the box, and without it description, seniorityLevel, employmentType and applicants are null on every search row. It costs the same per job either way.

Full descriptions on thousands of jobs is a lot to ask of one run. Split that into batches of a few hundred and you will have a better time of it.

📤 What you get back

A real row from a recent run, from a card-only search, with the logo link cut short:

{
  "ok": true,
  "sourceType": "search",
  "jobId": "4445788134",
  "title": "Software Engineer (C++) - Platform & Emerging Technologies",
  "company": "Autodesk",
  "companyUrl": "https://www.linkedin.com/company/autodesk?trk=public_jobs_jserp-result_job-search-card-subtitle",
  "companyLogo": "https://media.licdn.com/dms/image/v2/D560BAQGrSi2UOCdL5g/company-logo_100_100/...",
  "location": "Toronto, Ontario, Canada",
  "salary": null,
  "postedAt": "2026-09-10",
  "postedText": "3 days ago",
  "workplaceType": null,
  "employmentType": null,
  "seniorityLevel": null,
  "jobFunction": [],
  "industries": [],
  "applicants": null,
  "description": null,
  "descriptionHtml": null,
  "url": "https://www.linkedin.com/jobs/view/4445788134",
  "searchQuery": "software engineer",
  "searchLocation": "Toronto, Ontario, Canada",
  "detailFetched": false
}

That is what a row looks like with includeDetails off. Everything below postedText fills in when it is on.

🧾 Reading the output

Three kinds of row, and only real jobs cost anything.

There is no charged field on these rows. sourceType is what separates a real job from a sample or a diagnostic.

One ordering quirk worth knowing: diagnostics are written as they happen, while job rows are written at the end of the run. So in dataset order the problems come first, and a run you abort half way through leaves you with the diagnostics and no jobs.

A diagnostic row carries an errorCode:

▶️ How to run it

1. Open LinkedIn Jobs Scraper and click Try for free. 2. Put job titles in Search queries and places in Locations. 3. Set Date posted and any other filter you want LinkedIn to apply. 4. Turn on Fetch full job details if you need the description, then set Maximum jobs. 5. Click Start, then download the dataset as JSON, CSV or Excel, or read it from the API.

💰 How much does it cost?

$0.80 per 1,000 jobs. Flat on every Apify plan, no volume tiers.

One charge per unique job row. A posting that several of your searches all find is written once and billed once. Sample rows and diagnostic rows are never charged, and a search that finds nothing costs you nothing for results. Fetching the full descriptions does not change the price.

💡 What people use it for

• Watching a set of titles in a set of cities on a schedule, and diffing the new ids against

yesterday's.

• Spotting which companies are hiring into a function right now, as a buying signal.
• Pulling descriptions for a market to see how a role is actually scoped and worded.
• Checking whether a specific posting is still live, by feeding its id back in.

🚧 What it does not do

• No applicant lists, no recruiter names, no contact details. None of that is on a public job

page.

• No salary for most postings. The field is there and it carries whatever the card says, which

is usually nothing. LinkedIn does not publish a salary unless the poster did.

• No applying for you, and no saved jobs. It can find Easy Apply jobs, but it only reads.
• **No remote, hybrid or on-site filter, no job type or experience level filter, and no newest

first.** LinkedIn ignores all four on a public search and sends back the same jobs, so a search that sets one stops with a message and nothing is charged.

• Location is text. It goes to LinkedIn as typed. Set distance to say how far around it to

look; otherwise LinkedIn decides what counts as nearby.

• No industry filter. LinkedIn's public job search accepts one and quietly ignores it, so it

would only look like filtering. With includeDetails on, every row lists the job's industries, so you can filter on those yourself.

• A search stops at the pages you allowed. A wide query will always have more behind it than

one run returns.

• No jobs that were never public, and none that have already been taken down.

🧭 Which job scraper do you need?

❓ Questions people ask

Do I need a LinkedIn account? No, and there is no cookie field. Job pages are public.

Why is the description empty? Because includeDetails was off. Check detailFetched on the row: false means that job's own page was never opened.

Why did I get fewer jobs than I asked for? Either the search genuinely has fewer, or maxPagesPerSearch stopped it. Widen the query, raise the page limit, or add locations.

Can I filter by salary? No. Too few postings publish one for that to be a useful filter.

How fresh is postedAt? It is the posting's own timestamp, so it is as accurate as what the employer set. Use datePosted if you only want recent ones.

Is scraping LinkedIn jobs legal? These are public pages LinkedIn publishes for search engines. Apify's write-up on scraping and the law is a reasonable starting point, and we are not lawyers.

🆘 If something breaks

Open the Issues tab on the actor page. Send the run ID and the exact query and location. The errorCode and searchQuery on the diagnostic row usually point straight at it.