Every open job on a company's Greenhouse job board as JSON: titles, locations, departments, full descriptions
- endpoints
- 2
- credit per call
- 1
The Greenhouse Jobs API returns every open job on a company's Greenhouse job board (boards.greenhouse.io/<token> and job-boards.greenhouse.io) as JSON: id, title, link, location and office list, department, requisition id, posted date, updated date, apply link and the full description as HTML and plain text, plus the pay range when the posting prints one.
/greenhouse/v1
- POST/greenhouse/v1/company_jobs1 credit
- POST/greenhouse/v1/job_detail1 credit
1 credit per call≈ $1/1,000 calls1,000 free credits, no card
Get a free API keyRun the call yourself, on the real endpoint
Change a parameter and press Try it. The response on the right is what your code will receive.
Greenhouse Jobs API
2 of 2 endpoints, ready to run
Every open job on one company's Greenhouse board, full descriptions included, in one call
// Press "Try it" and this pane shows exactly what the // live site returned this second — including an empty // result, if that is the truth. No key, no account.
What Greenhouse Jobs endpoints does ReefAPI ship?
2 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
company_jobs
1 crEvery open job on one company's Greenhouse board → jobs[] (id, title, url, company, location,…
- required
- company
- optional
- limit, cursor, page
job_detail
1 crOne Greenhouse posting in full by company + job_id.
- required
- company, job_id
- optional
- —
Every parameter, every allowed value →
Missing a Greenhouse Jobs endpoint, or need a source we don't have yet?Contact us real people · same-day reply.How the Greenhouse Jobs API works
Greenhouse Jobs is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 746 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and nothing is cached: every call reads the source live.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
From a company's Greenhouse board to every open role with dates and pay
Read the whole board once, then open single postings when you need them again. Old POST /ats-jobs/v1/... calls keep working unchanged; the call for Greenhouse on its own is POST /greenhouse/v1/<action>.
{"company": "gitlab"}On 2026-11-21 GitLab's board held 246 open jobs; 25 came back in 1.6 seconds with limit 25. Each row has title, link, location, locations, department, requisition id, posted and updated dates, apply link and the full description.
{"company": "gitlab", "job_id": "8638232002"}One posting in full. A job id works only while the role is open: of 3 older ids sent by a customer, 2 answered and 1 was NOT_FOUND because the role had closed.
The company's own list of open roles, with requisition ids, posted and updated dates, departments, locations, full descriptions and the pay range where the posting prints one.
curl -X POST https://api.reefapi.com/greenhouse/v1/company_jobs \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"company":"gitlab"}'{
"ok": true,
"data": { … },
"meta": {
"api": "greenhouse",
"endpoint": "company_jobs",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}What a Greenhouse job field contains
Fields that read differently from how they look. Each row was measured on GitLab's Greenhouse board through this API on 2026-11-21.
| Field | What it holds |
|---|---|
| company (request) | The board token from the board's own link (gitlab in boards.greenhouse.io/gitlab), not the brand name. A pasted Greenhouse link is accepted. A wrong token answers NOT_FOUND. |
| id | Greenhouse's numeric job id as a string (8638232002). Valid only while the role is open. |
| company (response) | The board's display name as Greenhouse prints it (GitLab); company_slug holds the token. |
| location, locations, location_parsed | location is the employer's text ("Remote, Canada; Remote, United States"), locations the office names, location_parsed the city, region and country. |
| requisition_id | The employer's own requisition number (6682). Present on 20 of 20 GitLab rows. |
| posted_date, updated_date | Separate ISO-8601 timestamps with the board's time-zone offset: posted 2026-07-22T13:38:40-04:00, updated 2026-11-06T15:25:07-05:00. |
| salary | min, max, currency and source description: read from the posting text, because Greenhouse has no pay field. 8 of the first 20 GitLab rows. |
| employment_type | Filled only when the employer adds an employment-type field to its Greenhouse jobs. Empty on all 20 GitLab rows. |
count is the number of rows in the response, total the number of open jobs on the board (25 and 246 for GitLab with limit 25).
What a Greenhouse board returns, measured
Every number below was read through this API on 2026-11-21.
GitLab: 246 open jobs on the board. company_jobs returns the whole board without paging; limit caps how many rows come back. A second board (PagerDuty) returned 48 jobs.
On the first 20 GitLab rows: title, link, location, locations, department, requisition id, posted date, updated date, apply link and full description (6,762 to 9,377 characters of text) on 20 of 20; workplace remote on 19 of 20.
Greenhouse has no salary field. salary is read from the posting text when it prints a range: 8 of the first 20 GitLab rows, e.g. USD 139,200 to 235,200.
posted_date and updated_date are separate timestamps with the board's time-zone offset (2026-07-22T13:38:40-04:00 posted, 2026-11-06 updated), so a re-posted role can be told from a new one.
location is the employer's text ("Remote, Canada; Remote, United States"), locations the office list, location_parsed the city and country. GitLab's rows covered the United States, Canada, the United Kingdom, Poland, Ireland and Spain.
employment_type was empty on all 20 GitLab rows (Greenhouse only has it when the employer adds it as a custom field). No recruiter or hiring-manager names, no applicant data. Greenhouse has no cross-company search: you need the company's board token.
What people build with Greenhouse Jobs
The jobs this data is most often used for.
Track new openings at a list of target companies straight from their Greenhouse boards, with the requisition id and posting date.
Build a job board or alert from employers' own Greenhouse listings, with the employer's apply link.
Measure a company's hiring by department and location from its open roles.
Collect the pay ranges US employers print in their Greenhouse postings.
endpoints
credit per call
What Greenhouse Jobs data costs
The cheapest call here is 1 credit, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
- 1,000 free credits on signup, no card
- One key, all 746 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/greenhouse/v1/company_jobs \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"company":"gitlab"}'import os
import requests
REEF_KEY = os.environ["REEF_KEY"]
r = requests.post(
"https://api.reefapi.com/greenhouse/v1/company_jobs",
headers={"x-api-key": REEF_KEY},
json={
"company": "gitlab"
},
timeout=90,
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Greenhouse Jobs.
Is there a Greenhouse API?▾
Yes. The greenhouse API on ReefAPI returns every open job on a company's Greenhouse board as JSON, with full descriptions, requisition ids and both dates, in the same shape as the Lever, Ashby and Workable APIs. Greenhouse's own job board API is public and needs no key for reading a board. The call is POST /greenhouse/v1/<action>; old POST /ats-jobs/v1/... calls with ats greenhouse keep working unchanged.
What do I pass as company?▾
The board token: the name in the board's link, gitlab in boards.greenhouse.io/gitlab. It is often the company name in lower case, but not always. A wrong token answers NOT_FOUND rather than another company's jobs.
How many jobs come back per call?▾
The whole board. company_jobs has no paging: GitLab's 246 open jobs come back in one call, and limit (1 to 2,000) caps how many rows you take.
Does it return salaries?▾
When the posting prints them. Greenhouse has no salary field; salary is read from the text and was present on 8 of the first 20 GitLab jobs on 2026-11-21, e.g. USD 139,200 to 235,200.
Can I search across all Greenhouse companies?▾
No. Greenhouse publishes one board per company and no cross-company index, so you need each company's board token. For a keyword search across companies, the workable API searches every company hiring on Workable.
Why does job_detail say NOT_FOUND for an id I saved?▾
The role has closed. A Greenhouse job id is valid only while the posting is open: of 3 older ids a customer sent on 2026-11-21, 2 answered and 1 had closed. Call company_jobs for current ids.
Can I tell a re-posted job from a new one?▾
Yes. posted_date and updated_date are separate timestamps; GitLab's AI Transformation Owner role was posted on 2026-07-22 and updated on 2026-11-06.
What is the Greenhouse Jobs API?▾
Greenhouse Jobs API is a ReefAPI endpoint group for every open job on a company's greenhouse board in one call: title, location, department, requisition id, posted and updated dates, full description. It returns live JSON through POST requests under /greenhouse/v1.
Is the Greenhouse Jobs API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Greenhouse Jobs calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Greenhouse Jobs login or account?▾
No login to Greenhouse Jobs is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Greenhouse Jobs data?▾
The page example is captured from a live company_jobs call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Greenhouse Jobs API use?▾
Greenhouse Jobs actions currently cost 1 credit per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call Greenhouse Jobs from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call greenhouse actions with the same key, credit pool and JSON envelope used by normal REST requests.
Is the Greenhouse Jobs API a Greenhouse Jobs scraper?▾
It is the managed alternative to a DIY Greenhouse Jobs scraper. Instead of building and maintaining your own scraper — proxies, headless browsers, captcha and constant breakage — you call one ReefAPI endpoint and get the same every open job on a company's greenhouse board in one call: title, location, department, requisition id, posted and updated dates, full description back as clean JSON.
36 Jobs & Hiring APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Greenhouse Jobs, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 745 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-11-21.