Seven Apify Actors, one per applicant tracking system, all returning the same job schema. Pick the platform a company runs its careers page on, paste the career-site URL or the slug, and get every open job as clean JSON. Leave the input empty and the Actor walks a built-in index of companies on that platform instead, filtered by keyword, location and country.
Each Actor reads the public JSON endpoint the platform itself publishes for its customers' job boards. No login, no API key, no proxies, and the posting is there the moment the employer publishes it, before any aggregator copies it.
The seven Actors
| Platform | Actor | Companies in the built-in index |
|---|---|---|
| Greenhouse | Greenhouse Jobs Scraper | 2,018 |
| Ashby | Ashby Jobs Scraper | 2,442 |
| Workable | Workable Jobs Scraper | 690 |
| Lever | Lever Jobs Scraper | 397 |
| Teamtailor | Teamtailor Jobs Scraper | 197 |
| SmartRecruiters | SmartRecruiters Jobs Scraper | 180 |
| Workday | Workday Jobs Scraper | 82 |
Need several platforms in one run without knowing which system a company uses? Use the Job Search API, which detects the platform per company automatically across all of them.
What every row contains
title, company, platform, job_id, location, country, remote, department, employment_type, posted_at, apply_url, description. The schema is identical across the seven Actors and the Job Search API, so feeds combine without remapping. Where a platform does not publish a field you get null, never an invented value.
Input in one line
Companies as slugs or full URLs, for example https://boards.greenhouse.io/stripe, https://jobs.lever.co/palantir or https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite. Optional filters: keywords, location text, normalised country, remote only, a cap on jobs in total and per company, and a switch to drop the description for a lighter dataset.
Pricing
Pay per job returned: $2 per 1,000 jobs, charged only for rows that pass your filters. A company that is not on the platform costs nothing beyond a few seconds of compute. Apify's free monthly credit covers thousands of jobs, so you can evaluate any of the seven without paying.
Who uses this
- Recruiters and sourcers who want the posting before it reaches LinkedIn or Indeed.
- Job boards and job search products that need a normalised feed per employer.
- Sales and growth teams using hiring as an intent signal: who is hiring for what, where, since when.
- AI agents and automations (n8n, Make, Zapier, Apify MCP server) that need structured openings instead of HTML.
FAQ
Why one Actor per platform instead of one for all?
Most buyers already know the platform: they have a career-site URL in hand. A per-platform Actor needs no detection step, runs faster, and its index is specific to that platform. The Job Search API exists for the other case.
How fresh are the jobs?
Fetched from the employer at the moment you run it. There is no cached copy.
Will a job be charged twice?
No. Rows are de-duplicated per run on the employer's own job id before anything is charged.
Is this scraping?
These are the public JSON endpoints the platforms publish for their customers' career pages. No login and no anti-bot workaround.