# Greenhouse Jobs API — Search All Greenhouse Job Boards (`factpipe/greenhouse-jobs-api`) Actor

Search open jobs on 3,600+ Greenhouse job boards (Stripe, Databricks, Anthropic…) by keyword, location, remote and department, or fetch any Greenhouse board live. Full descriptions. $2 per 1,000 jobs.

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

## Pricing

from $1.40 / 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.
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 Jobs API — Search All Greenhouse Job Boards

**Search open jobs on 3,600+ Greenhouse job boards (Stripe, Databricks, Anthropic…) by keyword, location, remote and department, or fetch any Greenhouse board live. Full descriptions. $2 per 1,000 jobs.**

| Title | Company | Department | Locations | Workplace |
|---|---|---|---|---|
| Staff Software Engineer | Robinhood | ENG Data and AI Platform Division | New York, NY | unknown |
| Sr. Staff Software Engineer, Browser (New Produ… | Mozilla | New Products | Remote Canada | remote |
| Senior Software Engineer | Xometry | Software Engineering | North Bethesda, Maryland | unknown |

*Real output from the “Software Engineer jobs on Greenhouse job boards” example, run on October 9, 2026.*

**Try a ready-made example:** [Software Engineer jobs on Greenhouse job boards](https://apify.com/factpipe/greenhouse-jobs-api/examples/greenhouse-software-engineer-jobs) · [Remote jobs on Greenhouse job boards (last 7 days)](https://apify.com/factpipe/greenhouse-jobs-api/examples/greenhouse-remote-jobs)

A **Greenhouse jobs API** and **Greenhouse job board scraper** in one: search every open job on **3,698 Greenhouse company job boards** (Stripe, Databricks, Anthropic, Datadog, Cloudflare, GitLab…) by keyword, location, remote, department and posting date, and get flat, deduplicated JSON: title, department, locations, country codes, remote flag, apply link and full description. Paste any Greenhouse board URL ("https://job-boards.greenhouse.io/gitlab") to fetch it live. **$2 per 1,000 jobs**, and you pay only for the jobs you get.

### Quick start

1. Click **Start** with the prefilled input: `keywords: ["software engineer"]`, `maxResults: 20`, `maxPerCompany: 3`. The run usually takes under a minute.
2. You get the 20 most relevant Greenhouse jobs for "software engineer" (backend, frontend, machine learning, platform…), at most 3 per company: jobs with the keyword in the title come first, newest first among equals.
3. That first run costs at most **$0.04 (20 jobs × $0.002)**, which fits in Apify's free monthly credit. Then name the companies you track (`companies: ["Stripe", "Datadog"]`), add `locations` or `remote`, or paste board URLs in `companyUrls`.

### What you get

One flat record per job opening, from a real run:

```json
{
  "job_id": "greenhouse:coinbase:8174232",
  "title": "Senior Software Engineer, Backend/Fullstack (Coinbase Advisor - Agentic Trading)",
  "company_name": "Coinbase",
  "company_board": "coinbase",
  "ats": "greenhouse",
  "department": "Engineering",
  "team": null,
  "employment_type": null,
  "workplace_type": "remote",
  "locations": [
    "Remote - USA"
  ],
  "country_codes": [
    "US"
  ],
  "remote": true,
  "salary_min": null,
  "salary_max": null,
  "salary_currency": null,
  "salary_period": null,
  "posted_at": "2026-10-08T23:50:37.000Z",
  "updated_at": "2026-10-08T23:50:38.000Z",
  "apply_url": "https://www.coinbase.com/careers/positions/8174232?gh_jid=8174232",
  "job_url": "https://www.coinbase.com/careers/positions/8174232?gh_jid=8174232",
  "description_text": "Ready to do the most impactful work of your career? At Coinbase, we…",
  "description_snippet": "Ready to do the most impactful work of your career? At Coinbase, we are uncompromising on our mission to increase economic freedom. The bar…",
  "description_status": "included",
  "duplicate_sources": [],
  "match_score": 100,
  "matched_in": "title",
  "source_url": "https://boards-api.greenhouse.io/v1/boards/coinbase/jobs?content=true",
  "fetched_at": "2026-10-09T03:18:53.181Z"
}
```

- Greenhouse's job-board API has no employment type or pay range, so `employment_type` and the `salary_*` fields are always `null` here. They are never guessed. `posted_at` is the job's first publication date.
- `match_score` (0–100) and `matched_in` (`title`, `department`, `description`) explain keyword matches. Both are `null` without keywords.
- `duplicate_sources` lists other `job_id`s of the same opening (for example a company with two boards). Each opening is delivered and charged once.
- **No personal data.** Recruiter and hiring-manager fields are never copied, and contact details in descriptions are replaced with `[… redacted]`.

### Use cases

- **Greenhouse API without integration work**: one call returns jobs from thousands of Greenhouse boards in one flat schema, instead of polling `boards-api.greenhouse.io` board by board.
- **Greenhouse job board scraper for aggregators**: feed a niche job board with Greenhouse jobs filtered by keyword, location and department, refreshed daily with `sinceLastRun: true`.
- **Tracking specific companies**: `companies: ["Stripe", "Datadog"]`, scheduled daily, to see new Greenhouse openings as they appear.
- **Recruiting and sales intelligence**: who is hiring which team, and where. For one row per company, see [Companies Hiring](https://apify.com/factpipe/companies-hiring).

### Input

| Field | Type | Notes |
|---|---|---|
| `keywords` | string\[] | Case-insensitive. Title matches rank first, then department/team, then description (first ~1,500 characters) |
| `keywordMatch` | `any` | `all` | Default `any` |
| `keywordScope` | `title` | `title_and_description` | Default `title_and_description` |
| `companies` | string\[] | Company names (`Stripe`) or Greenhouse board tokens (`stripe`). Empty = every Greenhouse company in the index |
| `excludeKeywords` | string\[] | Drops jobs whose title contains any of them |
| `locations` | string\[] | Location text as written in the posting, or an ISO country code (`US`, `DE`) |
| `remote` | `any` | `remote_only` | `onsite_only` | Default `any` |
| `postedWithinDays` | integer | First published within the last N days |
| `departments` | string\[] | Substring match on department or team |
| `employmentTypes` | string\[] | `full_time`, `part_time`, `contract`, `temporary`, `internship`, `other`. Greenhouse's job-board API does not state an employment type, so Greenhouse jobs have none and are excluded when this is set. |
| `maxResults` | integer | Default 100 |
| `maxPerCompany` | integer | Optional cap on jobs from any one company (prefill 3), so a single employer posting many near-identical roles can't fill your results |
| `includeDescription` | boolean | Default `true`: full description fetched live from Greenhouse for each delivered job |
| `sinceLastRun` | boolean | Only jobs not delivered by an earlier run with the same filters |
| `companyUrls` | string\[] | **Live mode**: Greenhouse board URLs or tokens, fetched directly from Greenhouse. URLs of other platforms are ignored with a warning |

**Greenhouse board references accepted in live mode:**

| Form | Example |
|---|---|
| Board page | `https://job-boards.greenhouse.io/gitlab`, `https://boards.greenhouse.io/gitlab` |
| Embedded board | `https://boards.greenhouse.io/embed/job_board?for=gitlab` |
| API URL | `https://boards-api.greenhouse.io/v1/boards/gitlab` |
| Token | `gitlab` or `greenhouse:gitlab` |

**How it works.** Without `companyUrls`, the Actor searches a compact search index of every Greenhouse board in our directory, rebuilt daily from Greenhouse's public API, and downloads only the Greenhouse parts of it for your date range. With keywords, it ranks every matching job before delivering the top `maxResults`. For each delivered job it then fetches the full description live from Greenhouse (one API call per company), which also drops jobs closed since the nightly build (not delivered, not charged).

### Pricing (pay per event)

| Event | Price | Meaning |
|---|---|---|
| `job-result` | **$2.00 per 1,000** ($0.002 each) | One job delivered. **No start fee.** Runs with no matches, jobs skipped by `sinceLastRun`, jobs found closed and failed boards are never charged. |

Set a maximum charge per run in Apify, and the Actor stops cleanly when it is reached.

### Coverage

Search-index build of 2026-10-09: **148,132 open jobs** on **3,698 Greenhouse company job boards**, including Stripe, Databricks, Anthropic, Datadog, Cloudflare, GitLab.

Boards were discovered from Common Crawl's public URL index and validated against Greenhouse's API. Every indexed board had at least one open job when last checked. A company that isn't indexed yet works in live mode through `companyUrls`.

### Sources and terms

Only Greenhouse's official, public, unauthenticated [Job Board API](https://developers.greenhouse.io/job-board.html), which Greenhouse publishes for displaying and syndicating open jobs: "Job Board data is publicly available"; no authentication for GET. No career-site HTML scraping, no logins, no LinkedIn or Indeed.

### factpipe Jobs Data

All of these Actors search the same daily index of open jobs from 10,000+ company job boards:

- [Jobs Feed API](https://apify.com/factpipe/ats-jobs-feed): every job from every platform, every filter, ranked by relevance.
- [Greenhouse, Lever & Ashby Jobs Scraper](https://apify.com/factpipe/ats-jobs-scraper): pick several applicant tracking systems (also Workable and Recruitee) in one run.
- [Remote Jobs API](https://apify.com/factpipe/remote-jobs-feed): remote and work-from-home jobs only, filtered by region or time zone.
- [Companies Hiring](https://apify.com/factpipe/companies-hiring): one row per company that is hiring for a role, as sales leads or market research.
- [Greenhouse Jobs API](https://apify.com/factpipe/greenhouse-jobs-api) (this Actor): every Greenhouse job board in one search.
- [Lever Jobs API](https://apify.com/factpipe/lever-jobs-api): every Lever job board, with salary where published.
- [Ashby Jobs API](https://apify.com/factpipe/ashby-jobs-api): every Ashby job board: startup and AI jobs, with salary where published.
- [Workday Jobs API](https://apify.com/factpipe/workday-jobs-api): every Workday career site in our directory (large employers), or any Workday site live.

### FAQ

**Do I need a Greenhouse account or API key?**
No. This is the public job-board API that powers each company's Greenhouse careers page. No key, no login.

**How do I find a company's board token?**
It is the last part of the careers-page URL: `job-boards.greenhouse.io/`**`gitlab`**. Or just type the company name in `companies`.

**How fresh is the data?**
The index is rebuilt daily. With `includeDescription` on (the default), every delivered job is re-checked live against Greenhouse during your run. Live mode (`companyUrls`) always reads Greenhouse directly.

**Why is there no salary or employment type on Greenhouse jobs?**
Greenhouse's public job-board API does not include pay ranges or employment types. We never extract or estimate them from free text. For pay data, [Lever Jobs API](https://apify.com/factpipe/lever-jobs-api) and [Ashby Jobs API](https://apify.com/factpipe/ashby-jobs-api) return the ranges employers publish.

**What happens to Lever, Ashby, Workable, Recruitee or Workday URLs?**
They are ignored with a warning in the log, and the rest of the run goes ahead. If no Greenhouse board is left, the run ends successfully with a message and nothing is charged. For several platforms in one run, use [Greenhouse, Lever & Ashby Jobs Scraper](https://apify.com/factpipe/ats-jobs-scraper).

**Switching from ats-jobs-scraper or other Greenhouse scrapers?**
Inputs from [ats-jobs-scraper](https://apify.com/factpipe/ats-jobs-scraper) work as they are: the same fields minus `ats` (ignored if present, the platform is always Greenhouse), and the same output records. Only `companyUrls` of other platforms are skipped. From other tools, this field map covers the usual settings:

| You want | Use here |
|---|---|
| Company name, board token or board URL | `companies` (index) or `companyUrls` (live) |
| Job title / search query | `keywords` (+ `keywordScope: "title"` for titles only) |
| Location or country | `locations` (text or ISO code) |
| Remote only | `remote: "remote_only"` |
| Date posted | `postedWithinDays` |
| Result limit | `maxResults` |
| Job description | `includeDescription` → `description_text` |
| Job id / URL / apply link | `job_id` / `job_url` / `apply_url` |
| Company / location / date | `company_name` / `locations` / `posted_at` |

**Can I call it from Python, JavaScript, Make, Zapier or an AI agent?**
Yes, through the Apify API, the official clients, Apify integrations (Make, Zapier, n8n, Google Sheets, Slack) or the Apify MCP server.

### Reliability

Official Greenhouse API only. Retries with backoff, per-host rate limits, a `RUN_SUMMARY` record on every run, and a built-in live fallback if the search index is ever unreachable.

# Actor input Schema

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

Optional: only these companies, by name ("Stripe") or Greenhouse board token ("stripe"). Empty = every company with a Greenhouse job board in the index.

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

Words or phrases to find (case-insensitive). A title matches at a word start ("engineer" matches "Engineering Manager"); description matching needs every word of the keyword, and covers the first ~1,500 characters. Results are ranked: title matches first. Leave empty for all jobs, newest first.

## `keywordMatch` (type: `string`):

"any": a job needs at least one keyword. "all": a job needs every keyword.

## `keywordScope` (type: `string`):

title: keywords must appear in the job title. title_and_description: in the title, or (every word of the keyword) in the department, team or the first ~1,500 characters of the description.

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

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

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

City, state, country or region as written in the posting (e.g. "Berlin", "California", "Remote (EU)"), or a 2-letter ISO country code (e.g. "US", "DE"). A job matches if any location matches.

## `remote` (type: `string`):

remote_only: remote jobs only. onsite_only: excludes jobs marked remote (on-site, hybrid and unspecified remain).

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

Only jobs first published in the last N days. Empty = any age.

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

Substring match on department or team, e.g. "engineering", "sales".

## `employmentTypes` (type: `array`):

Greenhouse's job-board API does not state an employment type, so Greenhouse jobs have none and are excluded when this is set.

## `maxResults` (type: `integer`):

Maximum number of jobs to return (and charge for). With keywords the most relevant jobs come first (title matches before department and description matches); without keywords the newest.

## `maxPerCompany` (type: `integer`):

Cap on jobs returned from any single company, so one employer posting many near-identical roles can't fill your results. Empty = no cap.

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

Fetch the full plain-text description (HTML stripped, contact details redacted, max 20,000 characters) live from the company's ATS for every delivered job. Adds a few seconds per company. A 300-character snippet is always included.

## `sinceLastRun` (type: `boolean`):

Incremental feed: remembers delivered jobs per filter combination (in a named key-value store in your account) and returns only jobs posted since, so a scheduled run never re-delivers or re-charges a job.

## `companyUrls` (type: `array`):

Optional. Fetch these Greenhouse boards live instead of searching the index, e.g. https://job-boards.greenhouse.io/gitlab, https://boards.greenhouse.io/stripe or just the board token "stripe". URLs of other platforms (Lever, Ashby, Workable, Recruitee or Workday) are ignored with a warning: use ats-jobs-scraper for those. All filters above still apply.

## Actor input object example

```json
{
  "keywords": [
    "software engineer"
  ],
  "keywordMatch": "any",
  "keywordScope": "title_and_description",
  "remote": "any",
  "maxResults": 20,
  "maxPerCompany": 3,
  "includeDescription": true,
  "sinceLastRun": false
}
```

# Actor output Schema

## `resultsDatasetUrl` (type: `string`):

No description

## `runSummary` (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 = {
    "keywords": [
        "software engineer"
    ],
    "maxResults": 20,
    "maxPerCompany": 3
};

// Run the Actor and wait for it to finish
const run = await client.actor("factpipe/greenhouse-jobs-api").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 = {
    "keywords": ["software engineer"],
    "maxResults": 20,
    "maxPerCompany": 3,
}

# Run the Actor and wait for it to finish
run = client.actor("factpipe/greenhouse-jobs-api").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 '{
  "keywords": [
    "software engineer"
  ],
  "maxResults": 20,
  "maxPerCompany": 3
}' |
apify call factpipe/greenhouse-jobs-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,factpipe/greenhouse-jobs-api"
        }
    }
}
```

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/LBYabmq0lPOUi2DAf/builds/QXWugMDo7ETekdYC8/openapi.json