LinkedIn Jobs Country Filter Scraper

No. It never uses a LinkedIn account, so there is none to block. It reads LinkedIn's public job search, the pages a logged-out visitor sees.

On the free plan, yes: $1.50 per 1,000 jobs here against $2.00 for curious_coder/linkedin-jobs-scraper. On paid plans it is $1.05 against $1.00. valig/linkedin-jobs-scraper is cheaper than both ($0.40 and $0.36). Choose this Actor for the exact country filter, other-country results dropped, job type and level re-checked on each job page, filtered-out jobs not charged, and an only-new-jobs mode for scheduled runs.

Run this Actor with your keywords and a country; it never logs in, so no LinkedIn account is needed. Then add Apify's Google Sheets integration on the Actor's **Integrations** tab, or download CSV or Excel from the run's **Storage** tab. Schedule it with 'Only new jobs since last run' on to get only new postings each time.

Two ways. For a fixed workflow, add Apify's n8n or Make node, choose **Run Actor**, enter aurelix/linkedin-jobs and map the dataset to the next step. For an AI agent (Claude, ChatGPT, Cursor or an n8n AI Agent node), add https://mcp.apify.com/?tools=aurelix/linkedin-jobs as an MCP server and ask for jobs in plain words; setup for each client is in the section above. Runs bill your own Apify account at the same per-result price.

$1.50 per 1,000 jobs ($1.05 on paid Apify plans), billed through your Apify account; you pay only for results. Apify's free plan includes $5 of credit a month, enough for about 3,333 jobs. A price change is scheduled; the Store page shows it before it applies.

No. The Actor reads only LinkedIn's public job pages that anyone can open without logging in. It never logs in and never uses cookies from an account.

It reads only public data any logged-out visitor can see: LinkedIn job postings. It goes at a polite pace, never logs in and never solves CAPTCHAs. It returns job posting fields (title, company, location, dates, description, link); personal emails in descriptions are removed and no member profiles or recruiter cards are read. To have a record removed, open an issue on this Actor's Issues tab; if LinkedIn formally asks us to stop, this Actor will stop. You are responsible for using the data lawfully, incl. anti-spam and privacy laws; this is not legal advice.

LinkedIn shows at most about 1,000 jobs per search, and results whose location, date, type or level do not match your filters are dropped (counted in the log). Narrow searches can have fewer matches.

Instead of free-text location, the search uses LinkedIn's numeric country id (verified for 30 countries), then any result whose location clearly names another country is removed.

On HTTP 429 the Actor waits (honouring Retry-After, doubling each time) and switches to a fresh proxy session. A search stops after six straight refusals and other searches carry on. The run still succeeds with the jobs it found, and its status message names the searches that stopped early.

Yes. The input is described for agents: give 'keywords' and optional filters. It works through Apify's MCP server and API.

Only jobs written to the dataset are charged, plus the small per-run start fee. Jobs dropped by the keyword, country, date, job type or level checks, duplicates and already-seen jobs are free. A search whose result pages show no matching titles three pages in a row stops early: in our test a nonsense keyword finished in about 5 s with 0 jobs. If LinkedIn rate-limits a search, the jobs found so far are kept and charged, and the status message names the searches that stopped. A run fails only when the input is invalid, or when every search failed and nothing was found.

By LinkedIn's job id. A job found by several keywords or search URLs in the same run is returned once, by the first search that finds it, and charged once. Across runs, switch on 'Only new jobs since last run'.

With details on, the Actor opens each job's public page, two at a time with short pauses, so it is polite and slower: in our test runs 50 jobs per search took about 4 minutes. With details off it reads only search pages: 100 jobs in 34 s and 800 jobs in about 2.5 minutes. LinkedIn rate-limiting adds waits.

Each job then comes from the search card only: title, company, company page, location, countries, posted date, job link and salary text where the card shows it. Seniority, employment type, industries, applicants, posted age and description stay empty. The keyword check then looks at the title only, and the job type and experience level re-checks are skipped. The price per job is the same.

The Actor remembers the job ids it returned for the same searches (keywords, country, location, filters and sort, or the URL's parameters) or for the state name you set. Already-seen jobs are skipped, free, and do not count toward 'Max jobs per search', so each run can fill its limit with new jobs. Ids are forgotten 60 days after they were last seen. Add a Slack or webhook URL to get the count and the top 10 new jobs after each run.

The Country list has 30 countries with LinkedIn's exact country id: US, CA, GB, IE, DE, FR, NL, BE, ES, PT, IT, CH, AT, SE, NO, DK, FI, PL, IN, SG, JP, PH, AU, NZ, AE, IL, ZA, BR, MX and AR. For anywhere else, type a location or paste a search URL with its geoId. Postings come in the language the employer wrote them. Keyword matching works on any alphabet; the built-in synonyms (RN for nurse, dev for developer) are English only.

Yes. URLs from linkedin.com/jobs/search and paths like /jobs/python-jobs-toronto work. These parameters are passed to LinkedIn: keywords, location, geoId, f_TPR, f_JT, f_E, f_WT, f_C, f_I, f_SB2, f_AL, distance and sortBy; others are ignored. A URL needs keywords, a location or a geoId. Only keyword relevance is re-checked on URL results.