Before you run

An Apify Actor is a cloud tool with an input form, a Run button, logs, and a result dataset. You do not need to install code for this workflow. Create or sign in to an Apify account, then open the LinkedIn Jobs Search Scraper.

Use a bounded first runDo not begin with ten roles across ten countries. One role, one location, and 25 rows is enough to confirm that the fields fit your use case.

Choose what one paid result should mean

The cheapest Actor is useful only when its output matches the decision you need. Broad search returns individual job cards. Specialist and intelligence Actors charge more because they verify details, classify direct evidence, or produce a complete analysis instead of leaving that work to you.

QuestionUse this workflowCurrent price band
Which jobs match a role and location?Jobs Search: one normalized public job row per result.$0.34 / 1,000 rows
What does this known job page disclose?Job Details: one complete public detail record.$0.70 / 1,000 records
Which jobs meet a verified specialist condition?Remote, salary, Easy Apply, company, and skill workflows retain only supported results.$6-$8 / 1,000 results
Which listings support a high-value hiring conclusion?Internship, entry-level, executive, sponsorship, contract, and upcoming analysis workflows include direct evidence.$12-$25 / 1,000 results or analyses

Always read the live Apify Pricing tab before scaling. Diagnostics, incomplete fetches, duplicates, unsupported classifications, empty searches, and unchanged monitor checks are not sold as successful intelligence results.

Run the Actor

  1. Open the LinkedIn Jobs Search Scraper.
  2. Select Try for free or open the Input tab.
  3. Replace the starter values with the JSON below, or fill the same fields in the form.
  4. Click Start. When the run succeeds, open its Dataset tab.
{
  "queries": ["AI engineer"],
  "locations": ["United States"],
  "includeDescriptions": true,
  "maxResultsPerQuery": 25
}

You can also open the public remote AI-jobs example and adjust its inputs.

Read the output

Each retained dataset row represents one public job listing. Check these fields before increasing the run size:

FieldWhy it matters
jobIdStable listing identifier for deduplication and detail enrichment.
title, company, locationThe core job record used for filtering and analysis.
postedAt, postedDatePublic recency evidence. Treat relative dates carefully.
jobUrl, companyUrlSource links for verification.
descriptionReturned only when description enrichment succeeds.

Export from the Dataset tab using JSON, CSV, Excel, XML, or RSS. For automation, use the dataset API URL shown by Apify after the run.

Understand the cost

The broad Jobs Search acquisition Actor is currently $0.34 per 1,000 returned job rows. A 25-row result is a small validation run. Specialist Actors cost more because a paid row must pass a narrower evidence rule; company analyses and monitors charge only for complete supported analyses or meaningful events. Apify may also show platform usage depending on your account and plan. Check the Actor's live Pricing tab before a production schedule.

Troubleshooting

The run succeeded but returned no rows

Try a broader role phrase or location. A very narrow keyword, recent-date filter, or unavailable location can legitimately return nothing.

Some jobs do not have descriptions

Set includeDescriptions to true. If a public detail page is expired, incomplete, or blocked, the Actor does not bill an incomplete enriched row.

I need more than 200 jobs

Split the work into distinct keywords, locations, or scheduled Tasks. This keeps each run bounded and makes failures easier to diagnose.

Can I scrape profiles or private data?

No. This workflow is scoped to public job listings and does not collect private profiles or bypass access controls.

Next workflow

Use the raw search Actor for discovery. If you need company-level demand instead of individual vacancies, continue with the hiring-signals guide.

Turn rows into company signals

Group the bounded search results by employer, role family, and location while keeping sample job URLs for auditability.

Read the hiring-signals guide