# Greenhouse Job Boards Scraper - All Openings, No API Key (`ninhothedev/greenhouse-jobs-scraper`) Actor

$0.5/1K 🔥 Greenhouse job board scraper! Every opening from any company career page with full descriptions. No key. JSON, CSV, Excel or API in seconds. Build job boards & hiring intel ⚡

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

## Pricing

from $0.50 / 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.

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 Boards Scraper

**The dedicated Greenhouse board reader.** Point it at any company slug and get every open position from that company's Greenhouse job board — with the full, readable job description. No API key, no login, no cookies.

Greenhouse is the single most-used applicant tracking system among tech companies. Thousands of employers — from seed startups to public companies — publish their openings on `boards.greenhouse.io/<slug>` or an embedded Greenhouse widget on their own careers page. This Actor reads those boards directly through Greenhouse's free public Job Board API, so the data is exactly what the company publishes: structured, complete and current.

***

### What you get

One dataset item per job opening:

| Field | Description |
|---|---|
| `company` | The board token (company slug) the job came from |
| `job_id` | Greenhouse public job ID |
| `internal_job_id` | Greenhouse internal job ID |
| `title` | Job title |
| `location` | Location string as published |
| `departments` | List of department names |
| `offices` | List of office names |
| `description` | Full description as clean, readable plain text (HTML entities decoded, tags stripped, max 8,000 chars) |
| `description_html` | Original description markup (max 20,000 chars) |
| `updated_at` | Last update, normalised to UTC ISO 8601 |
| `requisition_id` | Company-internal requisition ID |
| `is_remote` | `true` when the location or title signals remote / anywhere / distributed |
| `employment_type` | Employment type, when the board publishes it as job metadata |
| `metadata` | Compact `[{name, value}]` list of the board's custom fields (max 15) |
| `apply_url` | Direct link to the application page |
| `source` | Always `greenhouse` |
| `scraped_at` | Run timestamp |

Every field is nullable — boards differ in how much they publish, and the Actor never invents data.

#### Sample output

```json
{
  "company": "figma",
  "job_id": 5364702004,
  "internal_job_id": 5178563004,
  "title": "Account Executive, Emerging Enterprise (Berlin, Germany)",
  "location": "Berlin, Germany",
  "departments": ["Sales"],
  "offices": ["Berlin, DE"],
  "description": "Figma is growing our team of passionate creatives and builders on a mission to make design accessible to all...",
  "description_html": "<div class=\"content-intro\"><p>Figma is growing our team...</p></div>",
  "updated_at": "2026-07-22T09:37:08Z",
  "requisition_id": "1334",
  "is_remote": false,
  "employment_type": null,
  "metadata": null,
  "apply_url": "https://boards.greenhouse.io/figma/jobs/5364702004?gh_jid=5364702004",
  "source": "greenhouse",
  "scraped_at": "2026-07-28T17:44:02Z"
}
```

***

### How to find a board token

The **board token** is the company slug in the Greenhouse URL. It is always lowercase.

1. **Straight from a Greenhouse board URL** — `https://boards.greenhouse.io/stripe` → token is `stripe`. New-style URLs work the same way: `https://job-boards.greenhouse.io/figma` → `figma`.
2. **From a company careers page** — open the careers page, click a job, and look at the URL or the apply link. If you see `gh_jid=` in the query string, the company uses Greenhouse. Then open the page source and search for `greenhouse.io/` — the segment right after it is the token. Many careers pages embed Greenhouse in an iframe pointing at `boards.greenhouse.io/embed/job_board?for=<token>`.
3. **Guess and check** — the token is very often the plain company name (`gitlab`, `reddit`, `coinbase`, `robinhood`, `airbnb`). Just try it: an unknown token is logged as a warning and skipped, it never kills the run.

Note that the token is not always the brand name — DoorDash, for example, publishes under `doordashusa`, not `doordash`.

You can also paste a full board URL into `boardTokens`; the Actor reduces it to the slug for you.

***

### Input

```json
{
  "mode": "boards",
  "boardTokens": ["stripe", "figma", "doordashusa"],
  "includeContent": true,
  "titleFilter": "engineer",
  "locationFilter": "remote",
  "maxItemsPerBoard": 200,
  "maxItems": 500
}
```

