# Multi-ATS Job Board Fetcher: Greenhouse, Lever, Ashby & More (`parth-tools/ats-job-board-fetcher`) Actor

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.

- **URL**: https://apify.com/parth-tools/ats-job-board-fetcher.md
- **Developed by:** [Parth](https://apify.com/parth-tools) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 job results

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

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

**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

| ATS | Example board URL | Token form |
|---|---|---|
| Greenhouse | `https://job-boards.greenhouse.io/airbnb`, `https://boards.greenhouse.io/stripe` | `greenhouse:airbnb` |
| Lever | `https://jobs.lever.co/palantir` (EU: `https://jobs.eu.lever.co/…`) | `lever:palantir`, `lever-eu:…` |
| Ashby | `https://jobs.ashbyhq.com/openai` | `ashby:openai` |
| SmartRecruiters | `https://careers.smartrecruiters.com/Experian` | `smartrecruiters:Experian` |
| Workable | `https://apply.workable.com/huggingface/` | `workable:huggingface` |
| Recruitee | `https://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

```json
{
    "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
}
```

| Field | What it does |
|---|---|
| `companies` | Careers URLs, ATS board URLs, domains or tokens (one per line) |
| `maxJobsPerCompany` | Cap per company after filters (`0` = all) |
| `keywords` / `excludeKeywords` | Match against title, department and team |
| `locations` | Keep jobs whose location/country contains any of these strings |
| `remoteFilter` | `any`, `remote`, `non-remote` |
| `postedWithinDays` | Only jobs published in the last N days |
| `includeDescriptions` | Include `descriptionText` and `descriptionHtml` |
| `newJobsOnly` | Output only jobs not returned by previous runs |
| `includeRemovedJobs` | Also output `removed_job` rows for postings that disappeared |
| `stateStoreName` | Named key-value store holding seen job IDs (use one per monitor) |

### Output example

One dataset item per job:

```json
{
    "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:

| Event | Price |
|---|---|
| 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.

### Legal note

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.

# Actor input Schema

## `companies` (type: `array`):

One company per line. Accepted formats:<ul><li><b>ATS board URL</b> – e.g. <code>https://job-boards.greenhouse.io/airbnb</code>, <code>https://jobs.lever.co/palantir</code>, <code>https://jobs.ashbyhq.com/openai</code>, <code>https://careers.smartrecruiters.com/Experian</code>, <code>https://apply.workable.com/huggingface</code>, <code>https://bunq.recruitee.com</code></li><li><b>ATS prefix + board token</b> – e.g. <code>greenhouse:airbnb</code>, <code>lever:palantir</code>, <code>ashby:openai</code>, <code>smartrecruiters:Experian</code>, <code>workable:huggingface</code>, <code>recruitee:bunq</code>, <code>lever-eu:token</code></li><li><b>Bare board token</b> – e.g. <code>stripe</code> (all supported ATS are probed)</li><li><b>Company domain or careers page</b> – e.g. <code>notion.so</code> or <code>https://www.example.com/careers</code>. The ATS is auto-detected (billed as one <i>ATS detection</i> event when found).</li></ul>Workday is not supported. Companies that cannot be resolved produce one free error row.

## `maxJobsPerCompany` (type: `integer`):

Maximum number of jobs to output per company (after filters). <code>0</code> = no limit (all open jobs). Use this to cap cost.

## `keywords` (type: `array`):

Only keep jobs whose title, department or team contains at least one of these words (case-insensitive). Example: <code>engineer</code>, <code>sales</code>, <code>data</code>. Leave empty to keep all jobs.

## `excludeKeywords` (type: `array`):

Drop jobs whose title, department or team contains any of these words, e.g. <code>intern</code>, <code>senior</code>.

## `locations` (type: `array`):

Only keep jobs where any location (or country code) contains one of these strings, e.g. <code>London</code>, <code>United States</code>, <code>Germany</code>, <code>remote</code>.

## `remoteFilter` (type: `string`):

Keep all jobs, only remote jobs, or only non-remote (on-site / hybrid) jobs. Remote status comes from the ATS's workplace-type field when published, otherwise from the location text.

## `postedWithinDays` (type: `integer`):

Only keep jobs first published in the last N days (jobs without a published date are kept). <code>0</code> = no date filter.

## `includeDescriptions` (type: `boolean`):

Include the full job description as plain text and HTML. Turn off for smaller, faster output (SmartRecruiters then skips its per-job detail requests).

## `newJobsOnly` (type: `boolean`):

Remember job IDs already returned (per company) in a named key-value store and output only jobs that were not seen in previous runs. The first run returns all current jobs as the baseline. Ideal for schedules and job alerts.

## `includeRemovedJobs` (type: `boolean`):

With <i>New jobs only</i>: also output one <code>removed_job</code> row for each previously seen job that is no longer on the board (filled or closed).

## `stateStoreName` (type: `string`):

Name of the key-value store that keeps seen job IDs for <i>New jobs only</i>. Use different names to run independent monitors (e.g. one per saved search). Letters, digits and dashes only.

## `maxConcurrency` (type: `integer`):

How many companies are fetched in parallel (1–10). The default is polite to the ATS APIs.

## Actor input object example

```json
{
  "companies": [
    "https://job-boards.greenhouse.io/airbnb",
    "https://jobs.lever.co/palantir",
    "https://jobs.ashbyhq.com/openai",
    "smartrecruiters:Experian",
    "https://apply.workable.com/huggingface/",
    "https://bunq.recruitee.com/"
  ],
  "maxJobsPerCompany": 20,
  "remoteFilter": "any",
  "postedWithinDays": 0,
  "includeDescriptions": true,
  "newJobsOnly": false,
  "includeRemovedJobs": false,
  "stateStoreName": "ats-job-board-fetcher-state",
  "maxConcurrency": 4
}
```

# Actor output Schema

## `jobs` (type: `string`):

No description

## `jobsFull` (type: `string`):

No description

## `summary` (type: `string`):

No description

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "companies": [
        "https://job-boards.greenhouse.io/airbnb",
        "https://jobs.lever.co/palantir",
        "https://jobs.ashbyhq.com/openai",
        "smartrecruiters:Experian",
        "https://apply.workable.com/huggingface/",
        "https://bunq.recruitee.com/"
    ],
    "maxJobsPerCompany": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("parth-tools/ats-job-board-fetcher").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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "companies": [
        "https://job-boards.greenhouse.io/airbnb",
        "https://jobs.lever.co/palantir",
        "https://jobs.ashbyhq.com/openai",
        "smartrecruiters:Experian",
        "https://apply.workable.com/huggingface/",
        "https://bunq.recruitee.com/",
    ],
    "maxJobsPerCompany": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("parth-tools/ats-job-board-fetcher").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 '{
  "companies": [
    "https://job-boards.greenhouse.io/airbnb",
    "https://jobs.lever.co/palantir",
    "https://jobs.ashbyhq.com/openai",
    "smartrecruiters:Experian",
    "https://apply.workable.com/huggingface/",
    "https://bunq.recruitee.com/"
  ],
  "maxJobsPerCompany": 20
}' |
apify call parth-tools/ats-job-board-fetcher --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,parth-tools/ats-job-board-fetcher"
        }
    }
}
```

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 <APIFY_API_TOKEN>` 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/5RcbsG81Elwjqe2ms/builds/1rsQkMZURDfYc1rLF/openapi.json
