Greenhouse API: pulling job postings from any Greenhouse-hosted career page
Greenhouse's Job Board API is free and public — but you need to know each company's board token. Here's the easier way: one endpoint, every Greenhouse tenant, the same JSON schema as every other source.
Eng team
Engineering
Greenhouse’s Job Board API is free and public. Hit https://boards-api.greenhouse.io/v1/boards/{board_token}/jobs and you get back a clean JSON list of every public job at that company. No auth required.
The problem isn’t the API — it’s the board_token. Each company has a different one. Stripe is stripe. Anthropic is anthropic. Notion is notion. But there’s no public directory of every Greenhouse-hosted board, and the list changes every week as companies onboard or churn.
The Greenhouse coverage problem
To pull jobs from any Greenhouse customer, you need to either:
- Maintain your own list of company → board_token mappings (we have ~12,000 today; it changes daily).
- Discover boards as you find companies of interest (slow, manual).
- Use a maintained index. That’s what JobsPipe does.
How to query Greenhouse through JobsPipe
# All jobs from a specific Greenhouse-hosted company
curl https://api.jobspipe.dev/v1/jobs \
-H "Authorization: Bearer $JOBSPIPE_KEY" \
-G \
-d "source=greenhouse" \
-d "company=anthropic"
# All Engineering jobs across every Greenhouse board
curl https://api.jobspipe.dev/v1/jobs \
-H "Authorization: Bearer $JOBSPIPE_KEY" \
-G \
-d "source=greenhouse" \
-d "department=engineering"What the official Greenhouse API doesn’t give you
- Parsed salary — Greenhouse returns the full description as HTML; you parse comp yourself. JobsPipe ships a structured
compensationobject on every job. - Normalized location — Greenhouse free-texts the location field. “Remote — US”, “NYC or Remote”, “London / Berlin (Hybrid)”. JobsPipe resolves these to city, country, lat/lng, and a remote flag.
- Cross-source dedup — the same job posted to Greenhouse and mirrored to Indeed shows up twice. JobsPipe merges them into one record with both source IDs preserved.
When to use the official Greenhouse API directly
If you only need jobs from a handful of specific companies and you’re happy parsing salary/location yourself, the direct Greenhouse API is great — free, no rate limit you’ll hit, no vendor needed. Use it.
If you need every Greenhouse-hosted company, normalized data, cross-source dedup, or webhook delivery, the math flips toward a managed source quickly.
Get Greenhouse jobs + 30 other sources from one endpoint.
Get a free API key