# Greenhouse Jobs Scraper — Any Company Board | $1/1K (`steadyrow/greenhouse-jobs`) Actor

Scrape every open job from any Greenhouse job board: paste a boards.greenhouse.io URL, a board name or a careers page. Official public API, no proxy. Salary ranges, filters by keyword, location, department, and a monitor mode that returns only new jobs.

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

## Pricing

from $1.00 / 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 Jobs Scraper — Any Company Board | $1/1K

**Paste a Greenhouse job board, get every open job as clean JSON. $1 per 1,000 jobs.**

Greenhouse powers the careers pages of thousands of tech companies (for example Stripe, Airbnb and Figma). This Actor reads a company's **official public Greenhouse Job Board API** — the same JSON feed the careers page uses — and returns every posting with title, department, all locations, pay range, full description and apply link.

- ✅ **Any Greenhouse board** — `boards.greenhouse.io/<company>`, `job-boards.greenhouse.io/<company>`, EU boards (`job-boards.eu.greenhouse.io`), or just the board token (`stripe`)
- ✅ **Pay ranges** — reads Greenhouse's structured pay-transparency data and, when absent, parses the range from the description
- ✅ **Monitor mode** — schedule it daily and only pay for jobs you have not received before
- ✅ **No browser, no proxy, no login** — plain HTTPS requests to the public API, so it is fast and stable
- ✅ **Filters** — keywords, excluded words, location, remote, department, posted within N days
- ✅ **No personal data** — no recruiter names or contacts; e-mail addresses inside descriptions are removed

