# Greenhouse Jobs Scraper (`fabrikit/greenhouse-jobs-scraper`) Actor

Scrape job postings from any Greenhouse job board: title, location, remote flag, department, apply URL and dates. Official public API — no key, no proxies. US$0.50 per 1,000 jobs.

- **URL**: https://apify.com/fabrikit/greenhouse-jobs-scraper.md
- **Developed by:** [Fabrikit](https://apify.com/fabrikit) (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 job 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/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 Scraper

Scrape job postings from any company's **Greenhouse job board** — just paste board slugs or careers-page URLs and get every open position back as clean JSON: title, location, remote flag, department, direct apply URL and posting dates. No API key, no login, no proxies, no browser: the Actor reads Greenhouse's **official public Job Board API**, so runs finish in seconds and never break when a careers page changes its design. Export to JSON, CSV, Excel, Google Sheets or your database.

What you get from a single run:

- **Every open job at every company you list** — thousands of companies hire through Greenhouse (Stripe, GitLab, Duolingo, Databricks, ...), and each posting comes back with the same clean fields, deduplicated.
- **Zero setup and zero breakage risk**: this is the same battle-tested Greenhouse connector that powers our multi-ATS scraper, reading `boards-api.greenhouse.io` directly instead of parsing HTML.
- **A per-company summary** (jobs found, boards not found, any errors) in the run's key-value store, so pipelines can verify coverage automatically.

Example output item (real posting from a live run):

```json
{
    "ats": "greenhouse",
    "company": "gitlab",
    "companyName": "GitLab",
    "sourceId": "8620720002",
    "title": "Backend Engineer (Ruby), AI Engineering: Agent Observability",
    "location": "Remote, Canada",
    "allLocations": ["Remote, Canada"],
    "remote": true,
    "department": "AI Engineering",
    "url": "https://job-boards.greenhouse.io/gitlab/jobs/8620720002",
    "applyUrl": "https://job-boards.greenhouse.io/gitlab/jobs/8620720002",
    "publishedAt": "2026-07-08T10:30:39.000Z",
    "updatedAt": "2026-08-10T20:52:46.000Z",
    "description": null,
    "scrapedAt": "2026-08-21T01:59:56.231Z"
}
```

### How to scrape Greenhouse job postings

1. Add one entry per company to **companies**. Any of these formats works:
   - The board slug — the identifier in the careers URL: `boards.greenhouse.io/stripe` → `stripe`.
   - The full board URL — `https://boards.greenhouse.io/gitlab` or `https://job-boards.greenhouse.io/stripe` (embed URLs with `?for=<slug>` work too).
2. Press **Start**. Results land in the dataset within seconds and can be downloaded as JSON, CSV or Excel, or pushed to Sheets, webhooks, Zapier, Make or the Apify API.

#### Example input

```json
{
    "companies": [
        "duolingo",
        "https://boards.greenhouse.io/gitlab"
    ],
    "maxJobsPerCompany": 50,
    "includeDescription": false
}
```

- **companies** *(required)* — list of Greenhouse board slugs or URLs.
- **maxJobsPerCompany** — cap per company; `0` = the full board. The form prefills `50` so your first run stays small and cheap.
- **includeDescription** — add the full plain-text job description to each item (larger dataset).

#### Example: full boards with descriptions

```json
{
    "companies": ["stripe", "databricks"],
    "maxJobsPerCompany": 0,
    "includeDescription": true
}
```

A run like this returns 1,000+ postings in well under a minute.

### Greenhouse job board API — output fields

| Field | Type | Description |
|---|---|---|
| `ats` | string | Always `greenhouse` (compatible with our multi-ATS scraper's schema) |
| `company` | string | The board slug you passed in |
| `companyName` | string | Company display name from the board |
| `sourceId` | string | Greenhouse posting ID (stable across runs — perfect for diffing) |
| `title` | string | Job title |
| `location` | string | null | Primary location as shown on the posting |
| `allLocations` | string\[] | All listed offices/locations |
| `remote` | boolean | null | `true` if detected as remote, `null` if the posting doesn't say |
| `department` | string | null | Department |
| `url` | string | Public posting URL |
| `applyUrl` | string | Direct application URL |
| `publishedAt` | string | null | ISO 8601 first-published date |
| `updatedAt` | string | null | ISO 8601 last-updated date |
| `description` | string | null | Plain-text description (only if `includeDescription`) |
| `scrapedAt` | string | ISO 8601 timestamp of this run |

### What can you build with Greenhouse jobs data?

- **Niche job boards** — remote-only, one industry, one region — refreshed automatically on a schedule.
- **Recruiting intelligence & talent mapping**: which target companies are hiring for which roles, right now.
- **Sales & investing signals**: a competitor opening 30 engineering roles is a growth signal you can query daily.
- **Lead generation for recruiters and agencies**: companies actively hiring for the roles you place.
- **LLM pipelines**: one consistent schema means one prompt — pipe the dataset into an LLM via Apify integrations or MCP.

### Pricing — US$0.50 per 1,000 jobs

This Actor uses Apify's **pay-per-event** model and charges **per job returned** (event `job-result`, **US$0.0005 per job = US$0.50 per 1,000 jobs**) on top of standard Apify platform usage. No subscription, no rental fee, no proxy costs — the Actor talks to an official public API, so compute usage is minimal. A 50-company sweep returning 5,000 jobs costs about US$2.50 in events. You only pay for jobs actually delivered to your dataset.

### Integrations

Run the Actor and read results from your own code with the Apify API — or connect the dataset to **Google Sheets, Zapier, Make, Slack, webhooks or MCP** directly from Apify Console with no code at all.

**Python** (`pip install apify-client`):

```python
from apify_client import ApifyClient

client = ApifyClient("<YOUR_API_TOKEN>")
run = client.actor("fabrikit/greenhouse-jobs-scraper").call(run_input={
    "companies": ["stripe", "gitlab"],
    "maxJobsPerCompany": 0,
})
for job in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(job["title"], "-", job["location"], job["url"])
```

**JavaScript** (`npm i apify-client`):

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

const client = new ApifyClient({ token: '<YOUR_API_TOKEN>' });
const run = await client.actor('fabrikit/greenhouse-jobs-scraper').call({
    companies: ['stripe', 'gitlab'],
    maxJobsPerCompany: 0,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`${items.length} jobs`);
```

### Performance & limits

- **Speed**: one HTTP request per company board — a full 800-job board downloads in ~2 seconds; 1,379 jobs from two boards took under 10 seconds in testing.
- **No pagination limits**: Greenhouse's board API returns the complete board in one response; `maxJobsPerCompany: 0` always gets everything.
- **No proxies, no browser**: minimal platform usage, no extra costs, nothing to configure.
- **Reliability**: the source is the official API Greenhouse itself serves careers pages from. If a board doesn't exist, the Actor logs it in `SUMMARY` with `"error": "board not found"` and continues with the rest.

### Tips for best results

- Start with the prefilled input (2 companies, 50 jobs each) to see the schema, then set `maxJobsPerCompany: 0` for full boards.
- Leave `includeDescription` off unless you need the text — datasets stay small and exports fast.
- **Monitoring**: schedule the Actor daily and diff on `sourceId` — it is stable per posting, so new/removed IDs are new/closed jobs, and `updatedAt` catches edits.
- Filter remote jobs downstream on the `remote` field (`true` / `null`), or on `allLocations` for specific offices.
- Company not on Greenhouse? Use our [ATS Jobs Scraper](https://apify.com/fabrikit/ats-jobs-api) — same schema, and it auto-detects Greenhouse, Lever, Ashby and SmartRecruiters boards.

### FAQ

**Does Greenhouse have a public API for job postings?**
Yes. Greenhouse publishes an official, unauthenticated Job Board API (`boards-api.greenhouse.io/v1/boards/<slug>/jobs`) — the same one that powers companies' careers pages. This Actor reads it directly, which is why it needs no API key, no login and no proxies, and why it's far more reliable than scrapers that parse careers-page HTML.

**How do I find a company's Greenhouse board slug?**
Open the company's careers page and look at the URL: `boards.greenhouse.io/stripe` → slug `stripe`. Or don't bother — paste the full URL and the Actor extracts the slug itself. Embedded boards (`boards.greenhouse.io/embed/job_board?for=acme`) work too.

**Can I export Greenhouse jobs to CSV or Excel?**
Yes. Every Apify dataset downloads as CSV, Excel, JSON, XML or HTML with one click, or syncs to Google Sheets — no code needed.

**Is it legal to scrape Greenhouse job postings?**
This Actor only reads job data that Greenhouse publishes through an official public API intended for exactly this purpose (powering careers pages and job boards). It collects no personal data — only public job postings.

**How many companies can I scrape in one run?**
There's no hard limit — one request per company means even hundreds of boards complete in minutes. For very large sweeps, split the list across scheduled runs.

**Can it monitor new job postings on a schedule?**
Yes — schedule the Actor in Apify Console (hourly, daily, weekly) and connect the dataset to Sheets, a webhook, Slack or your ATS. `sourceId` is stable per posting, so downstream dedup across runs is trivial.

**What if a company uses Lever or Ashby instead of Greenhouse?**
Use our [ATS Jobs Scraper — Greenhouse, Lever, Ashby & SmartRecruiters](https://apify.com/fabrikit/ats-jobs-api): the same normalized schema across the four biggest ATS platforms, with auto-detection when you don't know which one a company uses.

**Does it include the full job description?**
Yes — set `includeDescription: true` and each item carries the full plain-text description (HTML stripped), ready for keyword filtering or LLM processing.

### Support

Found an issue or need a field this Actor doesn't return yet? Open an issue on the Actor's **Issues tab** — issues are answered in **less than 24 hours**, and reasonable feature requests usually ship within days.

### More scrapers by Fabrikit

- **[ATS Jobs Scraper — Greenhouse, Lever, Ashby & SmartRecruiters](https://apify.com/fabrikit/ats-jobs-api)** — need more than Greenhouse? The same normalized job schema across the four biggest ATS platforms, with ATS auto-detection and a remote-only filter.
- **[Google Play Reviews Scraper](https://apify.com/fabrikit/google-play-reviews-scraper)** — reviews for any Android app: rating, text, versions and developer replies.
- **[App Reviews Scraper — App Store & Google Play](https://apify.com/fabrikit/app-reviews-unified)** — reviews from both mobile stores in one run and one schema.
- **[Portal Inmobiliario Scraper — Chile Real Estate](https://apify.com/fabrikit/portal-inmobiliario-scraper)** — property listings from Chile's largest real estate marketplace.

### Technical details

- Data source (official, public, unauthenticated): `boards-api.greenhouse.io/v1/boards/<slug>/jobs?content=true`.
- Accepts bare slugs, `boards.greenhouse.io` / `job-boards.greenhouse.io` / EU-region URLs, and embed URLs (`?for=<slug>`).
- Items are deduplicated within a run by `company:sourceId`.
- Plain HTTP with a 30 s timeout per request; no headless browser, no proxy usage.
- A per-company run summary is stored in the key-value store under `SUMMARY`.
- Output schema is a strict subset of our [ATS Jobs Scraper](https://apify.com/fabrikit/ats-jobs-api)'s schema — you can switch or mix the two without changing downstream code.

# Actor input Schema

## `companies` (type: `array`):

One entry per company: a Greenhouse board slug (e.g. `stripe`) or any Greenhouse board URL (e.g. `https://boards.greenhouse.io/gitlab` or `https://job-boards.greenhouse.io/stripe`). The slug is the identifier in the company's careers URL.

## `maxJobsPerCompany` (type: `integer`):

Stop after this many jobs per company. 0 = no limit (full board).

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

Add the full plain-text job description to each item. Makes the dataset much larger.

## Actor input object example

```json
{
  "companies": [
    "duolingo",
    "https://boards.greenhouse.io/gitlab"
  ],
  "maxJobsPerCompany": 50,
  "includeDescription": false
}
```

# Actor output Schema

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

All Greenhouse job postings collected during the run

# 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 = {
    "companies": [
        "duolingo",
        "https://boards.greenhouse.io/gitlab"
    ],
    "maxJobsPerCompany": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("fabrikit/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 = {
    "companies": [
        "duolingo",
        "https://boards.greenhouse.io/gitlab",
    ],
    "maxJobsPerCompany": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("fabrikit/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 '{
  "companies": [
    "duolingo",
    "https://boards.greenhouse.io/gitlab"
  ],
  "maxJobsPerCompany": 50
}' |
apify call fabrikit/greenhouse-jobs-scraper --silent --output-dataset

```

## MCP server setup

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