Multi-ATS Job Board Fetcher: Greenhouse, Lever, Ashby & More avatar

Multi-ATS Job Board Fetcher: Greenhouse, Lever, Ashby & More

Pricing

from $1.00 / 1,000 job results

Go to Apify Store
Multi-ATS Job Board Fetcher: Greenhouse, Lever, Ashby & More

Multi-ATS Job Board Fetcher: Greenhouse, Lever, Ashby & More

Fetch all open jobs from Greenhouse, Lever, Ashby, SmartRecruiters, Workable & Recruitee via official public APIs. Auto-detects the ATS from a domain. Salaries, remote flag, new-jobs-only mode.

Pricing

from $1.00 / 1,000 job results

Rating

0.0

(0)

Developer

Parth

Parth

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Get every open job from any company that hires through Greenhouse, Lever, Ashby, SmartRecruiters, Workable or Recruitee — in one normalized dataset. Paste careers-page URLs, ATS board links, company domains or board tokens. The Actor detects the applicant tracking system (ATS), reads the jobs live from that ATS's official public job-board API and returns one clean row per job: title, department, locations, remote flag, employment type, salary range (when published), full description, dates and apply link.

No login, no API keys, no proxies, no headless browser — just fast, cheap HTTP calls to the same public endpoints that power each company's own careers page.

