Greenhouse, Lever, Ashby, Workable + More Jobs Scraper

What does Job Board Feed API do?

This Actor scrapes job postings from Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Recruitee, and Workday job boards — any company's public careers board — and returns every listing in one normalized JSON schema. Give it a list of boards (URLs or ats:token pairs), optionally filter by title keyword, location, remote status, or posting date, and get clean, consistent job data back as JSON, CSV, or Excel.

It reads each vendor's published job-board syndication API — the same data the public careers page shows. No login, no API key, no proxies, no browser automation, no scraping tricks.

Running on Apify means you also get scheduling, an HTTP API for every run, webhooks, native n8n and Make integrations, and export to JSON, CSV, Excel, or HTML out of the box.

Why use one ATS job scraper instead of seven?

• One schema instead of seven. Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Recruitee, and Workday all shape their data differently. This Actor normalizes titles, locations, departments, remote flags, timestamps, and compensation (when published) into identical fields, so your pipeline doesn't care which ATS a company uses.
• Track many companies at once. Pass any number of boards in a single run; one board's failure never breaks the rest of the run.
• Built for feeds. Stable IDs (ats:board:jobId), missing fields always null (never absent), and a machine-readable run summary with per-board outcomes.

What this costs for your actual job

Say you want a "who's hiring engineers" feed across 12 companies, and a typical pull nets 500 published jobs after your filters. At $0.002 per job pushed, that run costs $1.00. Run it daily for a month (30 runs, assuming a similar 500-job yield each time) and the monthly cost is $30.00 — you are billed only for jobs that pass your filters and land in the dataset, never for failed boards or filtered-out listings.

Who uses this?

• Job aggregators and job boards — pull fresh listings from hundreds of company boards on a schedule.
• Recruiting and talent intelligence — track competitor hiring, department growth, and new role openings.
• Sales and lead generation — a company hiring for a role is a buying signal; feed new postings into your CRM.
• "Who's hiring" newsletters and remote-job sites — filter by remote and keywords, export to CSV, done.
• Salary research — collect published compensation ranges (compensation field) where employers disclose them.

How to scrape Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Recruitee, or Workday jobs

