Greenhouse Jobs API - Career Site Job Board Scraper

Job postings pulled straight from company career sites running Greenhouse, with a verified directory of 3,584 Greenhouse boards included so you never have to guess a company's board slug.

Greenhouse publishes a meta.total count with every board, so completeness here is provable rather than asserted: each board is compared against the vendor's own number and the result is reported per board.

Why this exists

Most job data on the market is scraped from aggregators, where postings are reposted, stale, or routed through a third-party apply flow. These come from the employer's own Greenhouse board: one hop from the hiring team, with the employer's real apply URL.

Completeness is checked, not claimed

Greenhouse publishes a job count alongside its results. This Actor compares that number against the rows it actually returned, per board, and reports the outcome. When they disagree, the run says so.

What you get

Field	Meaning
company	Employer name
title	Role title
location	Location as the employer wrote it
department	Team or department, when the board exposes one
url	Direct apply URL on the employer's board
updated	Posting or last-updated timestamp from the vendor
board_token	The Greenhouse board identifier, reusable in later runs
job_id	Vendor's own job id
verified_complete	true, false, or null - see below

Every run also writes a PROVENANCE record to the key-value store: per board, how many postings were fetched, what count the vendor published, and whether the two matched.

verified_complete is three-valued on purpose

• true - the vendor published a count and our row count matched it.
• false - the vendor published a count and we did not match it. Something is wrong; the run tells you rather than hiding it.
• null - the vendor publishes no count. Honestly unknown.

Most job scrapers report only what they found. That is indistinguishable from a board that half-failed. A silent partial result is worse than an error, because you build on it.

Input

Option	What it does
companies	Company names. Resolved against the verified directory first, then live.
boards	Exact Greenhouse board tokens, if you already know them.
listKnownBoards	Return the whole verified directory of 3,584 boards instead of jobs.
allBoards	Sweep directory boards when no company is given.
keyword	Case-insensitive filter on job title.
maxBoards	Cap boards per run (default 25).
maxResults	Cap rows returned.

Start here

Set listKnownBoards to true. You get every Greenhouse board we have confirmed live, and can pick the companies you care about from real tokens instead of guessing.

Platform notes

Greenhouse serves a whole board in a single call and publishes the job count alongside it, which makes it the strongest platform on the store for verifiable completeness. Boards live on both boards.greenhouse.io and the newer job-boards.greenhouse.io; both are covered.

Where the directory comes from

Board tokens are harvested from public web crawl archives, then every one is re-checked against Greenhouse's own public API before it ships. A token that was seen once but no longer resolves does not make it in. Guessing company slugs instead was measured at a 0.77% hit rate; this approach measured about 67%.

To be exact about what the directory is: a board qualifies when it resolved and had at least one open role at validation time. A real board that happened to be empty that day is not in here. So treat the count as a floor, not a census.

Legal

This Actor reads Greenhouse's documented public job board endpoints - the same data any visitor sees without logging in. No login, no cookies, no terms accepted, no paywall or access control circumvented. Job postings are published by employers specifically to be seen.

Limits

• Coverage is the directory plus anything you name explicitly; it is not every Greenhouse board in existence, and this README says so rather than implying totals.
• updated is passed through from the vendor and means slightly different things on different platforms.
• Rate limits are the vendor's, not ours. Errors are reported per board.