LinkedIn Jobs Scraper

This scraper collects only job postings that LinkedIn shows publicly to visitors who are not logged in. Some fields, such as the job poster's name, are personal data, which laws such as the GDPR and CCPA protect. Make sure you have a lawful reason to collect and use it. If you are unsure, ask a lawyer.

No. You don't need a LinkedIn account, a login or cookies, and the scraper never uses yours.

LinkedIn shows at most 1,000 jobs per search, logged in or not. To get more, split the search: one search per city instead of one per country, or one per keyword. Each search URL or keyword in the input is its own search, and a job found by two searches is saved once.

Date posted, Easy Apply, Fewer than 10 applicants, company and location filters work as on LinkedIn. Workplace (remote, hybrid), Job type and Experience level don't: LinkedIn ignores them for logged-out visitors. The scraper adds their words to the search keywords instead, for example "Remote (Full-time OR Part-time) accountant", which brings closely matching jobs but is not an exact filter. Check employment_type and seniority_level in the results if you need to be strict. Sorting by "Most recent" is also ignored by LinkedIn; use Posted since or Date posted instead.

The run's status message says why, and the log names each input that failed. If a mistake in the input stops the run before anything is scraped, the run ends without results and its status message says what to change. Either way the Actor sends us a short error report, so we can fix the cause even if you never open an issue: the Actor's build, the reason, the counts from the end-of-run summary, whether your Apify plan is free or paid and, for an unexpected error, where in our code it happened. Web addresses and @usernames are blanked out first. The report never includes your input, your account, the pages you scraped or your results. Every run, failed or not, also sends one usage line as it ends, so we can see which options people use, what runs cost us and how well the data is filled: how many of each charged event it used (for example 120 full details) and the price your plan paid for them; the run's platform cost by item and its resources (time, memory, proxy traffic); whether it stopped at your maximum cost or maximum items; how it was started (Console, API, schedule, saved task, and for API runs the kind of tool, such as Make, Zapier or the Apify client, never the tool's full identity); our scraper's own retry and timing counts; and for each output field, how many results had it filled (counts only, never the values). That never includes your input, your account, your IP address, the pages you scraped or your results either. If you need help with a run, open an issue on the Issues tab and attach the run, or email support@kekliktech.com with the run's link; the run's log ends with both.

$0.25 per 1,000 jobs on Apify's free plan, down to $0.17 on the Business plan. Use the calculator above for your numbers.