# Greenhouse Jobs API - Every Company's Board (`groundtruth/greenhouse-jobs-api`) Actor

Read any company's open jobs straight from its Greenhouse job board. 4,168 companies already mapped, salaries parsed into numbers, and a daily mode that returns only what is new.

- **URL**: https://apify.com/groundtruth/greenhouse-jobs-api.md
- **Developed by:** [Ground Truth](https://apify.com/groundtruth) (community)
- **Categories:** Jobs, AI, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 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?

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 Jobs API - Every Company's Board

Read any company's open jobs **straight from its Greenhouse job board**, with
salaries parsed into numbers and a mode that returns only what is new since
your last run.

On Greenhouse: Stripe, Anthropic, Airbnb, Cloudflare, Databricks, Figma, and 4,168 more.

```
company_search: "stripe"     -> finds the board, reads every open role
boards: ["https://boards.greenhouse.io/stripe", "stripe"]
```

### The directory: 4,168 companies

Greenhouse's job board API is open and documented, and **useless unless you
already know the company's board name**. Greenhouse publishes no directory of its
customers, and could not publish a useful one anyway.

So this Actor ships one: 4,168 boards, every one confirmed against
Greenhouse's own API, each carrying the date it was confirmed.

### Run it daily

| mode | returns |
|---|---|
| `all` | every open job |
| **`new`** | **only postings you have not been sent before** |

You are charged per job returned, so in `new` mode a quiet day costs you
nothing but the Actor start. That is what makes this affordable to run every
morning instead of once.

`first_seen` is on every record in `new` mode: the date this feed first saw
the posting. It is the one fact Greenhouse cannot give you, because it publishes
when a job was posted, not when you first heard of it.

### Why this rather than a scraper

Greenhouse publishes this API so that third parties can build job sites from its
customers' openings. There is no login, no bot protection, no cookies to keep
alive, and nothing that can be switched off because it was never sneaking in.
`SOURCES.md` records the evidence and the date it was checked.

Pay ranges come through in exact cents wherever the employer has pay transparency switched on.

### No personal data

Recruiter names and contact details are never mapped. Email addresses and
phone numbers are stripped out of job descriptions, because descriptions
genuinely carry them and a column of those is a marketing list.

### Looking across systems

This edition reads Greenhouse only. Companies are also on Ashby, Lever and
Workable, and **no single system can tell you about the others**. For one
schema across all of them, use
[Job Listings from Career Pages](https://apify.com/groundtruth/ats-job-listings).

# Actor input Schema

## `company_search` (type: `string`):

Find companies in the built-in directory of 4,168 Greenhouse job boards and read all of them. Try 'stripe', or a word several companies share. Leave empty if you are naming boards directly below.

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

One entry per company: a Greenhouse careers URL, or just the company's board name. Up to 500 per run.

## `mode` (type: `string`):

'all' returns every open job. 'new' returns only postings this feed has not sent you before, which is what makes a daily run cheap: a quiet day costs you nothing but the Actor start.

## `feed_id` (type: `string`):

Keeps separate schedules from interfering. Two pipelines using different feed names each get their own 'what I have already seen'. Letters, numbers, dashes and underscores.

## `max_boards` (type: `integer`):

Only applies to 'Search companies by name'. Caps how many matching boards are read.

## `limit` (type: `integer`):

Total jobs to return across every company. You are charged per job returned.

## `include_description` (type: `boolean`):

Off by default, because a description is most of a record's size and you are charged per record. Email addresses and phone numbers are removed from descriptions either way.

## Actor input object example

```json
{
  "company_search": "anthropic",
  "boards": [
    "https://boards.greenhouse.io/stripe"
  ],
  "mode": "all",
  "feed_id": "default",
  "max_boards": 25,
  "limit": 1000,
  "include_description": false
}
```

# Actor output Schema

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

No description

## `jobsCsv` (type: `string`):

No description

## `runDetails` (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 = {
    "boards": [
        "https://boards.greenhouse.io/stripe"
    ],
    "limit": 1000
};

// Run the Actor and wait for it to finish
const run = await client.actor("groundtruth/greenhouse-jobs-api").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://boards.greenhouse.io/stripe"],
    "limit": 1000,
}

# Run the Actor and wait for it to finish
run = client.actor("groundtruth/greenhouse-jobs-api").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://boards.greenhouse.io/stripe"
  ],
  "limit": 1000
}' |
apify call groundtruth/greenhouse-jobs-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,groundtruth/greenhouse-jobs-api"
        }
    }
}

```

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/2kNODCayYbtBDhwWL/builds/W00znTLr0lSCTzUMD/openapi.json