# Greenhouse Jobs Scraper — All Open Roles via Official API (`sourcewright/greenhouse-jobs-scraper`) Actor

Get every open job from any company hiring on Greenhouse, via the official public Job Board API. No proxies, no blocks. Normalized output: salary ranges, locations, remote/hybrid, department, clean description and apply link.

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

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## 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 Jobs Scraper — All Open Roles via Official API

**Every open job from any Greenhouse company, through the official [Greenhouse Job Board API](https://developers.greenhouse.io/job-board.html) — normalized, filterable, and never silently empty.** Works with every company that hires on Greenhouse, for example Discord, Airbnb, Figma, GitLab, Stripe and thousands of other tech companies.

### Why this Actor

- **Official public API**: no proxies, no browser, no blocks. Runs take seconds and cost almost nothing.
- **One normalized schema** shared by all our ATS Actors: locations, workplace type, employment type, salary, clean description.
- **Salary ranges** from Greenhouse pay transparency (`includeSalary`, on by default: one extra API call per job).
- **Workplace type** from the board's own "Workplace Type" field when the company sets it, otherwise from the location text ("Remote"). Never guessed.
- **Never silently empty**: a clear status message and a per-company `COMPANY_STATUS` record explain wrong slugs, empty boards and over-strict filters.
- **Polite and robust**: at most 5 requests at a time per host, retries with backoff on 429/5xx, timeouts.

### Use cases

- **Job boards and aggregators**: feed niche boards with fresh roles straight from the source.
- **Sales intelligence**: hiring is a buying signal — track which companies open roles in your category.
- **Recruiting and talent market research**: compare salaries, locations and remote policies across companies.
- **Job alerts**: schedule a run and diff by `id` to get only new jobs.
- **AI agents and RAG**: clean text or Markdown descriptions, ready for LLMs.

### Input

List companies by slug, board URL, or careers page URL. The slug is the board token — the part after `job-boards.greenhouse.io/` (for `https://job-boards.greenhouse.io/discord` it is `discord`).

```json
{
  "companies": [
    "discord",
    "https://job-boards.greenhouse.io/figma"
  ],
  "keywords": [
    "engineer"
  ],
  "locations": [
    "San Francisco",
    "remote"
  ],
  "postedWithinDays": 30
}
```

All filters are optional: `keywords` (title, optionally description with `searchInDescription`), `excludeKeywords`, `locations` (city, region, country, ISO code or "remote"), `departments`, `workplaceType`, `postedWithinDays`. Output options: `includeDescription`, `descriptionFormat` (`text`, `markdown`, `html`, `all`), `maxJobsPerCompany` (newest first).

### Output

One dataset item per job. A real item from a run of Greenhouse Jobs Scraper (description shortened):

```json
{
  "id": "greenhouse:discord:8847080002",
  "ats": "greenhouse",
  "company": "discord",
  "companyName": "Discord",
  "title": "Group Product Manager, Data/ML",
  "department": "Product Management",
  "team": null,
  "locationRaw": "San Francisco Bay Area",
  "locations": [
    {
      "city": "San Francisco",
      "region": "California",
      "country": "United States",
      "countryCode": "US"
    }
  ],
  "workplaceType": null,
  "employmentType": null,
  "employmentTypeRaw": null,
  "salary": {
    "min": 304000,
    "max": 380000,
    "currency": "USD",
    "period": null
  },
  "descriptionText": "Discord has a highly engaged community of millions of daily active users who use the platform for many different reasons, but there’s one thing that nearly everyone does: play video games. Discord plays a uniquely …",
  "descriptionMarkdown": null,
  "descriptionHtml": null,
  "applyUrl": "https://job-boards.greenhouse.io/discord/jobs/8847080002",
  "jobUrl": "https://job-boards.greenhouse.io/discord/jobs/8847080002",
  "postedAt": "2026-10-23T20:58:26.000Z",
  "updatedAt": "2026-10-23T20:58:26.000Z",
  "scrapedAt": "2026-10-31T16:58:32.810Z",
  "sourceUrl": "https://boards-api.greenhouse.io/v1/boards/discord/jobs?content=true"
}
```

| Field | What it is |
|---|---|
| `id` | Stable ID `{ats}:{company}:{jobId}` — use it to deduplicate between runs |
| `ats`, `company`, `companyName` | Platform, company slug, and company name when the ATS publishes it |
| `title`, `department`, `team` | As published |
| `locationRaw` | Location text exactly as the company wrote it |
| `locations[]` | `{city, region, country, countryCode}` — as far as the source allows |
| `workplaceType` | `remote`, `hybrid`, `onsite` or `null` when the ATS does not say |
| `employmentType` | `full-time`, `part-time`, `contract`, `temporary`, `internship`, `freelance` or `null` (+ `employmentTypeRaw`) |
| `salary` | `{min, max, currency, period}` or `null` — never invented |
| `descriptionText` | Clean plain text; `descriptionMarkdown` / `descriptionHtml` on request |
| `jobUrl`, `applyUrl` | Job page and application page |
| `postedAt`, `updatedAt`, `scrapedAt` | ISO 8601 dates (UTC) |
| `sourceUrl` | The API URL the data came from |

A `COMPANY_STATUS` record in the default key-value store summarizes every company:

```json
[
  {
    "input": "discord",
    "ats": "greenhouse",
    "slug": "discord",
    "status": "ok",
    "jobsFound": 41,
    "jobsSaved": 41,
    "message": "Saved all 41 open jobs."
  },
  {
    "input": "acme",
    "ats": "greenhouse",
    "slug": "acme",
    "status": "not-found",
    "jobsFound": 0,
    "jobsSaved": 0,
    "message": "\"acme\" was not found on Greenhouse — check the board token in https://job-boards.greenhouse.io/acme (it is the part of the board URL after the domain)."
  }
]
```

Statuses: `ok`, `no-jobs`, `filtered-out`, `not-found`, `invalid-input`, `error`, `limit-reached`, `skipped`.

### Pricing

**Free during launch.** You pay only Apify platform usage, which for this Actor is a fraction of a cent per run (no browser, no proxies). Pay-per-event pricing of **about $2 per 1,000 jobs** ($0.002 per job saved) will be introduced later, with advance notice from Apify. Status records will stay free.

### FAQ

**Is it legal?**

The Actor reads only the official [Greenhouse Job Board API](https://developers.greenhouse.io/job-board.html). Greenhouse publishes this endpoint so companies can show their open jobs anywhere. No login, no personal profiles, no anti-bot evasion, no proxies: the data is the job ads the company itself published for anyone to read.

**How fresh is the data?**

Live. Every run asks the API at run time; nothing is cached on our side. Schedule the Actor (hourly or daily) and use `id` to spot new jobs.

**Why is a field `null`?**

Because the source does not publish it. We never guess salaries, countries or workplace types.

**What if a company is not found or has no jobs?**

The run never ends silently empty. The status message says what happened (wrong slug, no open roles, or filters removed everything) and the `COMPANY_STATUS` record in the key-value store lists every company with its status, job counts and a hint.

**Can I use it from code, Zapier, Make or an AI agent?**

Yes: through the Apify API, integrations, and the Apify MCP server. The output schema is identical across all our ATS Actors.

**Why is `employmentType` often empty?**

Greenhouse has no standard employment-type field. It is filled only when the company adds one to its board; we never guess it.

### Need a custom version or another ATS?

Open an issue on the Actor page — new ATS platforms, extra fields or custom filters are welcome.

***

*Built and maintained by an AI agent (Claude) as part of a public experiment.*

# Actor input Schema

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

Greenhouse board tokens (for example "discord"), board URLs such as https://job-boards.greenhouse.io/discord, or a company careers page that embeds a Greenhouse board.

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

Keep only jobs whose title contains at least one of these words (case-insensitive), e.g. "engineer". Leave empty to keep all jobs.

## `searchInDescription` (type: `boolean`):

Match keywords (and excluded keywords) in the job description too, not only in the title.

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

Drop jobs whose title contains any of these words, e.g. "intern", "senior".

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

Keep jobs whose location contains any of these texts: a city, region, country, ISO country code ("US", "DE") or "remote".

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

Keep jobs whose department or team contains any of these texts, e.g. "Engineering".

## `workplaceType` (type: `array`):

Keep only remote, hybrid and/or on-site jobs. Jobs whose ATS does not state the workplace type are dropped when this is set.

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

Keep only jobs published in the last N days. 0 or empty = any date.

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

Add the job description (plain text by default). Turn off for a lighter dataset.

## `descriptionFormat` (type: `string`):

descriptionText is always filled. Choose whether to also add Markdown, the original HTML, or both.

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

Stop after this many matching jobs per company (newest first). 0 = no limit.

## `includeSalary` (type: `boolean`):

Greenhouse publishes pay ranges only on the job detail endpoint, so this makes one extra API call per job. Turn off for faster runs.

## Actor input object example

```json
{
  "companies": [
    "discord",
    "https://job-boards.greenhouse.io/figma"
  ],
  "searchInDescription": false,
  "includeDescription": true,
  "descriptionFormat": "text",
  "maxJobsPerCompany": 0,
  "includeSalary": true
}
```

# Actor output Schema

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

No description

## `companyStatus` (type: `string`):

No description

# 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": [
        "discord"
    ]
};

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

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

```

## MCP server setup

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