# ATS jobs - Greenhouse, Lever, Ashby, Workable (public APIs) (`retrainmap/ats-jobs`) Actor

Job postings from any company's public Greenhouse, Lever, Ashby or Workable board, read from the ATS's own keyless JSON endpoint and normalised to one row per job: title, department, location, remote flag, type, dates, URL, description, salary when published. Filter by keyword and location.

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

## Pricing

from $5.00 / 1,000 records

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## ATS job boards — Greenhouse, Lever, Ashby, Workable (public APIs)

One row per job posting from any company's **public** job board on the four most common
applicant-tracking systems, read from each ATS's own keyless JSON endpoint (the same data the
company's careers page renders) and normalised to one flat schema: ATS, company, job id, title,
department, team, location(s), remote flag, employment type, posted/updated dates, absolute job
URL, description text (first 3,000 characters), salary range when the company publishes one.
Give any number of board tokens per ATS; filter by keyword, location or remote.

**The default input (Stripe + Airbnb on Greenhouse, Spotify on Lever, Ramp on Ashby, Netguru on
Workable, 200 rows) succeeds within 5 minutes and returns rows** — Apify auto-tests it daily.

### Data sources and status

| ATS | Endpoint (no key) | Fields the row keeps |
|---|---|---|
| Greenhouse | `boards-api.greenhouse.io/v1/boards/<token>/jobs?content=true&pay_transparency=true` — Job Board API, documented at https://developers.greenhouse.io/job-board.html | id, title, departments, location, offices, first\_published, updated\_at, absolute\_url, content, pay\_input\_ranges, "Workplace Type" metadata |
| Lever | `api.lever.co/v0/postings/<site>?mode=json` — Postings API, documented at https://github.com/lever/postings-api | id, text, categories (department, team, location, allLocations, commitment), workplaceType, country, createdAt, hostedUrl, applyUrl, descriptionPlain, salaryRange |
| Ashby | `api.ashbyhq.com/posting-api/job-board/<name>?includeCompensation=true` — Job Posting API, documented at https://developers.ashbyhq.com/reference/jobpostingapi | id, title, department, team, employmentType, location, secondaryLocations, address, publishedAt, isRemote, workplaceType, jobUrl, applyUrl, descriptionPlain, compensation |
| Workable | `apply.workable.com/api/v1/widget/accounts/<subdomain>` (list) + `apply.workable.com/api/v2/accounts/<subdomain>/jobs/<shortcode>` (per-job detail) — the embeddable careers widget feeds | title, shortcode, department, employment\_type, telecommuting, city/state/country, locations, published\_on, url, application\_url; detail: description, requirements, benefits, workplace, remote |

The board token is the slug in the public URL: `boards.greenhouse.io/<token>`,
`jobs.lever.co/<site>`, `jobs.ashbyhq.com/<name>`, `apply.workable.com/<subdomain>`. Companies
move between ATSs — an unknown token answers HTTP 404, is **skipped and listed** in the run's
status message and `RUN_SUMMARY`; the run fails only when every board failed.

Honesty notes:

- Rows are the ATS's own fields renamed. **`remote` is the ATS's flag** where one exists
  (Lever `workplaceType`, Ashby `isRemote`, Workable `telecommuting`/`workplace`); Greenhouse has
  no flag, so it is inferred from a "Workplace Type" metadata field or the word *remote* in the
  location. `remote_source` on every row says which (`ats_flag`, `location_text`, `none`).
- Salary fields are filled only when the ATS publishes them (Greenhouse `pay_input_ranges` —
  first range, `salary_note` counts the rest; Ashby `Salary` compensation component; Lever
  `salaryRange`). Workable publishes none. Nothing is parsed out of description text.
- `description` is the posting text with HTML stripped, cut at 3,000 characters (` ...`).
- Layout changes (a board answer without the documented shape, a job without an id/title) stop
  the run with an error rather than guess.

Terms: these endpoints are the public, unauthenticated feeds each ATS provides for companies'
careers pages; the postings are the employers' own public content. Use the rows for search,
alerts and analysis; link back to `url` for the full posting and to apply. Requests carry a
product-token User-Agent and the operator contact in the `From:` header; at most one request
per 500 ms by default.

### Input

| Field | Type | Meaning |
|---|---|---|
| `greenhouse`, `lever`, `ashby`, `workable` | arrays of slugs | Board tokens per ATS; at least one in total |
| `keyword` | string | Optional substring on title/department/team/description (case-insensitive) |
| `location` | string | Optional substring on location(s) and country |
| `remote_only` | boolean | Keep only `remote == true` |
| `max_records` | integer | Default 200; rows are interleaved across boards (round-robin) |
| `workable_details` | boolean | Default on: one extra request per Workable job for the description |
| `request_interval_ms` | integer | Default 500 (floor 250) |
| `contact_email` | string | Sent in the `From:` header |

