Indeed + LinkedIn

Collect job listings from Indeed and LinkedIn. Search one job title and city or provide lists of titles and cities, then download structured results.

Features

Process	What you get
Indeed jobs	Available job titles, companies, locations, dates, descriptions, salaries and application links
LinkedIn jobs	Public job cards with titles, companies, locations, links and any displayed salary snippets
Search filters	Source-supported country, distance, job type, remote-work and posting-age filters

LinkedIn collection does not include full job descriptions or detailed company profiles. Field and filter availability differ by source.

Quick start

Enter a job title and city, select Indeed, LinkedIn or both, and run the Actor.

{
  "title": "software engineer",
  "city": "Atlanta",
  "country": "USA",
  "engines": "3",
  "jobtype": "fulltime",
  "remote": "No",
  "last": "all",
  "distance": "50",
  "max": 40,
  "proxy": { "useApifyProxy": true }
}

Use engines: "1" for Indeed, "2" for LinkedIn or "3" for both. For bulk searches, provide titles and/or cities lists. Lists override the corresponding single value; each title is searched in each city, up to 100 combinations.

max limits real jobs per source and title/city pair. maxResults optionally limits the total real jobs across the run. Duplicate source job IDs are removed across searches. The same job listed separately on Indeed and LinkedIn can appear once from each source.

Results

Each job is a separate row. Fields include id, site, job_url, title, company, location, date_posted, description, salary fields and available company details. Posting dates use Unix milliseconds. Unknown or unavailable values are null. Salary ranges with known hourly, daily, weekly or monthly units are converted to annual amounts when both bounds are available.

During pay-per-event pricing, real jobs have rowType: "result"; minimum-charge padding has rowType: "placeholder". Placeholder rows contain no job data. The run summary shows actual job counts, errors and any limits reached.

Pricing

See the Pricing tab for the active rate and any scheduled changes. The pay-per-event rate is $1.25 per 1,000 unique jobs + $0.01 per start, including platform usage. Each valid pay-per-event run with at least one search input includes a shared minimum charge of 100 unique job units across all sources and searches. Results above 100 are charged individually at the listed event rate. The minimum also applies when fewer jobs are returned, no matches are found.

When fewer than 100 real jobs are returned, clearly marked placeholder rows fill the difference and contain no scraped job data; filter them out when exporting. For example, 10 jobs produce 10 job rows and 90 placeholders. Each separate run has its own minimum, including scheduled or API runs. Platform usage is included. Smaller result limits do not reduce the PPE minimum charge. Set a maximum run budget of at least $0.14.

Tips and limitations

• Apify proxy is selected by default for reliable cloud searches. You can disable it to try direct requests. If a source blocks your search, try another proxy. Residential proxies are used only if you select them.
• Remote flags use source labels and text hints; they can include hybrid jobs or mentions of remote work.
• Results depend on the source's public listings and search behavior; filters are requests to the source, not a guarantee of exact matches.
• Country selects the Indeed region. For LinkedIn, include the region or country in the city/location value when needed.
• Available results may be fewer than requested. LinkedIn public searches are limited to approximately the first 1,000 listings per search.
• If one source is unavailable, jobs from the other source can still be returned. Blocked searches are reported in the run summary; all-blocked runs return labeled placeholders with “Try another proxy”.
• Large runs stop when the result, spending, time or transfer limit is reached. No sign-in credentials are required.

Support

Open an issue with your run URL and search settings. Do not share passwords or proxy credentials.

Unsuccessful lookups

Where listed in the Pricing tab, a handled lookup problem that prevents a run from returning any real results produces one clear error record and a single $0.02 unsuccessful-lookup fee, in addition to any listed start fee.