# Greenhouse, Lever & Ashby Jobs Scraper (`datatap/ats-jobs`) Actor

Get job postings from Greenhouse, Lever and Ashby public job boards in one normalized JSON schema: title, department, location, remote, salary and description. Filter by keywords, location, department, employment type and posting date.

- **URL**: https://apify.com/datatap/ats-jobs.md
- **Developed by:** [datatap](https://apify.com/datatap) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 jobs

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

## Greenhouse, Lever & Ashby Jobs Scraper — Normalized Job Postings API

Fetch job postings from company job boards hosted on **Greenhouse**, **Lever** and **Ashby**
and get every posting back in **one normalized JSON schema**, no matter which ATS (applicant
tracking system) the company uses. Give it a list of companies, optionally filter by title,
location, department, employment type, remote and posting date, and download the results as
JSON, CSV or Excel — or read them through the Apify API as a simple jobs API.

### Who uses it

- **Job boards and aggregators** — sync the open roles of a fixed list of companies every
  day, in one schema, without writing three ATS integrations.
- **Recruiting and labor-market research** — titles, departments, locations, remote share
  and salary ranges (Lever, Ashby) across many companies, ready for a spreadsheet or BI tool.
- **Sales and lead generation** — hiring is a buying signal: track which companies are
  opening engineering, sales or data roles right now.
- **AI agents** — a small, predictable input schema that works as a tool through the Apify
  MCP server (see below).

### What it does

- Reads each company's **public job-board API** on Greenhouse, Lever or Ashby.
- Converts every posting to the same fields: title, company, department, team, location(s),
  country, workplace type, remote flag, employment type, URLs, dates, salary and description.
- Applies your filters, then saves the matching jobs to the run's dataset.
- Keeps going when one company fails (for example, a slug that does not exist); the run
  fails only if every company fails. A *malformed* entry — unknown host or prefix, or a slug
  with illegal characters — stops the run before any job is fetched or charged.
- Stops as soon as `maxItems` jobs are saved, so you control the cost of every run.

### Supported companies and input formats

Any company whose careers page runs on one of these job boards. Add each one to `companies`
in either form:

| ATS | `ats:slug` form | Job-board URL forms |
|---|---|---|
| Greenhouse | `greenhouse:airbnb` | `https://boards.greenhouse.io/airbnb`, `https://job-boards.greenhouse.io/airbnb` |
| Lever | `lever:leverdemo` | `https://jobs.lever.co/leverdemo` |
| Lever (EU) | `lever-eu:acme` | `https://jobs.eu.lever.co/acme` |
| Ashby | `ashby:ashby` | `https://jobs.ashbyhq.com/ashby` |

- The slug is the part of the job-board URL right after the host. Links to a single job
  (`.../airbnb/jobs/123`) work too; only the board is used.
- The prefix is case-insensitive. Duplicate entries are removed.
- Greenhouse and Ashby slugs are case-insensitive (`greenhouse:Airbnb` is the same board as
  `greenhouse:airbnb`) and are normalized to lowercase in `id` and `company`. Lever slugs are
  case-sensitive: type them exactly as they appear in the board URL.
- If any entry is malformed (unknown host or prefix, or a slug with characters other than
  letters, digits, `.`, `_`, `-`), the run stops before any job is fetched or charged and the
  log names every bad entry. A well-formed slug that does not exist only fails that company.
- `lever:` entries try Lever's global instance and fall back to the EU instance only when
  the board is not found there. `lever-eu:` and `jobs.eu.lever.co` always use the EU instance.

### Input example

```json
{
  "companies": [
    "greenhouse:airbnb",
    "https://jobs.lever.co/leverdemo",
    "ashby:ashby"
  ],
  "titleKeywords": ["engineer"],
  "excludeTitleKeywords": ["intern"],
  "locationKeywords": ["remote", "berlin"],
  "departmentKeywords": ["engineering"],
  "employmentTypeKeywords": [],
  "remoteOnly": false,
  "postedWithinDays": 0,
  "includeDescription": true,
  "maxItems": 500,
  "maxConcurrency": 5
}
```

Only `companies` is required. Everything else has a default.

### Output example

One dataset item per job. Descriptions are trimmed here for space.

```json
{
  "id": "ashby:ashby:7458d4e9-da2e-47bd-98cb-adfda43d42b2",
  "source": "ashby",
  "company": "ashby",
  "companyName": "ashby",
  "externalId": "7458d4e9-da2e-47bd-98cb-adfda43d42b2",
  "title": "Engineering Manager - EU",
  "department": "Engineering",
  "team": "EMEA Engineering",
  "location": "Remote - European Union",
  "locations": ["Remote - European Union", "Spain", "Germany", "Berlin", "Netherlands"],
  "country": "European Union",
  "workplaceType": "remote",
  "isRemote": true,
  "employmentType": "FullTime",
  "url": "https://jobs.ashbyhq.com/ashby/7458d4e9-da2e-47bd-98cb-adfda43d42b2",
  "applyUrl": "https://jobs.ashbyhq.com/ashby/7458d4e9-da2e-47bd-98cb-adfda43d42b2/application",
  "publishedAt": "2024-03-04T14:29:08Z",
  "updatedAt": "",
  "salary": { "min": 110000, "max": 185000, "currency": "EUR", "interval": "year" },
  "descriptionHtml": "<p>How do you feel about software engineers writing product specs, ...</p>",
  "descriptionText": "How do you feel about software engineers writing product specs, ...",
  "scrapedAt": "2026-10-01T15:54:50Z"
}
```

| Field | Notes |
|---|---|
| `id` | `source:company:externalId` — stable and unique across all sources; use it to dedupe between runs. |
| `source` | `greenhouse`, `lever` or `ashby`. |
| `company` / `companyName` | Slug / display name (Greenhouse's company name; Lever and Ashby use the slug). |
| `location` / `locations` | Main location / every listed location. |
| `country` | From Lever and Ashby when given, otherwise `""`. |
| `workplaceType` | `remote`, `hybrid`, `onsite` or `""`. |
| `employmentType` | As the ATS writes it (e.g. `FullTime`, `Full-time`); `""` for Greenhouse. |
| `publishedAt`, `updatedAt`, `scrapedAt` | UTC RFC 3339, or `""` when the ATS does not give one. |
| `salary` | `{min, max, currency, interval}` or `null`. Lever and Ashby only. |
| `descriptionHtml`, `descriptionText` | Empty when `includeDescription` is off. |

### Filters

All keyword filters are **case-insensitive substring** matches. Within one list, any keyword
may match (OR). Across lists, every list you fill in must match (AND). Empty lists are ignored.

| Input | Matches against | Default |
|---|---|---|
| `titleKeywords` | title | all titles |
| `excludeTitleKeywords` | title — matching jobs are dropped | none dropped |
| `locationKeywords` | location, all locations, country | all locations |
| `departmentKeywords` | department, team | all departments |
| `employmentTypeKeywords` | employment type (excludes all Greenhouse jobs, see Limits) | all types |
| `remoteOnly` | jobs marked remote | `false` |
| `postedWithinDays` | publish date, or update date if no publish date; undated jobs are dropped (0–3650, 0 = off) | `0` |
| `includeDescription` | keep HTML and plain-text descriptions | `true` |
| `maxItems` | stop after this many saved jobs (0 = no limit) | `0` |
| `maxConcurrency` | company boards fetched at once (1–20) | `5` |

### Pricing

**Pay per event: $0.0015 per job saved to the dataset** ($1.50 per 1,000 jobs), plus Apify's
small per-run Actor start event. Jobs removed by your filters are not charged. Use `maxItems`,
or the run's **Maximum cost per run** option, to put a hard ceiling on what one run can cost —
the Actor stops saving jobs once either limit is reached.

### Use it from AI agents (MCP)

Add this Actor as a tool to Claude, Cursor or any MCP client through the Apify MCP server:

```json
{
  "mcpServers": {
    "ats-jobs": {
      "url": "https://mcp.apify.com?tools=datatap/ats-jobs"
    }
  }
}
```

The first connection signs you in to Apify in the browser. Then ask, for example: *"List
the remote engineering jobs at Airbnb, Stripe and OpenAI posted in the last week."*

### Reliability

- One company failing (a wrong slug, a board that is down) never fails the others.
- One malformed posting is skipped and logged; the rest of that company's jobs are kept.
- If Apify restarts or migrates a run, jobs it already saved are recognized and are not
  saved or charged again.
- Network errors and rate limits are retried with backoff.

### Limits

- **Greenhouse:** its public job-board API has no salary and no employment type, so
  `salary` is `null` and `employmentType` is `""` for Greenhouse jobs in v0.1. Setting
  `employmentTypeKeywords` therefore excludes every Greenhouse job.
- **Greenhouse EU-hosted boards** (`job-boards.eu.greenhouse.io`) are not supported yet.
- **Lever and Ashby:** their public APIs have no company display name, so `companyName` is
  the slug (e.g. `leverdemo`).
- Only the three ATSs above. Workday, SmartRecruiters, iCIMS and others are not supported.
- Only **public job-board APIs** are read — the same data shown on each company's careers
  page. No login, no candidate data, no personal data.
- You supply the company list. The Actor does not discover companies for you.

### Tips

- **Set `maxItems` as your cost cap.** Large companies can list thousands of jobs; a cap
  keeps a run's cost predictable.
- **Daily syncs:** schedule the Actor with `postedWithinDays: 1` (or 2 for some overlap) and
  dedupe on `id` to pick up only new postings.
- Turn `includeDescription` off when you only need listings — the output is much smaller.
- Check the run log: it prints, per company, how many jobs were fetched and emitted
  (`fetched N, emitted M`), and names any company that failed.

### FAQ

**How do I find a company's slug?**
Open its careers page and look for a link to `boards.greenhouse.io`, `job-boards.greenhouse.io`,
`jobs.lever.co` or `jobs.ashbyhq.com`. Paste that URL as is, or take the part after the host.

**Why did a company return no jobs?**
Either the board has no open postings, your filters removed them (check the log's fetched vs.
emitted counts), or the slug is wrong — then the log names the company and the error.

**Is there an official API to get all jobs from Greenhouse, Lever or Ashby?**
Each ATS has a public job-board API per company, but each returns a different format.
This Actor calls those official public APIs and converts all three into one schema, so you
don't maintain three integrations.

**Is this scraping allowed?**
It reads only the public job-board APIs that power each company's own careers page — no
login, no candidate data, no personal data. Check that your use of the data fits your own
legal requirements.

**Can I run it every day?**
Yes. Use Apify Schedules, set `postedWithinDays: 1`, and dedupe on `id`. You can send the
results to Google Sheets, Slack, Make, Zapier, n8n or a webhook with Apify integrations.

**Can I get the data through an API?**
Yes. Run the Actor through the Apify API and read the dataset as JSON, CSV or Excel. Every
job has the same fields whatever the source ATS.

# Actor input Schema

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

One company job board per line. Use the form ats:slug (greenhouse:airbnb, lever:leverdemo, lever-eu:slug, ashby:ashby) or paste a job-board URL: boards.greenhouse.io/{slug}, job-boards.greenhouse.io/{slug}, jobs.lever.co/{slug}, jobs.eu.lever.co/{slug} or jobs.ashbyhq.com/{slug}. lever-eu: and jobs.eu.lever.co always use Lever's EU instance; plain Lever entries try the global instance and fall back to EU only when the board is not found. Greenhouse and Ashby slugs are case-insensitive; Lever slugs are case-sensitive. Duplicates are removed. A malformed entry stops the run before any job is fetched; a slug that does not exist only fails that company.

## `titleKeywords` (type: `array`):

Keep jobs whose title contains any of these words (case-insensitive substring, e.g. "engineer"). Leave empty to keep all titles.

## `excludeTitleKeywords` (type: `array`):

Drop jobs whose title contains any of these words (case-insensitive substring, e.g. "intern").

## `locationKeywords` (type: `array`):

Keep jobs whose location, any listed location, or country contains any of these words (case-insensitive substring, e.g. "remote", "berlin").

## `departmentKeywords` (type: `array`):

Keep jobs whose department or team contains any of these words (case-insensitive substring, e.g. "engineering").

## `employmentTypeKeywords` (type: `array`):

Keep jobs whose employment type, as the ATS writes it, contains any of these words (case-insensitive substring, e.g. "full"). Greenhouse's public API has no employment type, so setting this filter excludes every Greenhouse job.

## `remoteOnly` (type: `boolean`):

Keep only jobs the ATS marks as remote.

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

Keep only jobs published (or, if no publish date, updated) within this many days. Jobs with no date are dropped when this is set. 0 = no date filter. Use 1 for daily syncs.

## `includeDescription` (type: `boolean`):

Include the full job description as HTML and plain text. Turn off for smaller, faster output.

## `maxItems` (type: `integer`):

Stop after this many jobs have been saved. You pay per saved job, so this is your cost cap. 0 = no limit.

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

How many company boards to fetch at the same time (1-20).

## Actor input object example

```json
{
  "companies": [
    "greenhouse:airbnb",
    "lever:leverdemo",
    "ashby:ashby"
  ],
  "remoteOnly": false,
  "postedWithinDays": 0,
  "includeDescription": true,
  "maxItems": 0,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Every job saved by this run, in the normalized Job schema.

# 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": [
        "greenhouse:airbnb",
        "lever:leverdemo",
        "ashby:ashby"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("datatap/ats-jobs").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": [
        "greenhouse:airbnb",
        "lever:leverdemo",
        "ashby:ashby",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("datatap/ats-jobs").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": [
    "greenhouse:airbnb",
    "lever:leverdemo",
    "ashby:ashby"
  ]
}' |
apify call datatap/ats-jobs --silent --output-dataset

```

## MCP server setup

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

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/IWCHAQ6X2rN12yASP/builds/0L9gXCDaMu6U196My/openapi.json