# Greenhouse Job Board Scraper (`usestring/greenhouse-jobs`) Actor

Collect every open job posting from any Greenhouse-hosted job board in one request.

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

## Pricing

from $1.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#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 Job Board Scraper — a whole board in one request

Collect every open job posting from any Greenhouse-hosted job board. Give this Actor a Greenhouse
board URL or a company board token, and it returns the whole board with title, company, department,
location, remote flag, posted date and apply URL.

Greenhouse publishes every board as JSON, so this Actor reads that board feed rather than the
rendered careers page. **One request returns an entire Greenhouse board** — a measured run collected
814 postings from 1.23 requests.

No Greenhouse account, login, API key or cookies are used. This Actor reads the public Greenhouse
board that a logged-out visitor sees.

### What it returns

| Field | Type | Notes |
| --- | --- | --- |
| `jobId` | string | Greenhouse's own posting ID — stable, use it to de-duplicate |
| `title` | string | |
| `company` | string | The company name Greenhouse publishes on the board |
| `tenant` | string | The Greenhouse board token, e.g. `databricks` |
| `location` | string | Exactly as the recruiter wrote it on the posting |
| `city`, `state`, `country` | string | Split out only when the location is unambiguously one place. `null` for a list or a qualifier such as `Dublin OR London` or `Remote - US`, where `location` still carries the original |
| `isRemote` | boolean | `true` when the location names remote or work from home |
| `department` | string | The Greenhouse department the posting is filed under; `null` when it is filed under none |
| `employmentType` | string | From the board's own metadata field where the company publishes one, e.g. `"Full-time"`; `null` otherwise |
| `postedAt` | string | ISO 8601 timestamp — the posting's `first_published`, falling back to `updated_at` |
| `jobUrl` | string | Direct link to the posting. Greenhouse may point this at the company's own careers page |
| `boardUrl` | string | The board a person would open, `https://job-boards.greenhouse.io/<tenant>` |
| `sourceUrl`, `collectedAt` | string | Provenance for every row |

### Input

```json
{ "boards": ["https://job-boards.greenhouse.io/databricks", "stripe"], "maxItems": 1000 }
```

| Field | Description |
| --- | --- |
| `boards` | Greenhouse board URLs or company board tokens. Required, 1–100. |
| `maxItems` | Cap on dataset items. Default 1000, maximum 50,000. Free plans stop at 250 requests and 250 results — see below. |
| `concurrency` | Boards fetched in parallel. Default 5, maximum 10. |

A board token, a board URL, a deep posting URL such as `/databricks/jobs/8559344002`, and an embedded
board URL carrying `?for=databricks` all resolve to the same Greenhouse board and are fetched once
rather than billed three times.

### Use cases

- Tracking which companies are hiring, and for which departments, across a watchlist of Greenhouse boards
- Competitor hiring signals — headcount direction by team, read from the board itself rather than an aggregator
- Filling an ATS, job board or talent CRM with live postings straight from the employer
- Recruiting lead lists by department, location or remote status
- Monitoring a board over time by re-running on a schedule and diffing on `jobId`

### Reliability

Greenhouse's board feed is structured JSON published by Greenhouse itself, so there is no markup
contract to break and no model in the path: a field is either present on the posting or absent.

An empty board is treated as a real result, not a failure — a company between hiring rounds
genuinely has no postings. An unknown board token is reported as a failure, because Greenhouse
answers it with `{"error":"Invalid Board Token"}`.

A board that cannot be read is recorded in the run's `SUMMARY` under `failures` rather than silently
returning fewer rows, and a run where every board failed exits with an error.

### Frequently asked questions

**How do I find a company's Greenhouse board URL?** A Greenhouse board lives at
`https://job-boards.greenhouse.io/<token>`, where the token is the company's own slug — `databricks`,
`stripe`. If the company embeds its board in its careers page, the token is the `for=` parameter on
the embedded board URL. You can pass the full URL or just the token.

**Do I need a Greenhouse account, API key or login?** No. This Actor reads the public Greenhouse
board feed that any logged-out visitor can see. No account, no cookies, no session.

**How many job postings does one request return?** One request returns the entire Greenhouse board.
A measured run collected 814 postings from 1.23 requests, so a large board costs the same single
fetch as a small one.

**Does it work for any company on Greenhouse?** Yes — any board hosted on Greenhouse, addressed by
its board token. Nothing is hardcoded per company.

**Can I get the full job description text?** No. This Actor returns the board's posting fields listed
above; follow `jobUrl` for the full description. The description is deliberately excluded because
requesting it inflates one board's response from 0.7MB to 7.5MB.

**Why are `city`, `state` and `country` sometimes empty?** Greenhouse does not model a location —
`location` is free text a recruiter typed. Values are only split when the string is unambiguously one
place, so `Cork, Ireland; Dublin, Ireland` and `Dublin OR London` are left unsplit rather than
guessed at. The verbatim string is always in `location`.

### Limitations

Board fields only: no job description body, no salary or compensation, no application counts and no
recruiter contacts. `employmentType` exists only where the company publishes it as board metadata, so
it is `null` on many boards. Only `greenhouse.io` boards are accepted — a URL on any other host is
rejected rather than fetched.

### Free plan limit

Runs started from an Apify **free plan** stop at **250 requests and 250 results**, and the run
reports that it reached the limit. Any paid plan runs the full input and `maxItems` you set.

The limit exists because this Actor fetches through our own infrastructure, which Apify does not
cover for free-plan runs. It binds on requests as well as results so that a large input list cannot
spend those fetches for rows the run will not return.

# Actor input Schema

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

Greenhouse board URLs or company tokens.

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

Global cap on dataset items. Runs started from an Apify free plan stop at 250 requests and 250 results; any paid plan runs the full amount.

## `concurrency` (type: `integer`):

Targets fetched in parallel.

## Actor input object example

```json
{
  "boards": [
    "https://job-boards.greenhouse.io/databricks"
  ],
  "maxItems": 1000,
  "concurrency": 5
}
```

# Actor output Schema

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

Collect every open job posting from any Greenhouse-hosted job board in one request.

## `summary` (type: `string`):

Item count, failure count and every target that failed, with its error.

# 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/databricks"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("usestring/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/databricks"] }

# Run the Actor and wait for it to finish
run = client.actor("usestring/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/databricks"
  ]
}' |
apify call usestring/greenhouse-jobs --silent --output-dataset

```

## MCP server setup

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