What can it do?

  • 🔎 Auto-detect the ATS from a company domain (notion.so) or careers page URL (https://linear.app/careers)
  • 🏢 Six ATS in one schema: Greenhouse, Lever (US & EU), Ashby, SmartRecruiters, Workable, Recruitee
  • 💰 Salary ranges when the company publishes them (Ashby compensation, Greenhouse pay transparency, Lever salary range, Recruitee salary)
  • 🌍 Remote / hybrid / on-site flag from the ATS's own workplace field
  • 📝 Full descriptions as plain text and HTML (toggle off for lighter output)
  • 🧲 Filters: keywords, exclude keywords, locations, remote only, posted within N days, max jobs per company
  • 🔔 New jobs only mode for schedules: remembers what it already returned and outputs only new postings — and optionally the ones that were removed (filled/closed)
  • 🧾 Fair billing: companies that can't be resolved produce one free error row — you never pay for failures

Supported ATS and accepted inputs

ATSExample board URLToken form
Greenhousehttps://job-boards.greenhouse.io/airbnb, https://boards.greenhouse.io/stripegreenhouse:airbnb
Leverhttps://jobs.lever.co/palantir (EU: https://jobs.eu.lever.co/…)lever:palantir, lever-eu:…
Ashbyhttps://jobs.ashbyhq.com/openaiashby:openai
SmartRecruitershttps://careers.smartrecruiters.com/Experiansmartrecruiters:Experian
Workablehttps://apply.workable.com/huggingface/workable:huggingface
Recruiteehttps://bunq.recruitee.com/recruitee:bunq

You can also enter:

  • A company domain or careers page – stripe.com, https://www.example.com/careers. The Actor scans the page (and /careers, /jobs) for ATS links and embeds, and falls back to checking the company name on each ATS. This is billed as one ATS detection.
  • A bare board token – figma. All six ATS are checked; the first public board that matches wins.

Workday, iCIMS, Taleo and other ATS are not supported; such inputs return a free error row.

Input example

{
"companies": [
"https://job-boards.greenhouse.io/airbnb",
"https://jobs.lever.co/palantir",
"https://jobs.ashbyhq.com/openai",
"smartrecruiters:Experian",
"https://apply.workable.com/huggingface/",
"notion.so"
],
"maxJobsPerCompany": 100,
"keywords": ["engineer", "data"],
"locations": ["United States", "remote"],
"remoteFilter": "any",
"includeDescriptions": true,
"newJobsOnly": false
}
FieldWhat it does
companiesCareers URLs, ATS board URLs, domains or tokens (one per line)
maxJobsPerCompanyCap per company after filters (0 = all)
keywords / excludeKeywordsMatch against title, department and team
locationsKeep jobs whose location/country contains any of these strings
remoteFilterany, remote, non-remote
postedWithinDaysOnly jobs published in the last N days
includeDescriptionsInclude descriptionText and descriptionHtml
newJobsOnlyOutput only jobs not returned by previous runs
includeRemovedJobsAlso output removed_job rows for postings that disappeared
stateStoreNameNamed key-value store holding seen job IDs (use one per monitor)

Output example

One dataset item per job:

{
"recordType": "job",
"company": "OpenAI",
"ats": "ashby",
"boardToken": "openai",
"jobId": "8fb1615c-34bf-47c4-a1d1-b7b2f836bbd3",
"title": "Technical Program Manager, Compute Infrastructure",
"department": "Technical Program Management",
"team": null,
"location": "San Francisco",
"locations": ["San Francisco"],
"country": "United States",
"isRemote": null,
"workplaceType": null,
"employmentType": "full-time",
"salaryMin": 257000,
"salaryMax": 335000,
"salaryCurrency": "USD",
"salaryInterval": "year",
"salaryText": "$257K – $335K • Offers Equity",
"descriptionText": "ABOUT THE TEAM\n\nThe compute infrastructure team runs the GPU fleet…",
"descriptionHtml": "<h3><strong>About the Team</strong></h3>…",
"postedAt": "2026-03-12T16:38:15.322Z",
"updatedAt": null,
"jobUrl": "https://jobs.ashbyhq.com/openai/8fb1615c-34bf-47c4-a1d1-b7b2f836bbd3",
"applyUrl": "https://jobs.ashbyhq.com/openai/8fb1615c-34bf-47c4-a1d1-b7b2f836bbd3/application",
"boardUrl": "https://jobs.ashbyhq.com/openai",
"sourceUrl": "https://api.ashbyhq.com/posting-api/job-board/openai?includeCompensation=true",
"input": "https://jobs.ashbyhq.com/openai",
"detectionMethod": "direct",
"fetchedAt": "2026-10-21T07:17:41.207Z"
}

Other row types:

  • "recordType": "removed_job" – in new-jobs-only mode with Also report removed jobs: jobId, title, jobUrl, firstSeenAt, removedDetectedAt.
  • "recordType": "error" – an input that could not be resolved, with an error message. Error rows are never charged.

Fields that an ATS does not publish are null (e.g. Workable never publishes salary; Lever has no update date). The dataset has three ready-made views: Jobs overview, Salaries and Full details. Export to JSON, CSV, Excel, or pull via the Apify API.

Monitoring new jobs (scheduled runs)

  1. Turn on New jobs only and give the monitor a State store name (e.g. my-ai-startups).
  2. Run once — the first run returns all current jobs and saves them as the baseline.
  3. Add a Schedule (hourly/daily). Each run outputs only jobs that weren't returned before, plus removed_job rows if enabled.
  4. Connect a webhook / Zapier / Make / Slack integration to get alerts.

Seen IDs are stored per company in the named key-value store, so you can add or remove companies at any time. Delete the store to reset the baseline.

Pricing

This Actor uses pay-per-event pricing — you only pay for results:

EventPrice
Actor start (Apify's default start fee, once per run per GB of memory)$0.00005
Job result (one job row, incl. removed-job rows)$0.001 ($1 per 1,000 jobs)
ATS detection (company given as a domain/careers URL and successfully resolved)$0.002

Giving an ATS board URL or ats:token skips the detection fee. Unresolvable companies and error rows are free. Set Max cost per run in the run options and the Actor stops cleanly when the budget is reached. Platform compute for a typical run is tiny (256 MB, plain HTTP).

Examples: 50 companies × 40 jobs given as board URLs ≈ $2.00. A daily new-jobs monitor of 200 companies that sees ~30 new postings a day ≈ $0.03/day plus start fees.

Use cases

  • Recruiters & sourcers – track openings at target companies, spot hiring managers' new reqs early, build talent-mapping reports by department and location.
  • Job boards & aggregators – power a niche board (AI startups, remote-only, climate tech) with fresh, structured postings and direct apply links.
  • Sales intent signals – hiring for "Salesforce admin", "data engineer" or "SOC 2" is a buying signal. Feed new postings into your CRM, Clay or Apollo workflows to time outreach.
  • Market & salary research – compare published pay ranges, remote share and hiring velocity across companies and competitors.
  • AI datasets & agents – clean, deduplicated job text + HTML for RAG, classification, skills extraction and LLM agents (check the content signals note in the legal section before using data for model training).

FAQ

Does it need a login, API key or proxy? No. It uses each ATS's public, unauthenticated job-board endpoint — the same data shown on the company's careers page.

How do I find a company's board token? You don't have to — just paste the careers page or domain. If you know the board URL, paste it to skip the detection fee.

Why did detection fail for a company? The company may use an unsupported ATS (e.g. Workday, iCIMS), a JavaScript-only careers page without ATS links, or a token different from its domain name. Paste the ATS board URL directly. Failed detections are free.

Can detection pick the wrong board? Rarely. Detection prefers explicit ATS links found on the company's site (detectionMethod: "careers-page-link"). When it falls back to name matching ("slug-guess") it prefers boards whose job URLs live on the company's domain. Check detectionMethod and boardUrl if in doubt.

How fresh is the data? Live — every run reads the ATS at that moment. Nothing is cached between runs (except seen IDs in new-jobs-only mode).

How many jobs can it fetch? All open jobs on each board (tested with boards of 800+ jobs). Use maxJobsPerCompany or filters to limit cost.

Is personal data collected? No. Only job postings are returned. Recruiter names, emails, job mailbox addresses and posting "creator" fields are deliberately dropped.

Can I use it via API, MCP or integrations? Yes — like any Apify Actor: REST API, JavaScript/Python clients, schedules, webhooks, Zapier, Make, n8n and AI agents via the Apify MCP server.

This Actor only reads job postings that employers have chosen to publish publicly, through the ATS vendors' public job-board endpoints, without logging in or bypassing any access control. It does not collect personal data. Requests are rate-limited per host and honor Retry-After (Lever publishes a 1-second crawl delay, which is respected).

You are responsible for how you use the data. Respect the employer's and ATS vendor's terms, copyright in job descriptions, and data-protection laws (GDPR/CCPA). If you republish postings, link back to the original jobUrl/applyUrl rather than intercepting the application flow. Some sources publish machine-readable content signals — for example Workable's apply.workable.com declares ai-train=no — so do not use that data to train AI models. This is not legal advice.

Support

Found a board that doesn't parse correctly, or want another ATS (Personio, BambooHR, Teamtailor…)? Open an issue on the Actor's Issues tab with the board URL.