Source · GreenhouseGreenhouse Jobs API.
Every public Greenhouse Job Board posting, one endpoint. No per-tenant Harvest API onboarding, no slug discovery.
Why people are confused about the Greenhouse API
Greenhouse ships two APIs that share a name. The Harvest API is private, OAuth-scoped, and exposes the full ATS surface - candidates, applications, scorecards, scheduled interviews. The Job Board API is public, unauthenticated, and exposes only the openings the customer has chosen to publish. Most developers searching 'Greenhouse API' land on Harvest docs and assume that's the only option, even though Job Board is what they actually need.
The Job Board endpoint lives at boards-api.greenhouse.io/v1/boards/<company>/jobs, but you still need to know each company's board token in advance, and many enterprises either disable the public board, use a vanity careers domain, or embed jobs through Greenhouse's iframe widget. JobsPipe indexes every public Greenhouse board it can identify and normalizes the data into the same JSON shape as every other source.
Works when the customer keeps a public board enabled and you already know their slug. There's no list endpoint to enumerate Greenhouse customers.
Required if you want applicants and pipeline state, not just postings. Each customer must mint you a Harvest key - does not scale to aggregation.
Every public Greenhouse board, one endpoint. Free tier covers 5,000 requests/month, no credit card.
Greenhouse API documentation
Greenhouse's developer documentation lives at developers.greenhouse.io. The Harvest API docs cover the OAuth-scoped private surface - candidates, applications, jobs (internal view), scorecards. The Job Board API docs at developers.greenhouse.io/job-board.html cover the unauthenticated public surface - published openings, departments, offices. The two are easy to confuse because both call themselves the 'Greenhouse API'. JobsPipe's normalized schema is documented at /docs and lines up with every other source, so you only learn one shape.
Greenhouse API key
The Greenhouse Job Board API does not require an API key - it's public by design. The Harvest API requires a key minted inside the customer's Greenhouse admin under Configure → Dev Center → API Credential Management. Job Board responses include only the fields a customer chose to publish; Harvest exposes the full record. JobsPipe never requests Harvest credentials and only consumes what the customer has already chosen to make public.
Greenhouse Job Board API
boards-api.greenhouse.io/v1/boards/<company>/jobs returns a JSON array of published openings for one Greenhouse customer, no authentication required. Useful when you know the board token (the customer's Greenhouse 'board name') and only need that one company. JobsPipe's value lives in the layer above: discovering board tokens across thousands of public Greenhouse customers, handling vanity careers domains, and normalizing the Job Board response into the same shape as Workday, Lever, Indeed, and 30+ other sources.
Sample request
curl "https://api.jobspipe.dev/v1/jobs?source=greenhouse" \
-H "Authorization: Bearer $JOBSPIPE_KEY" \
-H "Accept: application/json"Sample response
{
"id": "gh_NzM0NTY3ODktYW",
"source": "greenhouse",
"tenant": "stripe",
"title": "Software Engineer, Payments Infrastructure",
"company": "Stripe",
"location": {
"city": "New York",
"region": "NY",
"country": "US",
"remote": false
},
"salary": {
"min": 198000,
"max": 297000,
"currency": "USD",
"period": "year",
"source": "explicit"
},
"employment_type": "full_time",
"posted_at": "2026-05-12T16:04:00Z",
"expires_at": null,
"apply_url": "https://boards.greenhouse.io/stripe/jobs/...",
"description": "Stripe is hiring a Software Engineer on Payments Infrastructure to build and operate the systems that move money for businesses around the world ..."
}Every Greenhouse job record is returned in the same JSON shape as every other JobsPipe source. The full schema is documented in the docs.
Fields in every Greenhouse job record
FAQ
Greenhouse Harvest API vs Job Board API - which does JobsPipe use?+
JobsPipe consumes only public postings, equivalent to what the Job Board API surfaces. We never touch Harvest endpoints, so applicant data, scorecards, and pipeline state stay private to each customer's Greenhouse account.
Do I need a Greenhouse API key to use JobsPipe?+
No. The Greenhouse Job Board API is unauthenticated, and JobsPipe's index is built on top of public data. You only need a JobsPipe key.
How fresh is Greenhouse data on JobsPipe?+
Every public Greenhouse board is re-crawled at least every 24 hours; high-volume boards (over ~200 active postings) are refreshed every 6 hours.
Can I filter to one Greenhouse company?+
Yes. ?tenant=stripe filters results to Stripe's Greenhouse postings. Substitute any board token.
Try Greenhouse data free - 5,000 requests/month, no credit card.
Get a free API key