LinkedIn Jobs Scraper - No Login, Full Descriptions & Salary avatar

LinkedIn Jobs Scraper - No Login, Full Descriptions & Salary

Pricing

$1.00 / 1,000 job scrapeds

Go to Apify Store
LinkedIn Jobs Scraper - No Login, Full Descriptions & Salary

LinkedIn Jobs Scraper - No Login, Full Descriptions & Salary

Scrape LinkedIn job postings by keyword, location or search URL: title, company, full description, salary, seniority, job type, applicants, posted date. Exact job-type, experience and remote filters. No login, no cookies, no ban risk. Pay only for delivered jobs.

Pricing

$1.00 / 1,000 job scrapeds

Rating

0.0

(0)

Developer

Mikkel Bech-Hansen

Mikkel Bech-Hansen

Maintained by Community

Actor stats

0

Bookmarked

11

Total users

1

Monthly active users

3 days ago

Last modified

Features

Limited permissions

Share

Scrape LinkedIn job postings by keyword and location, or paste LinkedIn job-search URLs straight from your browser. Every listing comes back with the full description (text and HTML), parsed salary, seniority level, employment type, industry, applicant count, posted date and the job link.

  • No login, no cookies, no account-ban risk. Only the pages LinkedIn serves to logged-out visitors are used. Nothing to set up before the first run.
  • Filters that actually filter. LinkedIn ignores job-type, experience-level and (currently) remote/hybrid filters for logged-out searches, so most no-login scrapers silently return unfiltered results. This actor checks every posting against its own details and only delivers - and only charges for - the ones that match.
  • Pay only for delivered listings. No start fee, no charge for empty searches, filtered-out listings, or listings whose details could not be read.
  • Nothing lost to rate limits. LinkedIn rate-limits about one request in ten; the actor paces itself and retries, so a run of 400 listings finishes with 400 listings.

What you can do with it

  • Build a job board or job-alert feed for a niche (schedule it daily with datePosted: past24Hours).
  • Track which companies are hiring, for what roles, and how fast (lead generation, sales intelligence, competitor monitoring).
  • Collect salary ranges and requirements for market or compensation research.
  • Feed full job descriptions to an LLM for matching, tagging or summarising.

Input

FieldTypeDefaultNotes
keywordsstring"software engineer"Job title, skill, or company. Blank = every job in the location.
locationstring"United States"City, state, country, or region. Blank = worldwide.
maxItemsinteger50Total listings to deliver (1-10,000). You are charged per delivered listing only.
datePostedenum"any"any, past24Hours, pastWeek, pastMonth, past6Months, past12Months.
workplaceTypeenum"any"any, onSite, remote, hybrid. See "How filters work".
jobTypearrayallAny of fullTime, partTime, contract, temporary, internship, volunteer, other.
experienceLevelarrayallAny of internship, entryLevel, associate, midSenior, director, executive.
searchUrlsarraynoneLinkedIn job-search URLs copied from the browser. Company (f_C), location (geoId) and date filters in the URL are kept.
fetchFullDescriptionbooleantrueOff = search-result fields only (title, company, location, posted date, link), much faster.
proxyConfigurationobjectno proxyOptional. Works without one; Apify Proxy makes large runs somewhat faster.

Minimal example:

{
"keywords": "data analyst",
"location": "London",
"datePosted": "pastWeek",
"jobType": ["fullTime", "contract"],
"maxItems": 200
}

All jobs at one company (paste the URL from LinkedIn after picking the company filter):

{
"searchUrls": ["https://www.linkedin.com/jobs/search?keywords=engineer&location=United%20States&f_C=1441"],
"maxItems": 500
}

Output

One dataset record per job listing. Export as JSON, CSV, Excel or via the Apify API.

