LinkedIn Jobs Scraper | No Login, No Cookie, Job Descriptions
Pricing
from $2.00 / 1,000 jobs
LinkedIn Jobs Scraper | No Login, No Cookie, Job Descriptions
Search LinkedIn job postings and export title, company, location, posting date, link and the full job description as clean JSON. No login and no session cookie, so your own account is never involved. Pay per result.
Pricing
from $2.00 / 1,000 jobs
Rating
0.0
(0)
Developer
Starvoid
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Features
Share
LinkedIn Jobs Scraper
Search LinkedIn job postings and get back clean, structured rows: title, company, location, posting date, link, and the full job description.
No login. No session cookie. No account of yours is involved. Other LinkedIn scrapers ask you to paste your own li_at cookie, which puts your account at risk of being restricted. This one never asks, because it reads the job pages LinkedIn serves to everyone.
Useful for building a job board, tracking who a competitor is hiring, sourcing roles for candidates, salary and market research, or feeding fresh postings into your own app.
What you get
{"id": "4476983365","url": "https://www.linkedin.com/jobs/view/software-engineer-ii-java-aws-at-jpmorganchase-4476983365","title": "Software Engineer II (Java/AWS)","company": "JPMorganChase","companyUrl": "https://www.linkedin.com/company/jpmorganchase","location": "New York, NY","postedAt": "2026-10-08","postedText": "5 days ago","salary": "$120,000.00/yr - $160,000.00/yr","benefits": "Medical, Vision, Dental","applicants": "Be among the first 25 applicants","seniority": "Mid-Senior level","employmentType": "Full-time","industries": "Financial Services","description": "Job Description\n\nYou're ready to gain the skills...","scrapedAt": "2026-10-13T16:52:09.079Z"}
Every field, and when it is filled:
| Field | What it is |
|---|---|
id | LinkedIn's own job id, stable across runs, use it to deduplicate |
url | Direct link to the posting |
title | Job title as posted |
company | Hiring company name |
companyUrl | The company's LinkedIn page, empty for postings without one |
location | As the employer wrote it, from a city to a whole country |
postedAt | Posting date, YYYY-MM-DD |
postedText | LinkedIn's wording, for example 5 days ago |
salary | Only when the employer published a range, which is a minority of postings |
benefits | Only when the employer listed them |
applicants | Applicant count or LinkedIn's "be among the first" note |
seniority | Entry, Associate, Mid-Senior, Director, Executive. Empty when the employer left it blank |
employmentType | Full-time, Part-time, Contract, Temporary, Internship, Volunteer |
industries | Industry of the role |
description | The complete posting text, only when Full job description is on |
scrapedAt | When this row was read, so you can tell fresh rows from stored ones |
Results export as JSON, CSV, Excel or XML, and the same dataset is readable from the Apify API, so you can pull it straight into a database or a sheet.
How to use it
Fill in the form:
| Field | What it does |
|---|---|
| Keywords | What you would type into LinkedIn's job search, e.g. python developer |
| Location | City, region or country, e.g. Bengaluru, India. Leave empty for everywhere |
| Number of jobs | How many rows to return. Results arrive in pages of 25 |
| Full job description | On by default. Turn off for a faster, cheaper list |
| Date posted | Any time, past month, past week, past 24 hours |
| Workplace | On-site, remote, hybrid |
| Experience level | Internship through executive |
| Job type | Full-time, part-time, contract, temporary, internship, volunteer |
| Sort by | Most relevant, or most recent |
Or skip the form: build the search in your browser and paste the URL into Or paste a LinkedIn jobs search URL. Every filter in that link is used, so what you get matches what you saw.
{"keywords": "data engineer","location": "Berlin, Germany","maxResults": 100,"includeDetails": true,"datePosted": "week","workplace": "remote"}
Run it on a schedule to catch new postings daily, or start it from the Apify API and read the dataset when it finishes. Both work with the same input.
Pricing
Pay per result. There is no charge for starting a run, and nothing is billed for a search that returns nothing.
| Event | Price | What it is |
|---|---|---|
| Job | $2.00 / 1,000 | One listing row: title, company, location, date, link |
| Job with description | $5.00 / 1,000 | The same row plus the full description, seniority, employment type, industries and applicant count |
So a run of 200 jobs with descriptions costs $1.00, and the same 200 as a plain list costs $0.40. Turning Full job description off bills every row at the lower price. If a posting will not load, that row is billed at the lower price too, because that is what you received. Set a maximum cost per run and the run stops at it rather than going past it.
Notes
- Results come from the job pages LinkedIn publishes publicly, so there is no login step and your own account is never used.
- A few fields are members-only on LinkedIn's side and are therefore never returned: job function, recruiter contact details, and your application status.
- LinkedIn does not answer an unmatched search with nothing, it quietly drops your keywords and returns whatever else it has. Rows that do not match are dropped and never billed, so a typo costs you nothing.
- Runs end successfully even when LinkedIn rate limits us mid-search. You get the rows gathered so far, a note in the log, and you are billed only for what was delivered.
- Residential proxy is on by default, because LinkedIn blocks shared datacenter addresses. You can switch the proxy off to save proxy usage, and if that gets blocked the run switches to residential by itself rather than handing you an empty result.
Questions
Do I need a LinkedIn account? No, and you should not give one to any scraper.
How fresh is the data? It is read live at the moment you run it, not from a stored database.
How many jobs can one search return? LinkedIn's own search stops producing new results after roughly a thousand per query. For more than that, split the search by location, seniority or date range.
Can I get the recruiter or company contact details? Not from this actor. LinkedIn only shows those to signed-in members, and asking you for your cookie is exactly what this actor is built to avoid.
Why is salary empty on most rows? Because most employers do not publish one. The field is filled whenever LinkedIn shows a range on the posting.
Can I run the same search every day and only keep new jobs? Yes. Schedule it and deduplicate on id, which is LinkedIn's own and does not change between runs.