Normalize Greenhouse, Lever & Ashby Job APIs

Zusammenfassung

Pixel shares a practical guide to public job-board endpoints from Greenhouse, Lever, and Ashby, including their URLs, authentication requirements, and response differences. Learn how to map their JSON job listings into one normalized schema using fetch, with a runnable example.

DEV Community

Public job-board endpoints of Greenhouse, Lever and Ashby, and how to normalize them

This post was written by AI coding agents working on my behalf, and it is labelled AI Generated. Disclosure: I built this tool with AI coding agents, and AI helped draft this article. Every request below was re-run on 2026-11-16, and the numbers and field names were checked against the live responses and the vendors' docs. Many companies host their careers page on an applicant tracking system (ATS). Three of the common ones, Greenhouse, Lever and Ashby, publish the open jobs of each customer through plain JSON endpoints. You need no API key and no login. This post documents what each endpoint returns, where they differ, which sources I decided not to use, and how I map the three shapes into one schema. You can use all of it with fetch and no tool of mine. A small runnable example is at the end. The three endpoints The identifier is called a "board token" (Greenhouse), a "site" (Lever) or a "job board name" (Ashby). It is usually the last part of the company's hosted board URL, for example jobs.lever.co/leverdemo gives leverdemo. It is often not the company's marketing name. ATS Endpoint Auth Greenhouse GET https://boards-api.greenhouse.io/v1/boards/{token}/jobs none for GET Lever GET https://api.lever.co/v0/postings/{site}?mode=json (EU: api.eu.lever.co) none for GET Ashby GET https://api.ashbyhq.com/posting-api/job-board/{name}?includeCompensation=true none Greenhouse's docs say "Job Board data is publicly available, so authentication is not required for any GET endpoints." Lever's repository documents the posting list and its filters (skip, limit, location, commitment, team, department). Ashby documents one endpoint and one parameter. Greenhouse The list response is { "jobs": [...], "meta": { "total": N } }. Each job has id, title, location.name, absolute_url, first_published, updated_at, company_name and a few compliance fields. Two things to know: The plain list does not include department or description. Add ?content=true to get the description, department and offices, or call /departments and join on job id. Pay ranges are not in the list. The docs describe pay_transparency=true on the single-job endpoint, GET /jobs/{id}, which means one extra request per job. Lever The response is a bare JSON array. Useful fields: id, text (the title), categories (location, commitment, team, department, allLocations), country, workplaceType (on-site, remote, hybrid or unspecified), createdAt in milliseconds since the epoch, hostedUrl, applyUrl, and an optional salaryRange with currency, interval, min and max. Descriptions come both as HTML and as plain text. Ashby The response is { "apiVersion": "1", "jobs": [...] }. Each job has title, department, team, employmentType, location, secondaryLocations, isRemote, workplaceType (OnSite, Remote, Hybrid), publishedAt, jobUrl, applyUrl, descriptionHtml, descriptionPlain, isListed and, with includeCompensation=true, a compensation object. Ashby's docs say a job with isListed: false "should only be available via direct link", so skip those. Compensation is structured: each tier has components, and a salary component has minValue, maxValue, currencyCode and interval. Bonus and equity components can appear in the same list with null values, so filter on compensationType === "Salary". Gotchas I hit Unknown boards return 404 on all three today (Greenhouse {"status":404,"error":"Job not found"}, Lever {"ok":false,"error":"Document not found"}, Ashby plain Not Found). A 200 with an empty list means the board exists and has no open jobs, but a 404 does not tell you the company is gone, only that this token is wrong. Some write-ups say Lever returns an empty array for unknown sites. I did not see that. Sizes differ a lot. On the day I tested, one large Greenhouse board returned about 490 KB for its list without descriptions, and Ashby's own board with compensation was about 4.5 MB. Cache by board and do not refetch on every user request. Timestamps differ. Greenhouse and Ashby give ISO strings, Lever...
Normalize Greenhouse, Lever & Ashby Job APIs
Powered by Readybot.io

Das Neueste von Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …