# Greenhouse, Lever, Ashby & Workable Scraper (`bibian/multi-ats-jobs-scraper`) Actor

Extract job postings from company career pages hosted on Greenhouse, Lever, Ashby or Workable in one run: title, department, location, remote policy, employment type and full description.

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

## Pricing

from $1.20 / 1,000 job postings

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 & Workable Scraper

Extract job postings from company career pages hosted on [Greenhouse](https://www.greenhouse.io), [Lever](https://www.lever.co), [Ashby](https://www.ashbyhq.com) or [Workable](https://www.workable.com) in a single run, and get clean structured data: title, department, location, remote policy, employment type and full description — no browser, no login, across all four ATS at once.

### What you can do with it

- **Monitor several companies' hiring at once**, whatever ATS each one happens to use, from one run instead of four separate tools.
- **Feed a job alert or an aggregator**: run it daily and dedupe against your own store by `id`.
- **Track a sector's hiring**: list every open role for a group of companies you follow.
- **Benchmark remote policy and employment types** across companies and platforms.

### Input

| Field | What it does |
|---|---|
| Greenhouse boards | Board tokens, for example `airbnb` from `boards.greenhouse.io/airbnb`. |
| Lever boards | Company slugs, for example `palantir` from `jobs.lever.co/palantir`. |
| Ashby boards | Job board names, for example `ramp` from `jobs.ashbyhq.com/ramp`. |
| Workable boards | Account shortcodes, for example `huggingface` from `apply.workable.com/huggingface`. |
| Maximum number of postings | The run stops once this many postings are saved, across all boards combined. |
| Include full descriptions | Adds the full job description as plain text. |

Leave every board list empty to run a small default set spanning all four platforms.

### Output

One record per posting:

```json
{
  "id": "greenhouse:webflow:8360279",
  "platform": "greenhouse",
  "company": "webflow",
  "title": "Account Executive, EMEA",
  "department": "Sales",
  "location": "London, United Kingdom",
  "remote": null,
  "employmentType": null,
  "publishedAt": "2026-09-18T09:00:00-07:00",
  "updatedAt": "2026-09-30T12:00:00-07:00",
  "url": "https://job-boards.greenhouse.io/webflow/jobs/8360279",
  "description": "…"
}
```

Export the dataset as JSON, CSV or Excel, or read it through the Apify API.

### Why this one

- **One run, four ATS.** Most scrapers on the Store cover a single platform; this one normalizes Greenhouse, Lever, Ashby and Workable into the same schema.
- **No login, no browser.** Every platform publishes a public job board API; this Actor only reads it.
- **Unknown board slugs don't fail the run.** A typo in one company's slug logs a warning and the others still come through.

### Good to know

- `remote` is read from each platform's own field (Lever's `workplaceType`, Ashby's `isRemote`, Workable's `telecommuting`) where available. Greenhouse does not expose it in a consistent way across companies, so it is always `null` there — this is not a bug, it reflects what Greenhouse publishes.
- `updatedAt` is only published by Greenhouse; it is `null` on the other three platforms.
- A board slug that does not exist on its platform is skipped with a warning in the log, not a failure.
- No browser and no proxy needed: runs are fast and cheap.
- The dataset contains job postings only: the hiring company is named, never an individual recruiter or candidate.

# Actor input Schema

## `greenhouseBoards` (type: `array`):

Greenhouse board tokens, taken from a company's career page URL, for example "airbnb" from boards.greenhouse.io/airbnb. Leave every board list empty to run a default set across all four platforms.

## `leverBoards` (type: `array`):

Lever company slugs, taken from a company's career page URL, for example "palantir" from jobs.lever.co/palantir.

## `ashbyBoards` (type: `array`):

Ashby job board names, taken from a company's career page URL, for example "ramp" from jobs.ashbyhq.com/ramp.

## `workableBoards` (type: `array`):

Workable account shortcodes, taken from a company's career page URL, for example "huggingface" from apply.workable.com/huggingface.

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

The run stops once this many postings are saved, across all boards combined.

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

Add the full job description as plain text.

## Actor input object example

```json
{
  "maxItems": 300,
  "includeDescriptions": true
}
```

# Actor output Schema

## `postings` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("bibian/multi-ats-jobs-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("bibian/multi-ats-jobs-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 '{}' |
apify call bibian/multi-ats-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bibian/multi-ats-jobs-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/0sOdrXsPCJ7uZsp7V/builds/PFD3S0cXytYzpJlfr/openapi.json