# ATS Jobs API: Greenhouse, Lever, Ashby, Workday +2 | $2/1K (`cleanfeedsapi/ats-jobs-feed`) Actor Official/public job-board JSON from Greenhouse, Lever, Ashby, Workday, SmartRecruiters and Recruitee in one feed. Pass source:slug or paste the careers URL. Title, location, department, apply URL, dates, id. No login, no HTML scrape, no proxies. $2 per 1,000 jobs. - **URL**: https://apify.com/cleanfeedsapi/ats-jobs-feed.md - **Developed by:** [CleanFeeds API](https://apify.com/cleanfeedsapi) (community) - **Categories:** Jobs, Automation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $2.00 / 1,000 job rows This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## ATS Jobs API: Greenhouse, Lever, Ashby, Workday, SmartRecruiters, Recruitee | $2/1K **Quick start** - One ATS jobs API for six platforms: one JSON row per open job on every career board you list, with title, location, department, apply URL, dates and a stable id, in one schema. - Minimal input: `{"boards": ["greenhouse:stripe", "lever:spotify"]}` - Run it from the Console, the API, or the Apify MCP server; export JSON, CSV or Excel. Pull live job openings from company career boards into **one JSON dataset**. Six ATS platforms, one schema. Each source is read through the ATS's **own public job-board JSON** (the same data the career page itself loads): no HTML scraping, no login, no proxies, no API keys. You pass boards (`greenhouse:stripe`, `lever:spotify`, `ashby:ramp`, `workday:adobe.wd5/external_experienced`, `smartrecruiters:InPost`, `recruitee:prisma`) **or just paste the careers URL**. You get one row per job: title, location, department, apply URL, dates, stable id. ### Supported ATS | Source | What you pass | Endpoint used | |---|---|---| | Greenhouse | `greenhouse:` or `https://boards.greenhouse.io/` | boards-api.greenhouse.io (official) | | Lever | `lever:` or `https://jobs.lever.co/` | api.lever.co/v0/postings (official) | | Ashby | `ashby:` or `https://jobs.ashbyhq.com/` | api.ashbyhq.com/posting-api (official) | | Workday | `workday:./` or `https://..myworkdayjobs.com/` | career-site CXS jobs JSON (public, paginated) | | SmartRecruiters | `smartrecruiters:` or `https://jobs.smartrecruiters.com/` | api.smartrecruiters.com/v1 postings (official) | | Recruitee | `recruitee:` or `https://.recruitee.com` | `.recruitee.com/api/offers` (public) | ### Why this instead of scraping or the vendor API - Every source is the JSON the career page itself loads. Greenhouse, Lever, Ashby and SmartRecruiters publish official job-board APIs; Workday and Recruitee sites expose public JSON behind their JavaScript front ends. No browser, no rendering, nothing to fix when a theme changes. - No keys. All six endpoints are unauthenticated. You never need Harvest, Lever Data API, Workday tenant credentials or a SmartRecruiters token. - One schema instead of six. Each ATS names and nests fields differently; the Actor maps all of them to the same nine columns so a target-account list with mixed ATSs produces one flat table. - Pasted URLs are recognized for all six, including `job-boards.greenhouse.io` and localized Workday paths like `/en-US/`. - Pagination is handled where the ATS needs it: Workday in pages of 20 (up to 2,000 per site), SmartRecruiters in pages of 100. Postings without a title or URL are dropped before charging. ### Input examples ```json { "boards": ["greenhouse:stripe", "lever:spotify", "ashby:ramp"] } ``` ```json { "boards": ["https://adobe.wd5.myworkdayjobs.com/external_experienced", "https://jobs.smartrecruiters.com/InPost", "https://prisma.recruitee.com"], "maxJobsPerBoard": 500 } ``` | Field | Type | Default | Notes | |---|---|---|---| | `boards` | string list | three sample boards | `source:slug` or careers URL, any mix | | `maxJobsPerBoard` | integer | `0` | `0` = everything the board returns | ### Output example ```json { "source": "greenhouse", "company": "stripe", "title": "Backend Engineer", "location": "Dublin", "department": "Engineering", "url": "https://stripe.com/jobs/search?gh_jid=8172487", "posted_at": "2026-09-03T17:30:34.000Z", "updated_at": "2026-10-29T14:42:09.000Z", "id": "8172487" } ``` | Field | Meaning | |---|---| | `source` | `greenhouse` / `lever` / `ashby` / `workday` / `smartrecruiters` / `recruitee` | | `company` | the slug you passed | | `title`, `location`, `department` | as the ATS reports them (`department` is `null` where the ATS does not expose it, e.g. Workday) | | `url` | public job / apply page | | `posted_at` | ISO 8601 when the ATS provides it (Workday list payload does not, so `null`) | | `updated_at` | ISO 8601 (Greenhouse and Recruitee only) | | `id` | ATS-side job id, stable across runs, use it to diff new vs. closed jobs | A board that fails (bad slug, HTTP error) does **not** abort the run: it yields one row with `source`, `company` and `error`, and the other boards continue. **Not included, by design:** full job descriptions, salary enrichment, LinkedIn data, a global company index. This Actor is a clean, cheap feed for boards you already know. ### How much does it cost? Pay per event: **$2.00 per 1,000 job rows** (`job` event, $0.002 each) plus Apify's small Actor-start event. Platform compute is on us, not on you. Set a maximum charge per run in the Console and the Actor stops at the limit. The Apify free plan is enough to try it on the sample boards. ### Use cases - **Recruiting SaaS, talent CRMs**: nightly sync of target accounts' career boards. - **Hiring-intent signals**: diff today's `id`s against yesterday's dataset, new rows = new hiring. - **AI agents and MCP**: "list open roles at these 20 companies" through the Apify MCP server, no browser automation. - **Market maps**: location and department mix per company over time. ### Monitoring new jobs Schedule the Actor daily, keep the dataset per run, and compare `id` sets. Or wire the Apify n8n / Make / Zapier node to push new rows to Slack or a sheet. ### Integrations - **Apify API**: `POST https://api.apify.com/v2/acts/cleanfeedsapi~ats-jobs-feed/run-sync-get-dataset-items?token=` with the input JSON as the body. The response is the dataset, ready to parse. - **Scheduling**: open the Actor in the Apify Console, click Schedule, pick a cron (for example daily at 06:00) and the saved input runs on its own. Each run keeps its own dataset. - **n8n, Make, Zapier**: use the Apify integration in each tool, choose this Actor and pass the same input JSON. No per-Actor setup, no custom code. - **Apify MCP server for AI agents**: connect the Apify MCP server to Claude, Cursor or any MCP client and ask the agent to run `cleanfeedsapi/ats-jobs-feed` with these inputs. ### Related Actors by CleanFeeds - [greenhouse-jobs-api](https://apify.com/cleanfeedsapi/greenhouse-jobs-api): Greenhouse only, $1.50 per 1,000 rows. - [lever-jobs-api](https://apify.com/cleanfeedsapi/lever-jobs-api): Lever only, same schema. - [ashby-jobs-api](https://apify.com/cleanfeedsapi/ashby-jobs-api): Ashby only, same schema. - [workday-jobs-api](https://apify.com/cleanfeedsapi/workday-jobs-api): Workday only, with a 500-row default cap per site. - [remote-jobs-feed](https://apify.com/cleanfeedsapi/remote-jobs-feed): RemoteOK and Arbeitnow remote listings in one schema. Free sample dataset: [cleanfeeds/tech-jobs-daily on Hugging Face](https://huggingface.co/datasets/cleanfeeds/tech-jobs-daily). More feeds at [cleanfeeds.dev](https://cleanfeeds.dev). ### FAQ **Do I need an ATS API key?** No. Every source is a public, unauthenticated endpoint. **Is this HTML scraping?** No. Greenhouse, Lever, Ashby and SmartRecruiters publish official job-board APIs; Workday and Recruitee career sites load their job lists from public JSON endpoints that this Actor reads directly. **Why is `department` or `posted_at` empty for some rows?** The ATS does not return it in its list payload. Fields are never guessed. **One company 404s, what happens?** You get one `error` row for it and the rest of the run completes. **Where do I find the slug?** It is the token in the careers URL. Or paste the URL itself. **How do I detect new and closed items between runs?** `id` is the ATS-side job id (Greenhouse job id, Lever posting id, Ashby posting id, Workday requisition id, SmartRecruiters posting id, Recruitee offer id) and does not change between runs. Keep each run's dataset and compare `id` sets per `company`: ids present today but not yesterday are new roles, ids present yesterday but not today are closed. **What happens when a source fails?** A board that returns an HTTP error, an unknown slug or an unrecognized URL does not stop the run. The Actor logs the failure, pushes one row with `source`, `company` and `error` (the message), and continues with the next board. Error rows are not charged. If the per-run charge limit is reached, the Actor stops after the board that hit it and the remaining boards are skipped. Greenhouse jobs API, Lever jobs API, Ashby jobs API, Workday jobs API, SmartRecruiters jobs API, Recruitee jobs API, ATS job scraper alternative, career site jobs feed. # Actor input Schema ## `boards` (type: `array`): List of source:slug (greenhouse:stripe, lever:spotify, ashby:ramp, workday:adobe.wd5/external_experienced, smartrecruiters:InPost, recruitee:prisma) or just paste careers URLs (boards.greenhouse.io/..., jobs.lever.co/..., jobs.ashbyhq.com/..., \*.myworkdayjobs.com/..., jobs.smartrecruiters.com/..., \*.recruitee.com). ## `maxJobsPerBoard` (type: `integer`): 0 = all ## Actor input object example ```json { "boards": [ "greenhouse:stripe", "ashby:ramp", "lever:spotify" ], "maxJobsPerBoard": 0 } ``` # Actor output Schema ## `jobs` (type: `string`): Default dataset with all job rows (source, company, title, location, department, url, posted_at, updated_at, id). ## `summary` (type: `string`): Key-value store record SUMMARY: {boards, jobs} counts for the run. # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "boards": [ "greenhouse:stripe", "ashby:ramp", "lever:spotify" ] }; // Run the Actor and wait for it to finish const run = await client.actor("cleanfeedsapi/ats-jobs-feed").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "boards": [ "greenhouse:stripe", "ashby:ramp", "lever:spotify", ] } # Run the Actor and wait for it to finish run = client.actor("cleanfeedsapi/ats-jobs-feed").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "boards": [ "greenhouse:stripe", "ashby:ramp", "lever:spotify" ] }' | apify call cleanfeedsapi/ats-jobs-feed --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,cleanfeedsapi/ats-jobs-feed" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/BG2qaPimQnF89ogPf/builds/VRbafHcXfzMOmtS37/openapi.json