{
"jobId": "4476983365",
"title": "Software Engineer II (Java/AWS)",
"companyName": "JPMorganChase",
"companyUrl": "https://www.linkedin.com/company/jpmorganchase",
"location": "New York, NY",
"postedAt": "2026-10-29",
"postedAgo": "2 weeks ago",
"applyUrl": "https://www.linkedin.com/jobs/view/software-engineer-ii-java-aws-at-jpmorganchase-4476983365",
"companyLogoUrl": "https://media.licdn.com/dms/image/v2/.../jpmorganchase_logo?...",
"description": "Job Description\n\nYou're ready to gain the skills and experience needed to grow within your role...",
"descriptionHtml": "<strong>Job Description<br><br></strong>You&apos;re ready to gain the skills...",
"seniorityLevel": "Not Applicable",
"employmentType": "Full-time",
"jobFunction": null,
"industries": "Financial Services",
"salary": "$123,500.00/yr - $150,000.00/yr",
"salaryMin": 123500,
"salaryMax": 150000,
"salaryCurrency": "USD",
"salaryPeriod": "year",
"applicantCount": "Over 200 applicants",
"workplaceType": "onSite",
"applyType": "external",
"companyId": "1068",
"hiringBadge": "Actively Hiring",
"searchKeywords": "software engineer",
"searchLocation": "United States",
"scrapedAt": "2026-11-16T11:07:52.448Z"
}

Field notes:

  • salary* are filled only when the poster lists a salary (roughly 10-30% of listings, depending on country and role).
  • workplaceType (remote, hybrid, onSite or null) is read from the posting's title, location and explicit statements in the description. null means the posting doesn't say.
  • applyType is easyApply (apply on LinkedIn) or external (company site). LinkedIn does not reveal the external apply URL to logged-out visitors.
  • jobFunction is kept for compatibility; LinkedIn currently shows it to logged-out visitors on very few postings, so it is almost always null.
  • With fetchFullDescription off, everything from description to companyId is null except workplaceType, which is then based on title and location only.

How filters work

  • datePosted and anything inside searchUrls (company, geo, date) are applied by LinkedIn itself.
  • jobType and experienceLevel are checked against each posting's own "Employment type" and "Seniority level" fields, so results are exact. Postings that don't match are skipped and not charged.
  • workplaceType: at the start of each run the actor tests whether LinkedIn is honouring its workplace filter. If it is, LinkedIn's filter is used. If it isn't (the case since late 2026), the actor filters on the workplaceType it reads from each posting - precise, but postings that never state their arrangement are treated as on-site.
  • Filtering needs each posting's details, so filtered runs always open the detail pages, and a rare combination (say, contract + director) can scan many postings to find a few. The run's status line shows how many were checked and skipped.

Pricing

Pay-per-event: you pay per job listing delivered to the dataset, and nothing else - no start fee. The current price per listing is shown on the actor's Pricing tab. Not charged: searches with no results, listings skipped by your filters, and listings whose details could not be read (those are still delivered with their search-result fields, free). Set a maximum charge on the run and the actor stops exactly at your budget.

Speed and limits

  • About 70 listings per minute with full descriptions without a proxy, and about 110 per minute with Apify Proxy enabled. With fetchFullDescription off, several hundred per minute.
  • LinkedIn returns at most 1,000 listings per search. To collect more, split the search: several searchUrls (by city, company or keyword variant), or a narrower datePosted on a schedule. Duplicates across searches are removed automatically.
  • When a search has few real matches LinkedIn pads the results with loosely related listings. That is LinkedIn's behaviour for logged-out visitors, not a scraper error.
  • No cookie-gated data: no recruiter contact details, applicant lists or other fields LinkedIn shows only to logged-in users.

FAQ

Do I need a LinkedIn account or cookies? No. There is no login or cookie field at all.

Can I run it on a schedule for new jobs only? Yes. Use datePosted: past24Hours with a daily schedule (or pastWeek weekly). Use jobId to de-duplicate against earlier runs.

Can I call it from code, Make, n8n or Zapier? Yes - it is a standard Apify Actor with an API, webhooks and integrations; results are available as JSON, CSV or Excel.

Why did I get fewer listings than maxItems? LinkedIn ran out of results for the search (1,000 per search at most), or your filters matched fewer postings. The run's final status message says which.

Something looks wrong. Open an issue on the Issues tab with the run ID.

This Actor is an independent, third-party tool. It is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation.

It retrieves data from LinkedIn's public, logged-out guest job-search pages, never from a login-gated surface and never using a session cookie. Despite that, LinkedIn's User Agreement (Section 8.2) restricts automated data collection from the site regardless of whether the page requires login, and LinkedIn has pursued this in practice. Using this Actor may not comply with LinkedIn's terms. You are responsible for reviewing LinkedIn's terms and applicable law before using this Actor, and for how you use the data it returns.