LinkedIn Jobs Search API

Run up to 20 LinkedIn guest job searches in one call, apply supported filters, and export job cards deduplicated by job ID. Optional detail enrichment adds available public descriptions and criteria to as many as 250 returned jobs. No LinkedIn account, cookies, or proxy setup is required.

The current Store configuration charges $0.005 at run start and $0.002 per accepted job row. Apify platform usage is billed separately to the user.

Built for repeatable job research

Use one search for a focused sourcing export or submit a bulk query list for several keyword and location combinations. Recruiting operations teams can feed the results into an internal workflow. Labor-market researchers can repeat the same search definition across named markets without merging duplicate job IDs afterward.

Supported filters cover posting age, workplace type, employment type, experience level, Easy Apply, and sort order. Each run records query-level stop reasons plus overall completeness in OUTPUT_SUMMARY.

Sample output

{
  "jobId": "4440655897",
  "title": "Medical AI Evaluator (Remote, Hourly Contractor)",
  "company": "CNTXT AI",
  "companyUrl": "https://www.linkedin.com/company/cntxt-ai",
  "location": "Miami, FL",
  "salary": null,
  "postedAt": "2026-07-15",
  "postedText": "6 days ago",
  "url": "https://www.linkedin.com/jobs/view/4440655897/",
  "descriptionText": "We are looking for licensed clinicians to evaluate model output...",
  "seniorityLevel": "Mid-Senior level",
  "employmentType": "Contract",
  "jobFunction": "Health Care Provider",
  "industries": "Technology, Information and Internet",
  "applicantsText": "Over 200 applicants",
  "searchKeywords": "AI evaluator",
  "searchLocation": "United States",
  "scrapedAt": "2026-07-21T19:21:50.000Z"
}

Salary stays null when the search card does not show one. Detail fields stay null when enrichment is off, the detail cap has been reached, or the public detail fragment is unavailable.

Input

Set keywords, location, or both for a single search. The queries field accepts up to 20 bulk entries with keywords, location, and optional geoId or companyId. Shared filters apply to each bulk entry. maxItems caps the combined output at 10,000 jobs, and the run has a fixed 400-page request budget.

{
  "queries": [
    { "keywords": "clinical AI", "location": "United States" },
    { "keywords": "LLM evaluation", "location": "France" }
  ],
  "postedLimit": "week",
  "workplaceType": ["remote"],
  "includeJobDetails": true,
  "maxDetailItems": 100,
  "maxItems": 500
}

Turn on includeJobDetails to request description text, description HTML, seniority, employment type, job function, industries, and applicant text. Detail requests run sequentially and are capped at 250 rows. On a 500-row export with a 100-row detail cap, the remaining 400 rows keep their card data and null detail fields.

Output and export

The default dataset view shows the compact job-card fields. A second view exposes the available detail columns. Download results as JSON, CSV, Excel, or XML from Apify, or read the dataset through its API.

OUTPUT_SUMMARY reports query outcomes, total card and page counts, detail outcomes, stop reasons, and run completeness. Read it before treating a capped or interrupted export as complete.

Pricing

The current public configuration uses a $0.005 Actor-start event and a $0.002 job-collected event. A run that returns 340 accepted rows creates $0.685 in Actor event charges. Apify platform usage, including compute and data transfer where applicable, is charged separately under the user's Apify plan.

Blocked and empty runs have no per-job events. The start event and any platform usage can still apply.

Source and run limits

This Actor reads LinkedIn's public guest job-search surface and available public job-detail fragments. Guest access can stop at a login wall or return markup that the current parser cannot identify. Those conditions are recorded as incomplete outcomes.

Search work is bounded to 20 queries, 400 result-page requests, and 10,000 returned rows. Detail work is bounded to 250 sequential requests with a short interval between attempts. Pagination advances by the number of cards actually returned, which covers the 10-card and 25-card pages seen in structural test fixtures.

Common questions

Does it use my LinkedIn account? No. The input has no credential field; requests use guest job endpoints.

Why did the run return fewer jobs than maxItems? The public search may have ended, a configured limit may have been reached, or the guest surface may have blocked further pages. The query entry in OUTPUT_SUMMARY gives the recorded reason.

Can I fetch full descriptions for all 10,000 rows? The detail limit is 250 jobs per run. Larger outputs remain useful as card-level exports.

Does it scrape profiles? The scope covers job-search cards and public job-detail fragments.

Support

For a reproducible issue report, include the Apify run ID, the relevant input fields, and OUTPUT_SUMMARY. Remove private labels and downstream customer data before sharing a report.