How to get all jobs from a Greenhouse board (no API key)
If you already have a company's Greenhouse board URL, you do not need to scrape the HTML. Greenhouse publishes a public Job Board API that returns every open job as JSON, and the list reques...
Résumé
If you already have a company's Greenhouse board URL, you do not need to scrape the HTML. Greenhouse publishes a public Job Board API that returns every open job as JSON, and the list request does not need an API key. The same idea works on Lever, Ashby, Workable, and SmartRecruiters, with slightly different URLs. This is useful when you want a spreadsheet, a daily "what's new" check, or a hiring-signal watch list. It is not a way to apply for jobs, and it only returns what the employer has already put on its public careers page. The short answer Find the board token in the company's Greenhouse URL (the airbnb in https://boards.greenhouse.io/airbnb), then call: curl "https://boards-api.greenhouse.io/v1/boards/airbnb/jobs" On November 20, 2026, at 10:44 AM CT (America/Chicago), that request returned HTTP 200 and meta.total of 200 open jobs. The jobs array also had 200 items. The first title in the list was "Account Executive (Hotels)", in Barcelona, Spain. Counts change as jobs open and close. The compact JSON body was 153,496 bytes. A short Python version of the same call: import requests url = "https://boards-api.greenhouse.io/v1/boards/airbnb/jobs" response = requests.get(url, timeout=60) response.raise_for_status() data = response.json() print("total:", data["meta"]["total"]) for job in data["jobs"][:3]: print(job["title"], "|", job["location"]["name"], "|", job["absolute_url"]) That script, run against the same response, printed: total: 200 Account Executive (Hotels) | Barcelona, Spain | https://careers.airbnb.com/positions/8365363?gh_jid=8365363 AirCover Specialist, Claims Experience | Japan | https://careers.airbnb.com/positions/8345532?gh_jid=8345532 Associate Legal Counsel, Japan | Tokyo, Japan | https://careers.airbnb.com/positions/7789554?gh_jid=7789554 Official docs: Greenhouse Job Board API (HTTP 200 today). On that page, Greenhouse says only the application submission endpoint (POST .../jobs/{id}) requires Basic Auth. The GET list call above did not ask for a key. 1. Get the board token The token is the last part of the hosted board URL: What you see Token to use https://boards.greenhouse.io/airbnb airbnb https://job-boards.greenhouse.io/airbnb airbnb Some companies use their own careers domain (for example careers.airbnb.com) and still run Greenhouse in the background. In that case, look in the page source for boards.greenhouse.io or boards-api.greenhouse.io, or for gh_jid in a job link. If you cannot find a token, the steps below will not work for that company, and you should not guess. Today, https://boards.greenhouse.io/airbnb redirected and landed on https://careers.airbnb.com/positions/ with HTTP 200. The API token is still airbnb. 2. Pull the list of jobs The list endpoint is: GET https://boards-api.greenhouse.io/v1/boards/{board_token}/jobs The official docs describe this as returning the list of all job posts, and they do not list a page or offset parameter. The Airbnb board came back in a single response today (200 in meta.total, 200 items in jobs). Add ?content=true only if you also need the HTML description, departments, and offices. That makes the response much larger. The JSON has a jobs array and a meta.total count. Each job includes id, title, location.name, updated_at, and absolute_url. With content=true, you also get departments, offices, and content (HTML). Greenhouse does not publish a standard remote flag. If you need "remote," you have to read it from the location text, the title, or, on some boards, custom fields in metadata. Those custom fields are not the same from company to company, so do not build around one board's labels. Other official list endpoints, from the same docs page: /v1/boards/{token}/jobs/{job_id} for one job, /departments and /offices for those breakdowns, and /v1/boards/{token} for the board itself. A 404 usually means the token is wrong, or the company has moved off Greenhouse. 3. Published pay ranges, when the company shares them The same docs page lists a pay_transparency=true query parameter. It adds a pay_input_ranges array to each job. curl "https://boards-api.greenhouse.io/v1/boards/airbnb/jobs?pay_transparency=true" On the Airbnb board today, that call was also HTTP 200, still with 200 jobs. 160 of those jobs had a non-empty pay_input_ranges array. The other 40 were empty. One example: "Brand Marketing Intern, France" listed a France annual pay range of 25,000 to 25,000 EUR (min_cents 2500000, max_cents 2500000). Treat those figures as what the board published today, not as a promise. 4. The same pattern on four other public boards These are the public JSON endpoints the employers already use to power their own careers pages. Each one was fetched on November 20, 2026, at 10:44 AM CT (America/Chicago), with no login and no API key. Only use a board you have a reason to read, and do not hammer the endpoints. ATS Example board Public JSON URL (verified HTTP 200 today) Open jobs today Official docs Greenhouse boards.greenhouse.io/airbnb (redirects; final HTTP 200 at careers.airbnb.com/positions/) https://boards-api.greenhouse.io/v1/boards/airbnb/jobs 200 (meta.total) docs.greenhouse.io/job-board.html (HTTP 200) Lever jobs.lever.co/palantir (HTTP 200) https://api.lever.co/v0/postings/palantir?mode=json 306 (top-level array length) github.com/lever/postings-api (HTTP 200). Lever's README says this API returns paginated postings, so a single unpaged call can truncate on very large boards. Palantir fit in one response today. Ashby jobs.ashbyhq.com/ramp (HTTP 200) https://api.ashbyhq.com/posting-api/job-board/ramp?includeCompensation=true 185 (jobs array) Ashby public job posting API (HTTP 200). includeCompensation=true is what adds pay ranges when the company publishes them. All 185 Ramp jobs today included a compensation object. Workable apply.workable.com/huggingface (HTTP 200) https://apply.workable.com/api/v1/widget/accounts/huggingface 10 (jobs array) The widget endpoint returned HTTP 200 and a job list today. Treat it as a public board feed. SmartRecruiters jobs.smartrecruiters.com/Ubisoft2 (HTTP 200) https://api.smartrecruiters.com/v1/companies/Ubisoft2/postings?limit=100&offset=0 230 (totalFound). This call returns 100 rows at a time, so you have to page with offset to get the rest. SmartRecruiters Posting API (HTTP 200) The SmartRecruiters identifier in the example is Ubisoft2, not Ubisoft. That product uses company-specific identifiers, and an unknown one can come back as an empty list instead of an error. Example for Lever, matching their docs' mode=json advice: curl "https://api.lever.co/v0/postings/palantir?mode=json" The first title in that response today was "Administrative Business Partner". 5. Keep only the new jobs A one-off list is the easy part. Tracking is a little more work: Save each job's id, plus the ATS and board name, so two boards cannot collide. On the next run, anything not in the saved list is new. Anything in the saved list that is gone from the board may be closed. Do not mark a board's jobs closed if the fetch failed, came back empty in a suspicious way, or (for SmartRecruiters) hit the page cap mid-board. A manual test run should not update the saved list, or you will train on incomplete data. For a handful of companies, a scheduled script or an n8n workflow with one HTTP Request node per ATS is enough. A tool we built, if the list gets long We built Company Jobs Tracker for the case where you have a list of companies, not one board, and you want hiring signals: new and closed jobs on a schedule. We are Hill Country Bots, and we should say that plainly. The live Store title, checked on November 20, 2026, at 10:43 AM CT (America/Chicago), is "Company Jobs Tracker: Hiring Signals from Greenhouse & Lever". It calls the same public endpoints above (Greenhouse, Lever, Ashby, Workable, SmartRecruiters). There is no browser and no login. The Store page returned HTTP 200 today. Live price, from the public Apify Actor API on November 20, 2026, at 10:43 AM CT: $0.0025 per open job returned and $0.001 per company checked. Closed-job rows are free. In tracking mode, later runs return and charge only jobs that are new since the last snapshot. The DIY calls above are free and are the right place to start. Use the tool if you would rather not keep five response shapes and a seen-list of your own. If you would rather call a hosted API, we also listed a Company Jobs API on RapidAPI. That listing URL returned HTTP 200 today. Check the public page for the current plan limits, because those can change. The Actor's public API description today lists Greenhouse, Lever, Ashby, Workable, and SmartRecruiters. Other applicant-tracking systems are outside that list. A longer version of this walkthrough, with the same method, is on our site: How to get all jobs from a Greenhouse board. Good to know These endpoints only return public postings. Unlisted jobs will not appear. The examples are real boards we checked today. Do not treat the job counts as permanent. Be polite: identify your client, cache results, and back off if you get an error. None of this is legal advice; check the terms that apply to you. We do not store personal data from these boards. Job descriptions can contain names, so if you save descriptions yourself, think about that first. Sources checked today Greenhouse Job Board API: https://docs.greenhouse.io/job-board.html (HTTP 200, November 20, 2026) Lever Postings API README: https://github.com/lever/postings-api (HTTP 200, November 20, 2026) Ashby public job posting API: https://developers.ashbyhq.com/docs/public-job-posting-api (HTTP 200, November 20, 2026) SmartRecruiters Posting API: https://developers.smartrecruiters.com/reference/posting-api-1 (HTTP 200, November 20, 2026) Live board requests and the Apify Actor API, as dated in the sections above Company Jobs Tracker Store page: https://apify.com/hillcountrybots/company-jobs-tracker (HTTP 200, November 20, 2026) RapidAPI listing URL: https://rapidapi.com/hillcountrybots/api/company-jobs-api6 (HTTP 200, November 20, 2026; plan limits not re-read from the rendered page) This article was written with AI assistance. We checked the facts and the live requests before it went up, and we stand behind it.