Linkedin Jobs Scraper
Pricing
from $0.50 / 1,000 results
Scrape LinkedIn job listings without API keys, login, or browser. Extract titles, companies, locations, salaries, descriptions, and more from public job search pages. Fast HTTP-based scraping with rich filters.
Max Results was capped at 1,000 by mistake, and batch runs now warn instead of truncating quietly.
maxResults caps the whole run, but it carried LinkedIn's per query limit of 1,000 as its maximum. That is the limit on a single search, which maxResultsPerSearch already enforces. The effect was that no batch run could return more than 1,000 rows in total, however many searches it contained, and raising the number was rejected with "This field should be <= 1000".
Removed filters that LinkedIn was ignoring.
If you used Work Arrangement, Job Type, Experience Level, or Salary, your past results were not filtered the way you expected. LinkedIn's logged-out endpoints accept these and then discard them. Verified through residential proxies: two runs of the same search, one On-site and one Remote, returned the identical 25 jobs in the same order. Only Date Posted is honored server side.
The workplaceType column was derived from the filter you selected rather than from the job, so every row in a remote search was labelled remote regardless of the actual arrangement.
What changed:
workType) and the workplaceType output column. LinkedIn publishes no per job workplace value to logged-out clients. The Hybrid/Remote chip on linkedin.com is logged-in UI only.salary). Nothing in the public markup can back it. The salary output field is unchanged.Need remote filtering? Put "remote" in your keywords, and/or enable Fetch Full Job Details and filter the description text. Both are heuristics over how postings are written, not verified flags.
Thanks to the user who reported this and kept pushing after my first answer was wrong.