</deriverge>

developer guide ยท checked 19 November 2026

Greenhouse Job Board API

Greenhouse publishes every job board through a read-only JSON API at boards-api.greenhouse.io. Our index calls it for 5,311 companies a day and holds 187,542 open Greenhouse jobs (20 November 2026).

the endpoint

The Greenhouse job board endpoint

GET https://boards-api.greenhouse.io/v1/boards/{board_token}/jobs

  • Authentication: none for GET requests. A key is needed only to submit applications through the API.
  • Format: JSON, an object with jobs and meta.total.
  • Pagination: none. One request returns every published job of the board.
ParameterWhat it does
content=trueadds the full job description (content, HTML-escaped), departments and offices to each job
pay_transparency=trueadds pay_input_ranges, the pay ranges the employer publishes. Documented for the single-job endpoint; the list accepted it too in our tests

Other endpoints of the same API:

  • GET /v1/boards/{board_token}/jobs/{job_id}: one job with its description; ?questions=true adds the application questions and ?pay_transparency=true the pay ranges
  • GET /v1/boards/{board_token}/departments: departments, each with its jobs (render_as=list or tree)
  • GET /v1/boards/{board_token}/offices: offices, each with its departments and jobs (render_as=list or tree)
  • GET /v1/boards/{board_token}: the board's name and intro text

Source: Greenhouse Job Board API documentation. Checked 19 November 2026.

try it

Request and response

The board of Stripe, a Greenhouse board from our index, as an example. Replace stripe with the board you need.

curl

curl "https://boards-api.greenhouse.io/v1/boards/stripe/jobs?content=true&pay_transparency=true"

Python

import html
import requests

r = requests.get(
    "https://boards-api.greenhouse.io/v1/boards/stripe/jobs",
    params={"content": "true", "pay_transparency": "true"},
    timeout=60,
)
r.raise_for_status()
for job in r.json()["jobs"]:
    description_html = html.unescape(job.get("content", ""))  # content arrives HTML-escaped
    print(job["id"], job["title"], job["location"]["name"], job["absolute_url"])

Response (shortened)

{
  "jobs": [
    {
      "id": 8172510,
      "internal_job_id": 3537063,
      "title": "Abuse Investigator",
      "company_name": "Stripe",
      "location": { "name": "Seattle, San Francisco, New York City" },
      "absolute_url": "https://stripe.com/jobs/search?gh_jid=8172510",
      "updated_at": "2026-11-19T12:12:24-05:00",
      "first_published": "2026-09-09T10:50:29-04:00",
      "language": "en",
      "content": "&lt;h2&gt;&lt;strong&gt;Who we are &lt;/strong&gt;&lt;/h2&gt;...",
      "departments": [{ "id": 81946, "name": "8611 Security Analytics" }],
      "offices": [{ "id": 65234, "name": "US" }],
      "pay_input_ranges": []
    }
  ],
  "meta": { "total": 771 }
}

the data

Fields of a job

FieldMeaning
idjob post ID; it is also the gh_jid in job links on the company's own site
internal_job_idID of the job behind the post; one job can have several posts
titlejob title
company_namethe board's company name (documented for the single-job endpoint, present in list responses too)
location.namelocation as one free-text string, often several cities
absolute_urljob page; points to the company's own careers site when the board is embedded there
first_published / updated_atwhen the post went live and when it last changed (first_published is documented for the single job)
contentdescription, HTML-escaped (only with content=true)
departments[] / offices[]department and office tree (only with content=true)
pay_input_ranges[]published pay ranges with min_cents, max_cents, currency_type and title (only with pay_transparency=true)

which board

Finding a company's board token

The board token is the last part of the board address: job-boards.greenhouse.io/stripe or boards.greenhouse.io/stripe means the token stripe. When a company embeds the board on its own site, the page loads boards.greenhouse.io/embed/job_board/js?for=<token> and job links end with ?gh_jid=<id>.

Our list of 5,597 companies using Greenhouse shows the careers address of each one, and the address contains the identifier. The list is free to search and download as CSV.

in practice

What we learned reading it every day

  • content is HTML with the tags escaped (&lt;p&gt;): unescape it once before you render or strip it.
  • With content=true a big board is several megabytes (Stripe: about 6 MB for 770 jobs). If you need only titles and locations, leave it off and call /departments for the department of each job.
  • Pay ranges are published by fewer than half of the employers, mostly for US jobs where pay transparency laws apply. When missing, pay_input_ranges is an empty list.
  • A board that no longer exists answers HTTP 404. A board with no openings answers 200 with an empty jobs list, so do not treat it as an error.
  • absolute_url often leads to the company's own careers site, not to Greenhouse. Use it as the apply link; it is what the employer wants candidates to open.

questions

Frequently asked questions

Does the Greenhouse job board API need an API key?

No. GET requests to the Job Board API need no key. Greenhouse uses keys only for posting applications through the API and for its Harvest API, which is for the employer's own data.

Is there a rate limit?

The documentation gives no number; it says requests may be rate limited for security and traffic reasons. One request per board returns everything, so a daily read of a board is a single call. Keep your request rate modest.

Can I get all Greenhouse jobs, from every company, at once?

No. The API answers for one company per request, and Greenhouse publishes no list of its customers. Our index reads 5,311 Greenhouse boards with open jobs every day (187,542 jobs on 20 November 2026); you can search all of them through our Apify actor or get them as a daily job data feed.

Is it allowed to use the Greenhouse job board API?

The API exists so that companies can show their jobs on their own sites and so that job boards can list them. It returns only what the employer has published. Read Greenhouse's documentation and terms for your use, keep request rates modest and link back to the original job for applications.

other systems

Public job APIs of other applicant tracking systems