> Need Lever, Ashby, Workday and SmartRecruiters in the same run? Use the combined [ATS Jobs API](https://apify.com/steadyrow/ats-jobs). This Actor is the Greenhouse-only version with inputs built for Greenhouse.

### What can I use it for?

- **Job boards and aggregators** — pull all Greenhouse companies you track into one feed
- **Job alerts** — daily monitor run → Slack, e-mail or Google Sheets with only the new roles
- **Hiring signals for sales and recruiting** — which departments a company is growing, and where
- **Salary research** — pay ranges by role, location and company
- **AI agents** — a typed job feed your agent can call through the Apify API or MCP

### Input

```json
{
    "boards": [
        "https://job-boards.greenhouse.io/figma",
        "stripe",
        "greenhouse:airbnb"
    ],
    "keywords": ["engineer", "data"],
    "excludeKeywords": ["intern"],
    "locations": ["United States", "Remote"],
    "departments": ["Engineering"],
    "postedWithinDays": 30,
    "maxItemsPerSource": 200,
    "monitorMode": false
}
```

| Field | What it does |
|---|---|
| `boards` | **Required.** One per line: a board URL, a board token (`stripe` or `greenhouse:stripe`), a job URL (the whole board is scraped) or a company careers page that embeds a Greenhouse board. Entries that belong to another ATS are skipped with a note in the log. |
| `keywords` | Keep jobs whose **title** contains any of these words (whole word, case-insensitive). Turn on `searchInDescription` to search the description too. |
| `excludeKeywords` | Drop jobs whose title contains any of these words. |
| `locations` | Keep jobs whose location or country contains one of these words. `remote` matches remote jobs. |
| `departments` | Keep jobs whose Greenhouse department contains one of these strings. |
| `postedWithinDays` | Only jobs first published in the last N days. |
| `maxItemsPerSource` / `maxItems` | Limits per board / per run (0 = no limit). |
| `fetchGreenhouseSalary` | Greenhouse publishes structured pay ranges only on each job's own endpoint. When on (default), one extra request is made per job that has no range in its text. Turn off for faster runs on big boards. |
| `includeDescription`, `includeDescriptionHtml` | Plain-text and/or HTML description. |
| `monitorMode`, `monitorStateName` | Output only jobs not delivered before; name of the store that remembers them. |

#### Finding a board token

Open the company's careers page and look at the address of a job: `https://boards.greenhouse.io/<token>/jobs/123` or `https://job-boards.greenhouse.io/<token>/jobs/123`. The `<token>` is what you need. If you only have the company's own careers page, paste that — the Actor looks for an embedded Greenhouse board (some company sites block automated requests; then paste the board URL instead).

### Output

One item per job:

```json
{
    "job_id": "greenhouse:figma:5426468004",
    "ats": "greenhouse",
    "company": "Figma",
    "company_board_id": "figma",
    "title": "Account Executive, Enterprise",
    "department": "Sales",
    "team": null,
    "location": "San Francisco, CA • New York, NY • United States",
    "locations": ["San Francisco, CA • New York, NY • United States"],
    "country": null,
    "remote": false,
    "workplace_type": null,
    "employment_type": null,
    "posted_at": "2025-01-28T23:57:29.000Z",
    "updated_at": "2026-07-22T09:37:08.000Z",
    "salary_min": 165000,
    "salary_max": 190000,
    "salary_currency": "USD",
    "salary_period": "YEAR",
    "salary_source": "description",
    "description_text": "Figma is growing our team of passionate creatives and builders…",
    "apply_url": "https://boards.greenhouse.io/figma/jobs/5426468004?gh_jid=5426468004",
    "source_url": "https://boards.greenhouse.io/figma/jobs/5426468004?gh_jid=5426468004",
    "input": "https://job-boards.greenhouse.io/figma",
    "scraped_at": "2026-10-20T16:53:02.740Z"
}
```

Greenhouse-specific notes:

- `job_id` is `greenhouse:<board>:<id>` and stays the same between runs.
- Greenhouse does not publish `team`, `employment_type` or `country`, so those are `null`. `workplace_type` is only set when the posting says remote / hybrid / onsite.
- `posted_at` is Greenhouse's first-published date; `updated_at` is the last update.
- `salary_source` is `ats` for Greenhouse's structured pay range and `description` for a range parsed from the text; all salary fields are `null` when the posting shows none.
- A run summary (per board: listed / output / errors) is saved as `SUMMARY` in the default key-value store. An unknown board is reported there and in the log; the other boards still run.

### Monitor mode: only new jobs

1. Turn on **Monitor mode** and save the input as a task.
2. Add a schedule (for example every morning).
3. The first run returns all matching jobs. Every later run returns only jobs not delivered before — and you pay only for those.

Delivered IDs are kept per board in the named key-value store `greenhouse-jobs-monitor` (change it with `monitorStateName` if you run several independent monitors). In our tests a second run on the same boards returned 0 jobs, and after forgetting 6 jobs a third run returned exactly those 6.

### Pricing

Pay per event:

| Event | Price |
|---|---|
| Job in the dataset | **$0.001** ($1 per 1,000 jobs) |
| Actor start | $0.002 per run |

Examples: 1,000 jobs ≈ $1. A daily monitor on 20 boards that finds 30 new jobs ≈ $0.03 + $0.002 per day. Jobs removed by your filters or already delivered in monitor mode are not charged. Set **Maximum cost per run** and the Actor stops cleanly at the limit.

### FAQ

**How many jobs can it get?** All of a board. In our tests Stripe listed 730 open jobs, Airbnb 182 and Figma 142.

**Is it legal?** The Actor reads public job postings through Greenhouse's public Job Board API, without logging in and without bypassing any protection. No recruiter or candidate data is collected. You are responsible for how you use the data.

**Why are some `salary_*` fields empty?** Only postings that publish a pay range (required in several US states and countries) have one.

**A board returns an error.** The token is probably wrong or the company has left Greenhouse. Open `https://boards.greenhouse.io/<token>` in a browser to check.

# Actor input Schema

## `boards` (type: `array`):

One per line. Paste a board URL (https://boards.greenhouse.io/airbnb, https://job-boards.greenhouse.io/figma, https://job-boards.eu.greenhouse.io/<company>), a board token (`stripe` or `greenhouse:stripe`), a job URL (the whole board is scraped), or a company careers page that embeds a Greenhouse board.

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

Keep jobs whose title contains at least one of these words (whole-word, case-insensitive). Leave empty to keep all.

## `searchInDescription` (type: `boolean`):

By default keywords are matched against the job title only.

## `excludeKeywords` (type: `array`):

Drop jobs whose title contains any of these words (e.g. Senior, Intern).

## `locations` (type: `array`):

Keep jobs whose location, any of their locations, or country contains one of these words (whole-word, case-insensitive; e.g. London, Germany, US). Use `remote` to match remote jobs.

## `remote` (type: `string`):

Filter by remote eligibility.

## `departments` (type: `array`):

Keep jobs whose Greenhouse department contains one of these strings (e.g. Engineering).

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

Only jobs posted in the last N days. 0 = no limit.

## `maxItemsPerSource` (type: `integer`):

Stop after this many jobs from one board. 0 = all jobs.

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

Stop the whole run after this many jobs. 0 = no limit.

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

Adds `description_text` (the full job text as plain text).

## `includeDescriptionHtml` (type: `boolean`):

Adds `description_html` (cleaned original HTML).

## `fetchGreenhouseSalary` (type: `boolean`):

Greenhouse publishes pay-transparency ranges only on each job's own endpoint. When on, we make one extra request per Greenhouse job that has no salary in its description. Turn off for faster runs on very large boards.

## `monitorMode` (type: `boolean`):

Remembers every job already delivered (per board) and outputs only jobs you have not received before. The first run outputs all matching jobs. Ideal for a daily schedule — you only pay for new jobs.

## `monitorStateName` (type: `string`):

Name of the key-value store that keeps the list of delivered jobs. Use a different name per task if you run several independent monitors.

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

Detail requests run in parallel up to this number. Requests to one ATS host are additionally limited to about 4 per second.

## Actor input object example

```json
{
  "boards": [
    "https://job-boards.greenhouse.io/figma",
    "stripe"
  ],
  "searchInDescription": false,
  "remote": "any",
  "postedWithinDays": 0,
  "maxItemsPerSource": 20,
  "maxItems": 0,
  "includeDescription": true,
  "includeDescriptionHtml": false,
  "fetchGreenhouseSalary": true,
  "monitorMode": false,
  "monitorStateName": "greenhouse-jobs-monitor",
  "maxConcurrency": 4
}
```

# Actor output Schema

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

All Greenhouse job postings collected in this run, one row per job.

# 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 = {
    "boards": [
        "https://job-boards.greenhouse.io/figma",
        "stripe"
    ],
    "maxItemsPerSource": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("steadyrow/greenhouse-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 = {
    "boards": [
        "https://job-boards.greenhouse.io/figma",
        "stripe",
    ],
    "maxItemsPerSource": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("steadyrow/greenhouse-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 '{
  "boards": [
    "https://job-boards.greenhouse.io/figma",
    "stripe"
  ],
  "maxItemsPerSource": 20
}' |
apify call steadyrow/greenhouse-jobs --silent --output-dataset

```

## MCP server setup

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