LinkedIn Job Search Scraper | Jobs & Hiring Data
Pricing
from $0.86 / 1,000 job details
LinkedIn Job Search Scraper | Jobs & Hiring Data
Search LinkedIn jobs by title, location, company, workplace and experience. Retrieve detailed job records for recruiting, hiring signals and job-market research.
Pricing
from $0.86 / 1,000 job details
Rating
0.0
(0)
Developer
CrawlKite
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
2
Monthly active users
a day ago
Last modified
Categories
Share
Search LinkedIn jobs by title, location, company, workplace and experience. Retrieve detailed job records for recruiting, hiring signals and job-market research.
Quick start
- Enter the target URLs or a focused search.
- Start with a small result cap and one page.
- Review the dataset and SUMMARY, then export JSON, CSV or Excel.
{"jobTitles": ["Software Engineer"],"locations": ["London"],"maxItems": 5,"maxRequests": 10,"maxPages": 1}
Inputs
| Field | How to use it |
|---|---|
jobTitles | Job titles or keywords. Each title/location combination has its own result limit. |
locations | Location names, such as London. Use full country names to avoid ambiguous abbreviations. |
maxItems | Maximum returned records. Zero continues within page, request, spending and total-result limits. |
company | LinkedIn company URLs, names or IDs. Name/URL resolution uses a company lookup before searching jobs. |
workplaceType | Optional Workplace Type. Choose from the available options. |
employmentType | Optional Employment Type. Choose from the available options. |
experienceLevel | Optional Experience Level. Choose from the available options. |
salary | Optional Salary Filter. Choose from the available options. |
under10Applicants | Optional Under 10 Applicants. Leave blank to skip this filter. |
easyApply | Optional LinkedIn Easy Apply. Leave blank to skip this filter. |
postedLimit | Time window. The 1h option fetches the 24h search and keeps only search records with a usable posted date in the last hour. |
industryIds | Optional Industry IDs Filter. Enter one value per line; leave empty to skip this filter. |
sortBy | Choose date for newest first or relevance. |
geoIds | LinkedIn location IDs. When supplied, these replace text locations. |
page | First job-search page. Starts at 1. |
cookie | Unavailable. Do not provide session cookies; a non-empty value is rejected. |
userAgent | Unavailable. Custom user agents are not forwarded. |
proxy | Unavailable. Custom proxies are not forwarded. |
maxRequests | Stops before making more data-service requests. Searches, lookups and enrichment each count. |
maxResults | Total output cap across every input. |
maxPages | Upper page limit when takePages is zero or omitted. Company search cannot pass page 20. |
Sample output
One JSON object per returned record. Source fields and nested objects are preserved; available fields vary. Search and detail modes can return different fields. The following shortened excerpt comes from a bounded successful data-service test.
{"id": "4467100753","title": "AI Solutions Manager","linkedinUrl": "https://www.linkedin.com/jobs/view/4467100753/","postedDate": "2026-11-04T04:46:49.000Z"}
Pagination and limits
Free-plan trials are limited to two data-service requests and two output records per run. Search pages, company resolution and profile/job enrichment each consume a data-service request. Paid plans use your input caps and spending limit. A company-name lookup can use one of the two free requests; use company URLs or numeric IDs where supported.
Searches advance page by page and stop at the requested result, page, request or spending limit. Zero is never an unlimited-spend setting. Duplicate records are omitted within a run. A successful empty page ends that query. Saved run state allows a resumed run to continue within the same limits; it is not cross-run database deduplication.
Each selected job is fetched through Job Details. Multiple salary choices run separate searches, sharing the title/location result cap. The one-hour filter omits records without a usable date; cookies, custom user agents and custom proxies are unavailable and rejected.
Pricing
Search pages and returned records are charged separately. The displayed per-record event price is not an all-in search price.
| Returned record / 1,000 | Free | Starter | Scale | Business |
|---|---|---|---|---|
| Job details | $0.864 | $0.864 | $0.864 | $0.864 |
Each successful search page costs $0.0009, on every plan, in addition to returned-record charges. A successful empty page is still charged. Pages that contain only duplicates or records excluded by a filter are also charged.
Successful company-name resolution costs $0.0015 per company. Company URLs also require resolution; numeric company IDs avoid it. Repeated resolutions of the same input are cached within the run.
Platinum and Diamond use the Business event rates; no additional higher-tier discount is offered. There is no separate actor-start fee. Use Apify’s spending cap and inspect SUMMARY.billingEvents and SUMMARY.eventChargesUsd. Failed lookups produce no returned-record event; previously successful page or lookup events remain payable if a later operation fails.
Bulk comparison
The following is a modeled total per 1,000 results, including our page charges. It assumes 25 results per search page. Page sizes and matches are not guaranteed. HarvestAPI’s column excludes its separate startup events. Sparse runs can cost more with CrawlKite; this is not an unconditional 10% cheaper claim.
| Plan | Mode | HarvestAPI / 1,000 | CrawlKite modeled total / 1,000 |
|---|---|---|---|
| Free | Jobs with details | $1 | $0.9 |
| Starter | Jobs with details | $1 | $0.9 |
| Scale | Jobs with details | $1 | $0.9 |
| Business | Jobs with details | $1 | $0.9 |
Comparison checked 4 November 2026: HarvestAPI pricing. Returned fields, coverage and query behavior may differ.
For example, one successful page plus one job details on Free costs $0.001764, before any optional company resolution.
Responsible use
Use collected information for a clear purpose, respect privacy requirements and retain the fields your workflow needs. Never place passwords, API keys or private account cookies in public inputs or support discussions.
Support
Open an issue on this actor and share the affected run with the developer. Include the run ID and redacted input. Never post API keys, passwords, cookies or database credentials.
More CrawlKite LinkedIn tools
Choose the tool for the data you need. Each actor has its own input options and pricing; check its Pricing tab for event units and optional charges.
Profiles and people search
Companies
Posts and engagement
- Profile Posts
- Company Posts
- Post Search
- Post Comments & Replies
- Post Reactions
- Profile Comment History
- Profile Reaction History