# Greenhouse Jobs Scraper: Locations, Departments & Apply Links (`arman-bd/greenhouse-jobs-scraper`) Actor

Scrape public job listings from any Greenhouse-hosted job board. Returns title, location, department, the full description and an apply URL. No login, no proxy, no browser.

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

## Pricing

from $2.00 / 1,000 job scrapeds

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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 Jobs Scraper: Locations, Departments & Apply Links

![Greenhouse Jobs: Every open role on any Greenhouse board, with departments, offices and apply links](https://api.apify.com/v2/key-value-stores/ZQOcNAOHrIgTacAmy/records/greenhouse-jobs-scraper.jpg)

Pulls every open role from any Greenhouse-hosted job board. You get the title, location, offices, departments, the full description as plain text, and a direct apply link.

Thousands of companies post through Greenhouse, and every board exposes a public JSON feed. This Actor reads that feed directly, so there's no browser, no proxy, no login and no rate-limit games. A board with 500 roles comes back in a couple of seconds.

**Agent skill: [SKILL.md](https://api.apify.com/v2/key-value-stores/t7YoTxpZEJOWvw4Ug/records/greenhouse-jobs-scraper.md)**

```
https://api.apify.com/v2/key-value-stores/t7YoTxpZEJOWvw4Ug/records/greenhouse-jobs-scraper.md
```

### What you get

| Field | What it holds |
|---|---|
| `board`, `company` | The board token used, and the company name Greenhouse reports |
| `jobId`, `requisitionId` | Greenhouse's job ID and the company's internal requisition ID |
| `title` | Job title |
| `location`, `offices` | The location string, plus the structured office list |
| `departments` | Every department the role is filed under |
| `url` | Direct apply link |
| `firstPublished`, `updatedAt`, `applicationDeadline` | Posting timestamps |
| `description` | Full description as clean plain text, with HTML stripped and entities decoded |
| `scrapedAt` | When the run happened |

`RUN_SUMMARY` in the key-value store holds per-run counts, the filters you used, and any board that failed.

### What people use it for

- **Job aggregators.** Ingest hundreds of company boards on a schedule.
- **Recruiting intelligence.** See which teams a competitor is hiring into, and where.
- **Lead generation.** A company hiring for a role is usually a company buying for it.
- **Market research.** Track hiring volume by department or location over time.
- **Job hunting.** Watch a shortlist of companies and filter down to what you actually want.

### Quick start

Two boards, everything on them:

```json
{
 "boards": ["stripe", "figma"]
}
```

Remote engineering roles only, capped:

```json
{
 "boards": ["stripe", "https://boards.greenhouse.io/airbnb"],
 "searchTerms": ["engineer", "developer"],
 "locationFilter": ["remote"],
 "departmentFilter": ["engineering"],
 "maxJobsPerBoard": 50,
 "includeDescription": true
}
```

A light sweep for change detection:

```json
{
 "boards": ["stripe"],
 "includeDescription": false
}
```

### Input

| Field | Type | Default | Notes |
|---|---|---|---|
| `boards` | array | required | Board tokens like `stripe`, or full board URLs. You can mix both. URLs get normalised to tokens for you. |
| `searchTerms` | array | `[]` | Keep only titles containing one of these terms, case-insensitive. Empty means keep everything. |
| `locationFilter` | array | `[]` | Keep only locations containing one of these terms. Empty means all locations. |
| `departmentFilter` | array | `[]` | Keep only departments matching one of these terms. Empty means all departments. |
| `maxJobsPerBoard` | integer | `0` | Cap jobs saved per board, applied after filtering. 0 means no limit. |
| `includeDescription` | boolean | `true` | Include the full plain-text description. Turn it off for a much smaller, faster dataset. |

The three filters are independent and combine with AND. A job has to match at least one term in each filter you actually filled in.

### Output example

```json
{
 "board": "stripe",
 "company": "Stripe",
 "jobId": 8023928,
 "requisitionId": "REQ-1234",
 "title": "Account Executive, Bridge",
 "location": "London",
 "offices": ["London"],
 "departments": ["Sales"],
 "url": "https://stripe.com/jobs/search?gh_jid=8023928",
 "firstPublished": "2026-07-14T09:12:00Z",
 "updatedAt": "2026-08-01T11:03:22Z",
 "applicationDeadline": null,
 "description": "About the team\n\nBridge is .",
 "scrapedAt": "2026-08-06T12:00:00.000Z"
}
```

### Finding a board token

Open a company's careers page and look at the URL.

| URL you see | Token |
|---|---|
| `boards.greenhouse.io/acme` | `acme` |
| `job-boards.greenhouse.io/acme` | `acme` |
| `./embed/job_board?for=acme` | `acme` |

You can paste the whole URL and let the Actor pull the token out. If the careers page sits on the company's own domain, view source and search for `greenhouse.io`. The token is nearly always in an iframe or a fetch URL.

### API example

```bash
curl -X POST "https://api.apify.com/v2/acts/arman-bd~greenhouse-jobs-scraper/run-sync-get-dataset-items?token=YOUR_TOKEN" \
 -H "Content-Type: application/json" \
 -d '{
 "boards": ["stripe"],
 "searchTerms": ["engineer"],
 "maxJobsPerBoard": 25
 }'
```

### JavaScript example

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

const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('arman-bd/greenhouse-jobs-scraper').call({
 boards: ['stripe', 'figma'],
 searchTerms: ['engineer'],
 locationFilter: ['remote'],
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
for (const job of items) console.log(`${job.company} - ${job.title} (${job.location})`);
```

### Notes

- A bad board won't kill the run. Unknown boards return HTTP 404 and land in `RUN_SUMMARY.failures`. The Actor only errors out if every board fails.
- Transient errors get retried. 429s and 5xx responses get three attempts with linear backoff.
- Descriptions are decoded twice. Greenhouse returns entity-encoded HTML and some boards double-encode it, so entities are decoded before tags are stripped and again afterwards. You get real text, not `<p>`.
- Public data only. No authentication, no personal data, nothing that gets around access controls.

### FAQ

**Do I need a Greenhouse API key?** No. You supply no credentials.

**Does it include salary?** Only if the company wrote it into the description. Greenhouse's public feed has no structured salary field, and this Actor won't invent one.

**How many boards can I pass at once?** There's no hard cap. Each board is one request and they run in sequence, so hundreds per run is normal.

**Why did a board return nothing?** Either the token is wrong or your filters excluded everything. `RUN_SUMMARY` reports listed, matched and saved counts per board, which tells the two apart straight away.

**Can I get only new or changed jobs?** Run it on a schedule and diff on `jobId` and `updatedAt`. Setting `includeDescription` to `false` makes those sweeps a lot cheaper.

**Can I plug it into something else?** Yes. Apify API, the client libraries, webhooks, scheduled runs, dataset exports to JSON, CSV or Excel, or MCP. The output is structured JSON.

# Actor input Schema

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

Board tokens or job-board URLs. The token is the company slug in the board URL, so for https://boards.greenhouse.io/stripe the token is 'stripe'. Full URLs work too and get normalized for you.

## `searchTerms` (type: `array`):

Keep only jobs whose title contains at least one of these terms (case-insensitive). Leave empty to keep every job.

## `locationFilter` (type: `array`):

Keep only jobs whose location contains at least one of these terms (case-insensitive). Leave empty for all locations.

## `departmentFilter` (type: `array`):

Keep only jobs in departments matching at least one of these terms (case-insensitive). Leave empty for all departments.

## `maxJobsPerBoard` (type: `integer`):

Cap the number of jobs saved per board after filtering. Set 0 for no limit.

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

Include the full job description as plain text. Disable for a smaller, faster dataset.

## Actor input object example

```json
{
  "boards": [
    "stripe",
    "https://boards.greenhouse.io/airbnb"
  ],
  "searchTerms": [
    "engineer",
    "designer"
  ],
  "locationFilter": [
    "remote",
    "london"
  ],
  "departmentFilter": [
    "engineering"
  ],
  "maxJobsPerBoard": 0,
  "includeDescription": true
}
```

# Actor output Schema

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

One record per open role that passed your filters.

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

Per-run counts, the filters used, and any board that failed.

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

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

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,arman-bd/greenhouse-jobs-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/U4xsopfnVIUenMjnN/builds/q1o1L7NojwTLz2iud/openapi.json