| Input | Default | What it does |
|---|---|---|
| `mode` | `boards` | Currently one mode: read all jobs of the given company boards |
| `boardTokens` | `["stripe","figma","doordashusa"]` | The company slugs to scrape. Full board URLs are accepted too |
| `includeContent` | `true` | Fetch full descriptions. Turn off for a much faster listing-only run |
| `titleFilter` | — | Case-insensitive substring on the job title |
| `locationFilter` | — | Case-insensitive substring on location and office names |
| `maxItemsPerBoard` | `200` | Cap per company — handy when scraping many boards |
| `maxItems` | `500` (max 5,000) | Global cap on dataset items |

Unknown board tokens produce a warning and are skipped. The run only fails when **no** board returned a single job.

***

### Pricing

Roughly **$0.50 per 1,000 jobs**. Each board is a single API call, so a run over dozens of companies costs cents and finishes in seconds. Descriptions come along in the same request — there is no per-job fetch penalty.

***

### Use cases

- **Job aggregators & job boards** — Greenhouse boards are the primary source for tech roles. One call per company gives you title, location, department, apply URL and the full description, ready to index and dedupe.
- **Recruiting intelligence** — track which teams a competitor is staffing, where they are opening offices, how quickly requisitions appear and disappear, and which roles stay open longest.
- **Hiring-trend analysis** — snapshot boards on a schedule and chart headcount plans by department, seniority and location. `updated_at` and `requisition_id` make it easy to diff runs.
- **Sales prospecting on hiring signals** — a company hiring five data engineers is buying a data stack. Filter descriptions for tools, certifications or platforms and turn open roles into a timed, well-qualified outbound list.

***

### Notes

- Data comes from Greenhouse's **public** Job Board API — the same content any visitor sees on the board. No credentials are used and no candidate data is touched.
- Greenhouse returns job descriptions HTML-entity-encoded. This Actor decodes them properly and gives you both a clean-text and an HTML version, so you never end up with `&lt;p&gt;` in your dataset.
- Boards do not paginate: one request returns every open position, so results are complete and consistent.

***

### Related Actors

- [Lever Jobs Scraper](https://apify.com/ninhothedev/lever-jobs-scraper) — the same job for Lever-powered boards
- [Ashby Jobs Scraper](https://apify.com/ninhothedev/ashby-jobs-scraper) — for companies on Ashby
- [Workable Jobs Scraper](https://apify.com/ninhothedev/workable-jobs-scraper) — for companies on Workable
- [ATS Jobs Scraper](https://apify.com/ninhothedev/ats-jobs-scraper) — multi-ATS scraper when you don't know which system a company uses

# Actor input Schema

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

What to scrape. 'boards' reads every open position from each company board token you supply. This is currently the only mode.

## `boardTokens` (type: `array`):

One or more Greenhouse board tokens. The board token is the company slug in the board URL: boards.greenhouse.io/<slug> (e.g. 'stripe' for boards.greenhouse.io/stripe). Tokens are lowercase. You can also paste a full board URL and it will be reduced to the slug. Unknown tokens are logged as a warning and skipped.

## `includeContent` (type: `boolean`):

Request the full job description for every opening (adds 'description' as clean text and 'description\_html' as raw HTML). Turn this off for a much smaller and faster listing-only run.

## `titleFilter` (type: `string`):

Case-insensitive substring that must appear in the job title, e.g. 'engineer' keeps 'Senior Software Engineer'. Leave empty to keep all titles.

## `locationFilter` (type: `string`):

Case-insensitive substring matched against the job location and office names, e.g. 'berlin', 'united states' or 'remote'. Leave empty to keep all locations.

## `maxItemsPerBoard` (type: `integer`):

Maximum number of jobs to keep from each single board token. Useful when you scrape many companies and only want a sample of each.

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

Hard cap on the total number of dataset items across all boards. The run stops once this is reached.

## Actor input object example

```json
{
  "mode": "boards",
  "boardTokens": [
    "stripe",
    "figma",
    "doordashusa"
  ],
  "includeContent": true,
  "maxItemsPerBoard": 200,
  "maxItems": 500
}
```

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

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

# Run the Actor and wait for it to finish
run = client.actor("ninhothedev/greenhouse-jobs-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "boardTokens": [
    "stripe",
    "figma",
    "doordashusa"
  ]
}' |
apify call ninhothedev/greenhouse-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=ninhothedev/greenhouse-jobs-scraper",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/YSgyr5TLfjyK0iewC/builds/O4n6pcJOzDif9v6rW/openapi.json