Greenhouse jobs API

The most widely used of the twelve here, and the one whose listing endpoint hands back full descriptions in the same call. If you are building one integration and want it to cover the most employers, this is where to start.

The endpoint

GET https://boards-api.greenhouse.io/v1/boards/{company}/jobs?content=true

No key, no login. The slug is the path segment in job-boards.greenhouse.io/{company} — older boards still live at boards.greenhouse.io/{company}, same slug.

curl -s 'https://boards-api.greenhouse.io/v1/boards/acme/jobs?content=true'

What it returns, measured

Measured across every live Greenhouse board in our registry — 179,303 postings from 5,751 boards, not a sample. yes means 99.5% or more; no means the field does not exist on this endpoint.

Field	Greenhouse
Posting date	yes
Description	yes
Pay	no
Marked remote	no

Title, company, location and an apply URL come back on every row.

What it is good at

Descriptions come back on 100% of postings when you pass content=true, so a single request per board gives you a corpus you can search. Every posting is dated.

Where it falls short

No compensation field of any kind, and no work-arrangement field — remote can only be inferred from the location string. Employment type is absent too, so full-time versus contract is not distinguishable from this endpoint.

Mistakes that cost us time

content=true is not the default.: Without it you get titles and links only, and it is easy to conclude Greenhouse has no descriptions.
Two domains, one slug.: Boards moved from boards.greenhouse.io to job-boards.greenhouse.io. Both resolve, and the API host is a third name — boards-api.greenhouse.io.
Departments nest.: A posting carries an array of offices and departments rather than one string. Flattening to the first element loses information for employers who tag several.

So should you use it

Yes, for a broad, description-rich corpus across venture-backed and mid-market employers.

No, for anything about pay. Four platforms publish compensation and this is not one of them.

How Greenhouse compares with the other eleven on the same four fields is on the comparison page. If you would rather not write and maintain a client, this Actor reads Greenhouse and emits the same row shape as the other eleven, and ATS Database is a free lookup for finding which platform a given company is on.

Finding the boards

Greenhouse boards came almost entirely from the Common Crawl URL index — 2,996 on the first pass. Re-harvesting the same platform from the Wayback CDX index later added only 131 more from 3,268 candidates, a 4% yield. That number is the useful one: it says Greenhouse coverage is mature, and further sweeping is not where the remaining boards are. One notable hole survived both passes — Stripe, whose board answers fine but never appeared in either index. Famous companies are worth checking by hand.