# 🌱 Greenhouse Job Scraper: Jobs, Pay and Descriptions (`findata/greenhouse-job-scraper`) Actor

Scrape every open job from any Greenhouse board, US or EU. Title, department, office, location, pay range, posted and updated dates, full description and apply link as clean JSON. Only-new mode for monitoring. No login, no proxies.

- **URL**: https://apify.com/findata/greenhouse-job-scraper.md
- **Developed by:** [Fin Data](https://apify.com/findata) (community)
- **Categories:** Jobs
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.10 / 1,000 job records

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/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 Job Scraper

Every open job from any Greenhouse job board, as clean JSON. Paste a `boards.greenhouse.io` URL or just the board token and get title, department, office, location, pay range, posted and updated dates, the full description and the apply link for every posting.

Built for recruiters sourcing from technology and growth companies, sales teams that use hiring as a buying signal, job boards that need a direct feed instead of a scrape of a scrape, and AI agents that need job data in one shape.

### Why a dedicated Greenhouse scraper

Greenhouse publishes a public job-board API, so the raw data is reachable. What this actor adds is the part that takes a day to get right yourself:

- One request per board returns every job with its full description; no per-job calls, no HTML parsing of the careers page.
- EU-hosted boards (`boards.eu.greenhouse.io`) are detected and read from the EU API automatically.
- Departments and offices are flattened into `department`, `team`, `location` and `locations` so you can filter without walking nested arrays.
- Pay ranges are read from Greenhouse's pay-transparency fields when a company fills them in, and parsed from the description text when it does not.
- Only-new mode, filters that run before billing, and a fail-soft run that finishes even when one board has been renamed or closed.

### Finding a Greenhouse board

Open the company's careers page and click any job. If the address bar shows `greenhouse.io`, the first path segment is the board token. Any of these work as a source:

| Shape | Example |
| --- | --- |
| Board URL | https://boards.greenhouse.io/stripe |
| New-style board URL | https://job-boards.greenhouse.io/cloudflare |
| A job page | https://boards.greenhouse.io/figma/jobs/5123456 |
| EU board | https://boards.eu.greenhouse.io/company |
| Just the token | stripe |

Companies that embed Greenhouse on their own domain still have a board token; it is in the embed script (`for=token`) or in the apply URL.

### Input

```json
{
  "sources": ["stripe", "https://boards.greenhouse.io/cloudflare"],
  "keywords": ["account executive", "sales"],
  "locations": ["New York", "Remote"],
  "postedWithinDays": 7,
  "onlyNew": true
}
```

| Field | Type | Default | What it does |
| --- | --- | --- | --- |
| preset | string | custom | Employer list: `custom` (default), `sample`. `custom` runs the sites you list and falls back to the sample boards when the list is empty |
| sources | string\[] | \[] | Greenhouse board URLs or board tokens |
| keywords | string\[] | \[] | Keep jobs whose title contains any of these (case-insensitive) |
| excludeKeywords | string\[] | \[] | Drop jobs whose title contains any of these |
| locations | string\[] | \[] | Keep jobs whose location or office text contains any of these |
| departments | string\[] | \[] | Keep jobs whose department or team contains any of these |
| remoteOnly | boolean | false | Keep only jobs whose location or office says remote |
| postedWithinDays | integer | 0 | Keep only jobs first published or updated in the last N days; 0 disables |
| includeDescriptionHtml | boolean | false | Add the original HTML description next to the plain text |
| onlyNew | boolean | false | Output only jobs not seen on a previous run of this board |
| seenStoreName | string | greenhouse-job-scraper-seen | Key-value store that remembers seen job IDs; use one name per monitor |
| maxJobsPerSource | integer | 0 | Stop after N jobs per board; 0 means the whole board |
| maxConcurrency | integer | 5 | Boards pulled in parallel |

Descriptions come with the list call, so there is no "fetch details" switch; every record has `descriptionText`.

### Output

One record per job.

```json
{
  "vendor": "greenhouse",
  "source": "https://boards.greenhouse.io/stripe",
  "company": "Stripe",
  "jobId": "6123456",
  "title": "Account Executive, Enterprise",
  "department": "Sales",
  "team": null,
  "location": "New York, NY",
  "locations": ["New York, NY", "NYC"],
  "remote": null,
  "employmentType": "Full-time",
  "postedAt": "2026-10-28T14:02:11.000Z",
  "updatedAt": "2026-11-03T09:15:40.000Z",
  "url": "https://boards.greenhouse.io/stripe/jobs/6123456",
  "descriptionText": "Who we are...",
  "salaryMin": 150000,
  "salaryMax": 210000,
  "salaryCurrency": "USD",
  "salaryPeriod": "year",
  "salaryText": "The annual US base salary range for this role is $150,000 - $210,000.",
  "extra": { "internalJobId": 4567890, "metadata": [] },
  "scrapedAt": "2026-11-05T01:47:38.912Z"
}
```

| Field | Meaning |
| --- | --- |
| company | Company name as Greenhouse reports it |
| jobId | Greenhouse job ID (the number in the job URL). Stable; use it as the key. `extra.internalJobId` is the requisition-level ID |
| department, team | First and second department Greenhouse lists for the job |
| location, locations | Greenhouse's location name first, then every office name |
| remote | true when the location or an office says remote; null otherwise (Greenhouse has no remote flag) |
| postedAt, updatedAt | `first_published` and `updated_at` from Greenhouse, ISO 8601 |
| employmentType | From the job's metadata when the company uses an employment-type field |
| salaryMin, salaryMax, salaryCurrency, salaryPeriod, salaryText | From pay-range fields or the description when published; otherwise null |
| extra.metadata | Every custom metadata field the company attaches to the job, untouched |

A `RUN_SUMMARY` record in the default key-value store reports boards processed, jobs fetched, filtered, de-duplicated, skipped as already seen, and any board failures with the error text.

### Pricing

Pay per event. You are charged per job record written to the dataset, plus a small actor-start event. Filtered-out jobs and already-seen jobs in only-new mode are not charged. One request per board and no proxies, so platform usage is a fraction of a cent per run.

### Monitoring new postings

1. Set `onlyNew` to true and give `seenStoreName` a name for this monitor.
2. Add your filters.
3. Schedule the actor (daily, or hourly for boards you care about).
4. Connect the dataset to Google Sheets, Slack, Make, Zapier or a webhook from the Integrations tab.

The first run outputs everything on the boards and remembers it. Each later run outputs only what is new.

### Limits and notes

- Public job-board API only. No login, no proxies, no candidate or private data.
- Boards that are closed, renamed or set to private return an error for that board only; the run continues.
- Greenhouse does not expose a remote flag; `remote` is inferred from location and office names.
- This actor reads Greenhouse boards only. For Workday, Lever, Ashby or SmartRecruiters, or for a mixed list where you do not know the ATS, use the FinData Career Site Job Scraper.

### Related FinData job scrapers

Same engine, same output fields, so records from any of them can be combined.

- [Workday Job Scraper](https://apify.com/findata/workday-job-scraper)
- [Lever Job Scraper](https://apify.com/findata/lever-job-scraper)
- [Ashby Job Scraper](https://apify.com/findata/ashby-job-scraper)
- [Career Site Job Scraper (any company, ATS auto-detected)](https://apify.com/findata/career-site-job-scraper)
- [Workday, Greenhouse, Lever, Ashby, SmartRecruiters Job Scraper (all five in one actor)](https://apify.com/findata/ats-jobs-feed)

### For AI agents

Every field is optional: an empty input `{}` runs the sample boards and returns jobs, so a first call never fails. Pick `"preset": "sample"` to say so explicitly. Minimal call: `{ "sources": ["stripe"] }`. Add `"keywords"` and `"locations"` arrays to narrow. Every record has the same fields and includes the description; `jobId` is the stable key.

### Using it from code

```js
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('findata/greenhouse-job-scraper').call({
    sources: ['stripe', 'cloudflare'],
    keywords: ['engineer'],
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
```

Works the same through the Apify API, MCP server and the Python client.

# Actor input Schema

## `preset` (type: `string`):

Pick a ready-made list or use your own. "The career sites I list below" runs exactly the sites in the next field, and if that field is empty it falls back to the sample boards so a run never fails for lack of input. The other choices add a curated list on top of anything you paste.

## `sources` (type: `array`):

Greenhouse board URLs or board tokens, one per line. The token is the last part of the board URL: for https://boards.greenhouse.io/stripe it is stripe. EU-hosted boards (boards.eu.greenhouse.io) are detected automatically. Examples: https://boards.greenhouse.io/stripe, https://job-boards.greenhouse.io/cloudflare, or just figma. Optional when an Employer list is chosen above.

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

Keep jobs whose title contains at least one of these words or phrases. Case-insensitive. Leave empty to keep all.

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

Drop jobs whose title contains any of these words or phrases. Case-insensitive.

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

Keep jobs whose location text contains at least one of these, e.g. Atlanta, Georgia, GA, United States. Case-insensitive. Leave empty to keep all. With the Georgia and upstate SC list chosen and this left empty, the list's own Georgia and South Carolina locations are used.

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

Keep jobs whose department or team contains at least one of these, e.g. Finance, Engineering, People.

## `remoteOnly` (type: `boolean`):

Keep only jobs the ATS marks as remote or whose location says remote.

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

Keep only jobs posted or updated within this many days. 0 means no limit. Workday list pages only give relative dates, so this is applied to the parsed value.

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

Add the raw HTML description to each record alongside the plain text. Makes datasets larger.

## `onlyNew` (type: `boolean`):

Remember every job ID seen per source in a named key-value store and output only jobs not seen before. Use with a schedule to get a feed of new postings. You are charged only for jobs that are output.

## `seenStoreName` (type: `string`):

Name of the key-value store used by only-new mode. Use a different name per monitor if you run several configurations.

## `maxJobsPerSource` (type: `integer`):

Stop paging a source after this many jobs. 0 means no limit. Workday boards cap at 2,000 per query; the actor splits large boards by facet automatically so you still get the whole board.

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

How many career sites to pull at the same time.

## Actor input object example

```json
{
  "preset": "custom",
  "sources": [
    "https://boards.greenhouse.io/stripe",
    "https://boards.greenhouse.io/cloudflare",
    "https://boards.greenhouse.io/figma",
    "https://boards.greenhouse.io/gitlab",
    "https://boards.greenhouse.io/reddit"
  ],
  "keywords": [],
  "excludeKeywords": [],
  "locations": [],
  "departments": [],
  "remoteOnly": false,
  "postedWithinDays": 0,
  "includeDescriptionHtml": false,
  "onlyNew": false,
  "seenStoreName": "greenhouse-job-scraper-seen",
  "maxJobsPerSource": 0,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

One record per job posting, normalized across Workday, Greenhouse, Lever, Ashby and SmartRecruiters.

## `jobsTable` (type: `string`):

Same records in the Console table view.

## `runSummary` (type: `string`):

Sources processed, jobs fetched, filtered, de-duplicated, already seen, and any source failures.

# 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 = {
    "sources": [
        "https://boards.greenhouse.io/stripe",
        "https://boards.greenhouse.io/cloudflare",
        "https://boards.greenhouse.io/figma",
        "https://boards.greenhouse.io/gitlab",
        "https://boards.greenhouse.io/reddit"
    ],
    "keywords": [],
    "excludeKeywords": [],
    "locations": [],
    "departments": [],
    "seenStoreName": "greenhouse-job-scraper-seen"
};

// Run the Actor and wait for it to finish
const run = await client.actor("findata/greenhouse-job-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 = {
    "sources": [
        "https://boards.greenhouse.io/stripe",
        "https://boards.greenhouse.io/cloudflare",
        "https://boards.greenhouse.io/figma",
        "https://boards.greenhouse.io/gitlab",
        "https://boards.greenhouse.io/reddit",
    ],
    "keywords": [],
    "excludeKeywords": [],
    "locations": [],
    "departments": [],
    "seenStoreName": "greenhouse-job-scraper-seen",
}

# Run the Actor and wait for it to finish
run = client.actor("findata/greenhouse-job-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 '{
  "sources": [
    "https://boards.greenhouse.io/stripe",
    "https://boards.greenhouse.io/cloudflare",
    "https://boards.greenhouse.io/figma",
    "https://boards.greenhouse.io/gitlab",
    "https://boards.greenhouse.io/reddit"
  ],
  "keywords": [],
  "excludeKeywords": [],
  "locations": [],
  "departments": [],
  "seenStoreName": "greenhouse-job-scraper-seen"
}' |
apify call findata/greenhouse-job-scraper --silent --output-dataset

```

## MCP server setup

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