LinkedIn Job Details Scraper | Job URLs to JSON
Pricing
from $0.90 / 1,000 job details
LinkedIn Job Details Scraper | Job URLs to JSON
Turn LinkedIn job URLs or numeric job IDs into detailed JSON records with available descriptions, company data and job metadata.
Pricing
from $0.90 / 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
Turn LinkedIn job URLs or numeric job IDs into detailed JSON records with available descriptions, company data and job metadata.
Quick start
- Enter current LinkedIn job URLs in
jobUrlsor numeric job IDs injobIds. - Start with one or two jobs and a small spending limit.
- Review the dataset and SUMMARY, then export JSON, CSV or Excel.
{"jobUrls": ["https://www.linkedin.com/jobs/view/4467100753/"],"maxRequests": 5}
Replace the illustrative job ID above with a current job URL or an ID from Job Search.
Inputs
| Field | How to use it |
|---|---|
jobUrls | Optional LinkedIn job URLs. Enter one value per line; leave empty to skip this filter. |
jobIds | Optional LinkedIn job IDs. Enter one value per line; leave empty to skip this filter. |
urls | Optional Job URLs (alias). Enter one value per line; leave empty to skip this filter. |
maxRequests | Stops before making more data-service requests. Searches, lookups and enrichment each count. |
maxResults | Total output cap across every input. |
maxPages | Not used for direct job-detail lookups. |
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.
Each distinct job ID is looked up once. The run stops at its request, output or spending limit. Duplicate IDs are omitted within a run. Saved run state supports resuming the same input; it is not cross-run database deduplication.
Pricing
This actor charges per successfully returned job detail. There is no search-page charge.
| Returned record / 1,000 | Free | Starter | Scale | Business |
|---|---|---|---|---|
| Job details | $0.9 | $0.9 | $0.9 | $0.9 |
No search-page or actor-start charge applies to direct job-detail requests.
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 direct job-detail lookups with no search pages. 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 | Job details | $1 | $0.9 |
| Starter | Job details | $1 | $0.9 |
| Scale | Job details | $1 | $0.9 |
| Business | Job details | $1 | $0.9 |
Comparison checked 4 November 2026: HarvestAPI pricing. This is a benchmark against the Job Search actor’s job-detail event; no separate current standalone Job Details counterpart was confirmed. Returned fields, coverage and query behavior may differ.
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