# Greenhouse, Lever & Ashby Job Boards Scraper (`literate_universe/ats-job-boards-scraper`) Actor

Pull every open job from company career pages hosted on Greenhouse, Lever or Ashby. Give it company slugs (or let it auto-detect the ATS), filter by keyword, location or department, and get clean job rows with apply links. Public APIs, no login.

- **URL**: https://apify.com/literate\_universe/ats-job-boards-scraper.md
- **Developed by:** [John Rutherford](https://apify.com/literate_universe) (community)
- **Stats:** 2 total users, 1 monthly users, 80.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 job rows

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

## Greenhouse, Lever & Ashby Job Boards Scraper

Pull **every open job from company career pages** hosted on **Greenhouse, Lever or Ashby**, the three ATS platforms behind most startup and tech hiring. Give it company slugs, or just names and let it detect the ATS, and get clean job rows with apply links. Public APIs, no login, no browser.

For recruiters, job-board builders, sales teams tracking who is hiring, researchers and job seekers who want a personal feed.

### What you get

One row per open job:

| Field | Meaning |
|---|---|
| `company`, `ats` | Board slug and which ATS served it |
| `title`, `department`, `team`, `location`, `remote`, `employment_type` | The role |
| `published_at`, `updated_at` | Timestamps where the ATS provides them |
| `job_id`, `url` | Stable id and the apply link |
| `description` | Plain-text description when **Include job description** is on |
| `compensation` | Ashby only, when the company publishes a range |

Sample row:

```json
{
  "company": "stripe",
  "ats": "greenhouse",
  "title": "Backend Engineer, Payments",
  "department": "Engineering",
  "location": "Remote, US",
  "updated_at": "2026-09-05T18:12:40-04:00",
  "url": "https://boards.greenhouse.io/stripe/jobs/6123456"
}
```

### Input

| Option | Default | What it does |
|---|---|---|
| **Companies** | | `greenhouse:stripe`, `lever:netflix`, `ashby:ramp`, or bare slugs to auto-detect |
| **Title keyword** | | Filter on title or department |
| **Location contains** | | e.g. Remote, London |
| **Department contains** | | e.g. Engineering |
| **Include job description** | off | Adds plain-text description |
| **Max jobs** | 5000 | Cap output |

Finding the slug: it is the last part of the careers URL. `boards.greenhouse.io/stripe` gives `stripe`; `jobs.lever.co/netflix` gives `netflix`; `jobs.ashbyhq.com/ramp` gives `ramp`.

### Pricing

Pay per event: one small charge per job row. Filters apply before charging.

### Notes and limits

- Companies not on one of these three platforms return "not found" in the run summary.
- Lever boards that are disabled return nothing.
- Schedule daily and diff `job_id` to get new-posting alerts.

# Actor input Schema

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

Company board slugs, optionally prefixed with the ATS: greenhouse:stripe, lever:netflix, ashby:ramp. Without a prefix the Actor tries Greenhouse, Lever then Ashby. The slug is the last part of the company's careers URL (boards.greenhouse.io/<slug>, jobs.lever.co/<slug>, jobs.ashbyhq.com/<slug>).

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

Keep only jobs whose title or department contains this text.

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

e.g. Remote, London, New York.

## `department` (type: `string`):

e.g. Engineering, Sales.

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

Adds the full description as plain text (larger output).

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

Stop after this many jobs.

## Actor input object example

```json
{
  "companies": [
    "greenhouse:stripe",
    "ashby:ramp"
  ],
  "includeDescription": false,
  "maxItems": 5000
}
```

# Actor output Schema

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

One row per open job. Append ?format=csv for CSV.

# 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:stripe",
        "ashby:ramp"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("literate_universe/ats-job-boards-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": [
        "greenhouse:stripe",
        "ashby:ramp",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("literate_universe/ats-job-boards-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": [
    "greenhouse:stripe",
    "ashby:ramp"
  ]
}' |
apify call literate_universe/ats-job-boards-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,literate_universe/ats-job-boards-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/88Uho4KODdTa3rHJu/builds/42smkKeKE2kd5jHWn/openapi.json