# ATS Job Board Scraper — Greenhouse (`chain_link/ats-job-board-api-scraper`) Actor

Pull every open job from company career sites on Greenhouse, Lever and Ashby using their official public job board APIs. Give company slugs or board URLs and get normalized jobs with full descriptions, departments, remote flag and salary ranges where published.

- **URL**: https://apify.com/chain_link/ats-job-board-api-scraper.md
- **Developed by:** [James White](https://apify.com/chain_link) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.40 / 1,000 job scrapeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Job Board Scraper — Greenhouse, Lever and Ashby

Get every open job from company career sites hosted on **Greenhouse**, **Lever** and **Ashby**. You give it company names (board slugs) or career board links. It returns one clean, consistent list of jobs: title, location, department, employment type, remote flag, published dates, full description and salary range where the company publishes one.

The tool reads only the official public job board APIs that these three vendors provide for showing open roles. It does not use a browser and does not parse web pages, so runs are fast and predictable.

### Price

**$0.002 per job saved** ($2 per 1,000 jobs). You pay only for jobs that pass your filters. Jobs removed by the keyword, location or remote filters are never saved and never charged.

### Typical uses

- Track hiring at competitors, customers or portfolio companies
- Build job boards or newsletters for a niche, such as remote engineering roles
- Collect salary ranges for compensation benchmarking (Ashby and Lever boards that publish them)
- Sales prospecting: spot companies hiring for roles that signal a need for your product
- Labour market research across many companies at once

### Inputs

| Field | What it does | Default |
|---|---|---|
| **Companies (slugs or board URLs)** (`companies`) | Required. A list of company board names, such as `stripe`, or board links such as `https://job-boards.greenhouse.io/stripe`, `https://jobs.lever.co/palantir` or `https://jobs.ashbyhq.com/ramp`. Links to the vendors' API addresses also work. You can mix slugs and links. | `["stripe"]` |
| **ATS provider** (`ats`) | Which system to check for plain slugs: `auto`, `greenhouse`, `lever` or `ashby`. With `auto`, the tool tries Greenhouse, then Lever, then Ashby, and uses the first one that has open jobs for that slug. Links are always recognised automatically. | `auto` |
| **Title keywords** (`keywords`) | Keep only jobs whose title contains at least one of these words. Case does not matter. Leave empty to keep every job. | empty |
| **Location contains** (`locationFilter`) | Keep only jobs whose location text contains this text, for example `London` or `Remote`. Case does not matter. Secondary locations and office names are checked too. | empty |
| **Remote jobs only** (`remoteOnly`) | Keep only jobs marked remote by the ATS, or whose location mentions remote. | `false` |
| **Include full description** (`includeDescription`) | Add the full job description as HTML and as plain text. Turn it off for smaller results. | `true` |
| **Max jobs** (`maxItems`) | The most jobs to save across all companies. `0` means no limit. The run stops as soon as this number is reached. | `100` |

#### Example input

```json
{
  "companies": [
    "stripe",
    "https://jobs.lever.co/palantir",
    "https://jobs.ashbyhq.com/ramp"
  ],
  "ats": "auto",
  "keywords": ["engineer", "security"],
  "locationFilter": "",
  "remoteOnly": false,
  "includeDescription": true,
  "maxItems": 100
}
```

### Output

Each job is one row with the same fields, whichever ATS it came from. Fields with no published value are `null`.

| Field | Description |
|---|---|
| `jobId` | The job posting ID used by the ATS |
| `title` | Job title |
| `company` | Company board slug the job came from |
| `ats` | `greenhouse`, `lever` or `ashby` |
| `jobUrl` | Public link to the job posting |
| `applyUrl` | Application link, when it differs from `jobUrl` (Lever and Ashby) |
| `location` | Main location, as published |
| `department` | Department or team |
| `employmentType` | For example Full-time or Part-time, when published |
| `isRemote` | `true` if the ATS marks the job as remote or the location mentions remote |
| `salaryMin` / `salaryMax` | Published salary range, when available |
| `salaryCurrency` | Currency code, such as USD |
| `salaryInterval` | Pay period, such as `per-year` or `per-hour` |
| `descriptionHtml` | Full description as HTML (if descriptions are on) |
| `descriptionText` | Full description as plain text (if descriptions are on) |
| `publishedAt` | When the job was first published or created (ISO date-time) |
| `updatedAt` | When the job was last updated, if the ATS provides it |
| `scrapedAt` | When this row was collected |

#### Example row

```json
{
  "jobId": "34413f8d-26bf-4bbc-8ade-eb309a0e2245",
  "title": "Security Engineer, Cloud",
  "company": "ramp",
  "ats": "ashby",
  "jobUrl": "https://jobs.ashbyhq.com/ramp/34413f8d-26bf-4bbc-8ade-eb309a0e2245",
  "applyUrl": "https://jobs.ashbyhq.com/ramp/34413f8d-26bf-4bbc-8ade-eb309a0e2245/application",
  "location": "New York, NY (HQ)",
  "department": "Engineering",
  "employmentType": "Full-time",
  "isRemote": true,
  "salaryMin": 211400,
  "salaryMax": 290600,
  "salaryCurrency": "USD",
  "salaryInterval": "per-year",
  "descriptionHtml": "<h1><strong>About Ramp</strong></h1><p>Ramp is building the smart infrastructure for finance teams...</p>",
  "descriptionText": "ABOUT RAMP Ramp is building the smart infrastructure for finance teams... (shortened)",
  "publishedAt": "2026-04-07T17:12:35.753+00:00",
  "updatedAt": null,
  "scrapedAt": "2026-10-15T09:30:00.000000+00:00"
}
```

### Limits and good to know

- **Salary ranges** come from Ashby compensation data and the Lever salary range field, and only when the company publishes them. Greenhouse's job list does not include structured salary, so salary fields are empty for Greenhouse jobs.
- **Updated dates** are provided by Greenhouse. Lever and Ashby often leave them out.
- **Only public, listed jobs** are returned. Internal or unlisted postings are not available.
- **Auto-detection**: if the same slug exists on more than one ATS, the first one with open jobs is used (Greenhouse, then Lever, then Ashby). Set `ats` or use a board link to pick one explicitly.
- **Company websites** (for example a company's own careers page on its own domain) are not supported. You need the company's Greenhouse, Lever or Ashby board slug or link, which is usually visible in the job application link.
- Lever boards in the EU region (`jobs.eu.lever.co`) are supported when you give the board link.
- If an API refuses access (HTTP 403) or keeps rate-limiting (HTTP 429) after a few polite retries, the run stops and logs the reason. Jobs saved before that point remain in your dataset.
- Descriptions are returned as the company wrote them. Text formatting can vary between companies.

### Terms

This tool reads job postings that companies publish openly through their ATS vendor's public job board API. It does not collect recruiter or hiring-manager details as separate fields. You are responsible for using the data in line with applicable laws and with the terms of the companies and vendors involved. Please respect the original postings, for example by linking back to `jobUrl` when you republish jobs.

# Actor input Schema

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

Company board tokens (e.g. 'stripe') or career board URLs such as https://job-boards.greenhouse.io/stripe, https://jobs.lever.co/palantir or https://jobs.ashbyhq.com/ramp.

## `ats` (type: `string`):

Which ATS to query for bare slugs: 'auto' (try Greenhouse, Lever, then Ashby), 'greenhouse', 'lever' or 'ashby'. URLs are detected automatically.

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

Only return jobs whose title contains any of these keywords (case-insensitive). Leave empty for all jobs.

## `locationFilter` (type: `string`):

Only return jobs whose location text contains this string (case-insensitive), e.g. 'London' or 'Remote'.

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

Return only jobs flagged or described as remote.

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

Include the full job description as HTML and plain text.

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

Maximum number of jobs to return across all companies (0 = no limit).

## Actor input object example

```json
{
  "companies": [
    "stripe"
  ],
  "ats": "auto",
  "keywords": [],
  "includeDescription": true,
  "maxItems": 100
}
```

# Actor output Schema

## `results` (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": [
        "stripe"
    ],
    "ats": "auto",
    "keywords": [],
    "locationFilter": "",
    "remoteOnly": false,
    "includeDescription": true,
    "maxItems": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("chain_link/ats-job-board-api-scraper").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": ["stripe"],
    "ats": "auto",
    "keywords": [],
    "locationFilter": "",
    "remoteOnly": False,
    "includeDescription": True,
    "maxItems": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("chain_link/ats-job-board-api-scraper").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": [
    "stripe"
  ],
  "ats": "auto",
  "keywords": [],
  "locationFilter": "",
  "remoteOnly": false,
  "includeDescription": true,
  "maxItems": 100
}' |
apify call chain_link/ats-job-board-api-scraper --silent --output-dataset

```

## MCP server setup

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

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/SggYYSNeG69Khpnga/builds/WhbUEmrvD5APYyLhd/openapi.json