Example — remote engineering roles at Figma (Greenhouse), Veeva (Lever) and Ramp (Ashby):

```json
{ "greenhouse": ["figma"], "lever": ["veeva"], "ashby": ["ramp"], "keyword": "engineer", "remote_only": true, "max_records": 100 }
```

### Output (dataset row)

`ats`, `board`, `company`, `job_id`, `title`, `department`, `team`, `location`, `all_locations`,
`country`, `remote`, `remote_source`, `workplace_type`, `employment_type`, `posted_at`,
`updated_at`, `url`, `apply_url`, `description`, `salary_min`, `salary_max`, `salary_currency`,
`salary_interval`, `salary_note`, `source_url`, `fetched_at`.

A run summary (per-board job counts, matches, skipped boards with the reason, requests, whether
the pay-per-event budget stopped the run) is stored as `RUN_SUMMARY` in the run's key-value store.

### Pricing (pay per event)

| Event | Price |
|---|---|
| `run-start` — once per run | $0.10 |
| `record` — per row written | $0.005 |

The default pull (200 rows) costs $1.10; 1,000 jobs cost $5.10. Rows stop when your run's
maximum charge is reached; the run summary says so.

### Operator

Steelyard Ventures LLC (RetrainMap) — info@steelyardclinical.com. Not affiliated with
Greenhouse, Lever, Ashby, Workable or any listed employer. The Actor writes only to its own
dataset and key-value store; it stores no credentials and sends nothing else.

# Actor input Schema

## `greenhouse` (type: `array`):

Slugs from boards.greenhouse.io/<token> (or the gh\_jid links on the company site). Read from boards-api.greenhouse.io/v1/boards/<token>/jobs?content=true\&pay\_transparency=true.

## `lever` (type: `array`):

Slugs from jobs.lever.co/<site>. Read from api.lever.co/v0/postings/<site>?mode=json. An unknown site answers 404 and is skipped (listed in the run summary).

## `ashby` (type: `array`):

Slugs from jobs.ashbyhq.com/<name>. Read from api.ashbyhq.com/posting-api/job-board/<name>?includeCompensation=true.

## `workable` (type: `array`):

Slugs from apply.workable.com/<subdomain>. Read from apply.workable.com/api/v1/widget/accounts/<subdomain>; the description comes from one extra request per job (see workable\_details).

## `keyword` (type: `string`):

Optional, case-insensitive substring matched against title, department, team and description (e.g. 'data engineer', 'nurse'). Empty = every job.

## `location` (type: `string`):

Optional, case-insensitive substring matched against the job's location(s) and country (e.g. 'london', 'remote', 'US').

## `remote_only` (type: `boolean`):

Keep only jobs whose `remote` flag is true (the ATS's own flag, or inferred from the location text for Greenhouse - see `remote_source`).

## `max_records` (type: `integer`):

Stop after this many job rows. Rows are interleaved across boards (round-robin) so every board is represented.

## `workable_details` (type: `boolean`):

Workable's list endpoint has no description; when on, one extra request per Workable job fills description, workplace type and remote flag (default on).

## `request_interval_ms` (type: `integer`):

Politeness delay towards the ATS hosts. One request per board (plus one per Workable job); the floor is 250 ms.

## `contact_email` (type: `string`):

Sent in the standard From: request header so the data owner can reach the operator (RFC 9110 s10.1.2).

## Actor input object example

```json
{
  "greenhouse": [
    "stripe",
    "airbnb"
  ],
  "lever": [
    "spotify"
  ],
  "ashby": [
    "ramp"
  ],
  "workable": [
    "netguru"
  ],
  "remote_only": false,
  "max_records": 200,
  "workable_details": true,
  "request_interval_ms": 500,
  "contact_email": "info@steelyardclinical.com"
}
```

# Actor output Schema

## `results` (type: `string`):

One row per job posting: ATS, company, title, department, team, location, remote flag, type, dates, URL, description, salary when published.

## `results_csv` (type: `string`):

The same rows as a CSV file.

# 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 = {
    "greenhouse": [
        "stripe",
        "airbnb"
    ],
    "lever": [
        "spotify"
    ],
    "ashby": [
        "ramp"
    ],
    "workable": [
        "netguru"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("retrainmap/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 = {
    "greenhouse": [
        "stripe",
        "airbnb",
    ],
    "lever": ["spotify"],
    "ashby": ["ramp"],
    "workable": ["netguru"],
}

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,retrainmap/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/fPnueVb8skakouKju/builds/hJa2YRUekyIMd9S0l/openapi.json