LinkedIn Jobs Scraper
Pricing
$1.00 / 1,000 jobs
LinkedIn Jobs Scraper
Scrape LinkedIn job search results and job details in guest mode: title, company, location, posted date, description, seniority, and applicant insights. No login required.
Pricing
$1.00 / 1,000 jobs
Rating
0.0
(0)
Developer
Cravl
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
LinkedIn Jobs Scraper
Scrape LinkedIn jobs in guest mode: no login, no cookies.
Two modes
- Search (
/jobs/search?keywords=...): full job cards (id, title, company + URL, location, posted date, salary when shown) honoring every query parameter verbatim (workplace type, experience level, posted window, Easy Apply, distance). Paginates through the guest fragment API (10 cards/page) up tojobPages. - Job detail (
/jobs/view/ID): full description, seniority/employment/function/industries criteria, applicant count, canonical URL. WithjobDetails=N, the first N search results are enriched with their detail pages.
Input
| Field | Type | Description |
|---|---|---|
directUrls | array | Search URLs and/or job view URLs |
jobPages | integer | Guest-API pagination pages (1–40, default 5) |
jobDetails | integer | Enrich first N search results with detail pages (0–25, default 0) |
proxyConfiguration | object | Apify proxy settings |
Output
- Search records:
kind: "search",total,fetched,pages,jobs[](id, title, company, companyUrl, location, postedDate, salaryText) - Job records:
kind: "job",jobId,title,company,location,description,criteria,applicants,canonicalUrl
Use cases
- Job market monitoring and salary research
- Lead generation for recruiting tools
- Applicant-demand tracking (applicant counts)
Migrating from other Apify Actors
Cravl Actors accept Apify-style inputs and emit familiar field names alongside Cravl-specific fields, so most pipelines migrate with minimal changes.
Input compatibility
startUrls(array of URLs, or objects with aurlkey) is accepted as an alias fordirectUrls.
Output compatibility
Search URLs emit one item per job (record job) with searchUrl and searchTotal context. Job URLs emit one item with added aliases: jobPostingId, jobPostingUrl, postedAt, applicantCount, companyName, jobLocation, salary, inputUrl.