Indeed Jobs Scraper (Apify Actor)

Scrapes job listings from Indeed by talking directly to Indeed's internal GraphQL API (the same one Indeed's own mobile app uses) — no headless browser, so it's fast and cheap to run on Apify's compute units.

Input

All fields are set from the Actor's input UI (or INPUT.json for local runs) — nothing is hardcoded.

Output

Each job is pushed as one row to the default dataset with the fields:

url, title, employer, companyUrl, companyUrlDirect, datePosted, employmentType, isRemote, description, jobLocation, city, state, country, salary, salaryMin, salaryMax, salaryCurrency, salaryInterval, applyLink, logoUrl, companyIndustry, companyNumEmployees, companyRevenue, companyDescription, emails

Download results from the Run's Dataset tab as JSON / CSV / Excel / etc.

Running locally

pip install -r requirements.txt
apify run

Put your test input in storage/key_value_stores/default/INPUT.json, e.g.:

{
  "search": "motorsport",
  "location": "",
  "country": "uk",
  "distance": 50,
  "results": 50
}

Running tests

pip install -r requirements-dev.txt
pytest test/ -v

Tests run against fixtures captured from real Indeed API responses (test/fixtures/), including edge cases seen in production data such as a null employer and jobs with no salary listed.

Notes

• This relies on an internal, unofficial Indeed API and static API key extracted from Indeed's mobile app traffic. Indeed can change or block this at any time without notice — there's no SLA.
• For higher volumes, turn on the proxy configuration in the input to reduce the chance of rate limiting.
• No database, email, or Slack integrations — this is a clean, stateless actor: input in, dataset out, exactly what the Apify platform (and Store buyers) expect.