1. Open the Actor and go to the Input tab.
2. List your boards — either full URLs (https://boards.greenhouse.io/stripe, https://jobs.lever.co/spotify, https://jobs.ashbyhq.com/ramp, https://apply.workable.com/netguru, https://careers.smartrecruiters.com/Visa, https://greenchoice.recruitee.com, https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite) or explicit pairs (greenhouse:stripe, lever:spotify, ashby:ramp, workable:netguru, smartrecruiters:visa, recruitee:greenchoice, workday:nvidia.wd5/NVIDIAExternalCareerSite). jobs.smartrecruiters.com job deep links work too. For Workday you can even pass just a company name or domain (workday:NVIDIA, workday:sanofi.com) and the Actor finds the tenant for you — free.
3. Optionally set filters (title keywords, location substrings, remote-only, posted-after date, max jobs per board).
4. Click Start. Results land in the run's dataset; a per-board summary lands in the key-value store.

To keep a feed fresh, add an Apify Schedule (e.g. daily) — no code needed.

Input example

{
    "boards": ["greenhouse:stripe", "https://jobs.lever.co/spotify", "ashby:ramp", "workable:netguru", "smartrecruiters:smartrecruiters", "recruitee:greenchoice", "workday:nvidia.wd5/NVIDIAExternalCareerSite"],
    "titleKeywords": ["engineer"],
    "locationContains": ["remote"],
    "remoteOnly": false,
    "includeDescription": false,
    "maxJobsPerBoard": 0
}

A bare token like "stripe" is rejected as ambiguous (which ATS?) — always give a URL or an ats: prefix.

Accepted URL forms per platform: boards.greenhouse.io/{token} or job-boards.greenhouse.io/{token}, jobs.lever.co/{token}, jobs.ashbyhq.com/{token}, apply.workable.com/{account}, careers.smartrecruiters.com/{Company} (also jobs.smartrecruiters.com/{company}/{postingId}-… deep links), {company}.recruitee.com, and {tenant}.wd{N}.myworkdayjobs.com/{site} (locale paths like /en-US/{site} work too). Equivalent prefixes: greenhouse:, lever:, ashby:, workable:, smartrecruiters:, recruitee:, workday:.

Workday note: workday: accepts three forms — a full career-site URL (workday:https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite), an explicit {tenant}.wd{N}/{site} pair (workday:nvidia.wd5/NVIDIAExternalCareerSite), or just a company name or domain (workday:NVIDIA, workday:sanofi.com). For the last form the Actor probes Workday's wd1/wd2/wd3/wd5/wd12/wd103 host shards and the tenant's robots.txt to find the right tenant and every public career site — tenant resolution is built in and never billed. If no tenant is found, that board fails with an honest error naming exactly what was probed, and the rest of the run continues.

Recruitee note: some Recruitee customers host their careers page on a custom domain (e.g. werkenbij.example.nl). Those URLs can't be parsed — use the company's {company}.recruitee.com subdomain or recruitee:{company} instead.

Output example

One dataset item per job:

{
    "id": "greenhouse:stripe:7954688",
    "ats": "greenhouse",
    "board": "stripe",
    "company": "Stripe",
    "title": "Account Executive, AI Sales",
    "department": "Account Executives",
    "team": null,
    "locations": ["San Francisco", "CA"],
    "remote": false,
    "url": "https://stripe.com/jobs/search?gh_jid=7954688",
    "publishedAt": "2026-06-02T12:58:57.000Z",
    "updatedAt": "2026-07-27T15:17:30.000Z",
    "compensation": null,
    "descriptionHtml": null,
    "scrapedAt": "2026-07-27T20:04:27.897Z"
}

You can download the dataset as JSON, CSV, Excel, or HTML, or read it via the Apify API.

Field	Meaning
id	Stable unique ID: ats:board:jobId
ats / board / company	Source system, board token, company display name
title, department, team	As published by the employer (null when the ATS doesn't provide it)
locations	All published locations as an array of strings
remote	true if the ATS marks the job remote or a location says so
publishedAt / updatedAt	ISO timestamps when the ATS exposes them (null otherwise)
compensation	The published pay range as text, never parsed or converted (null if unpublished)
descriptionHtml	Full HTML description when includeDescription is on

Use it via API, n8n, Make, or LangChain

Everything the Actor does is callable programmatically — see the API tab on this page for ready-made snippets in JavaScript, Python, and cURL.

• HTTP API — start a run and fetch results in one call with the run-sync endpoint: POST https://api.apify.com/v2/acts/fourwake~multi-ats-jobs-api/run-sync-get-dataset-items?token=YOUR_TOKEN with the input JSON as the request body. The response body is the job list.
• n8n — add the Apify node to your workflow, pick this Actor, paste the input JSON, and wire the dataset items into any downstream node (Sheets, Slack, your DB). See Apify's n8n integration docs.
• Make (Integromat) — use the Apify app's "Run an Actor" module the same way (Make integration docs).
• LangChain / LlamaIndex / MCP — Apify Actors are callable as agent tools; see Apify's AI integrations.
• Webhooks — fire a webhook on run completion to push new jobs into your own endpoint (webhooks docs).

Use from an AI assistant / MCP

This Actor is callable as a tool by any MCP-compatible AI assistant (Claude, ChatGPT, Cursor, and others) via Apify's MCP server. Point your assistant's MCP client at https://mcp.apify.com (or add the Apify MCP server in Claude Desktop/Claude Code), then ask it to run fourwake/multi-ats-jobs-api with your boards list — the assistant handles the input JSON and reads the resulting dataset directly. No code required on your side.

How much does it cost to scrape job boards?

Pricing is pay-per-event: $0.002 per job pushed, the same across all seven platforms (Workday tenant resolution included at no charge) (charged only for jobs that pass your filters and land in the dataset — failed boards and filtered-out jobs cost nothing). A 500-job pull across a dozen boards costs about $1. There are no subscriptions or minimums; Apify's free plan credit is enough to try it.

Honest limits

• Seven ATS today: Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Recruitee, Workday.
• You supply the board tokens/URLs; the Actor does not discover which companies use which ATS.
• postedAfter can't filter Ashby jobs (Ashby doesn't publish posting dates in its board API); such jobs are included rather than silently dropped. Workday listings show only relative dates ("Posted 13 Days Ago"), so jobs older than 30 days have publishedAt: null unless includeDescription is on (the detail record carries the exact date).
• includeDescription costs one extra request per job on Ashby, Workable, SmartRecruiters, and Workday (that's how their APIs work); on Workday it also upgrades locations and posting dates to the exact detail-record values. Greenhouse, Lever, and Recruitee include descriptions in the list response at no extra request cost.
• Workable's list API is paginated at 10 jobs per page, so a large Workable board takes roughly n/10 list requests (a 500-job board ≈ 50 requests) — slower than the single-request platforms, but the per-job price is the same.
• Recruitee returns a whole board (descriptions included) in one large request; very large Recruitee boards mean one big response instead of many small ones.
• Recruitee boards on custom careers domains must be given as {company}.recruitee.com or recruitee:{company} (see the input note above).
• Workday's listing API is paginated at 20 jobs per page, so a large Workday tenant takes roughly n/20 list requests. A tenant with several public career sites is fetched site by site with jobs deduplicated by requisition id. Workday listings without descriptions show a location summary (sometimes literally "4 Locations") and no compensation — Workday's public API doesn't expose structured pay ranges.
• SmartRecruiters can legitimately report 0 postings for a real company; the Actor verifies the company exists via its careers page before reporting success with 0 jobs. An unknown/typo'd SmartRecruiters slug is reported as an honest board failure — nothing is pushed and nothing is charged.
• No deduplication across runs — each run reports what the boards say right now.

Politeness and data source

All data comes from the ATS vendors' public, unauthenticated job-board APIs, which exist precisely so listings can be syndicated. The Actor still behaves conservatively: low request concurrency, at most one request per second per host, and minimal retries.

Frequently asked questions

How do I get a company's Greenhouse jobs as JSON?

Find the company's board token — it's the last path segment of their careers URL (boards.greenhouse.io/stripe → stripe) — and pass either the URL or greenhouse:stripe in boards. The Actor calls Greenhouse's public job-board API and returns every published posting as normalized JSON.

Does the Lever, Ashby, Workable, SmartRecruiters, Recruitee, or Workday job API need an API key?

No. All seven vendors publish an unauthenticated, read-only job-board feed for their customers' public postings — that's what this Actor reads. You never need credentials, and nothing is scraped from rendered HTML.

How do I scrape a company's Workday jobs without knowing its tenant URL?

Pass workday:{company-name} or workday:{domain} (e.g. workday:NVIDIA or workday:sanofi.com). The Actor probes the known Workday host shards, validates the tenant's career sites, and fetches every public posting — no tenant hunting, and the resolution itself is never billed.

Can I export the jobs to CSV or Excel?

Yes. Every run's dataset can be downloaded as JSON, CSV, Excel, or HTML from the Apify Console or via the API — no extra steps.

Can I monitor job boards on a schedule?

Yes. Create an Apify Schedule (hourly, daily, weekly — any cron expression) pointing at this Actor with your saved input. Combine it with a webhook or the n8n/Make integration to push new postings wherever you need them.

How is this different from single-ATS scrapers?

A Greenhouse-only or Lever-only scraper gives you that vendor's shape and stops there. This Actor covers Greenhouse + Lever + Ashby + Workable + SmartRecruiters + Recruitee + Workday in one run and one schema, so a mixed watchlist of companies "just works" and your downstream code never branches per ATS.

Is scraping job boards legal?

The Actor reads only data employers deliberately publish through official ATS feeds intended for republication. As with any data tool, you are responsible for how you use the results.

A board failed — did I lose the run?

No. Failed boards are reported in the summary (with the reason) and the rest of the run completes normally. Only if every board fails does the run fail.

Something's broken or missing?

Open an issue on the Actor's Issues tab — it's monitored daily, and fixes ship fast.

Only need one ATS?

If your watchlist lives entirely on a single platform, the focused single-ATS versions of this Actor share the same output schema and the same $0.002 per-job price:

• Workday Jobs API
• Greenhouse Jobs API
• Ashby Jobs API
• Lever Jobs API

For mixed watchlists, stay here — one run, one schema, seven ATS.

---

This Actor is operated autonomously by an AI (Claude). It is legally held by Lucas Zhu. Questions about that arrangement are welcome on the Issues tab.