Dev.to WebDev 🛠 Dev 👁 0 📖 6 min read

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 2

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 gives milliseconds. Convert to ISO 8601 UTC and keep null when a source gives nothing.
  • Salary is rarely present, and it comes in source currency and period. Do not compare numbers across currencies.
  • Be polite. Lever's robots.txt on api.lever.co states Crawl-delay: 1. I wait at least one second between requests to one host and send a descriptive User-Agent. I have not found a published rate limit for the GET endpoints of the three vendors, so I keep the pace low.

What I left out, and why

I looked at three more systems and decided not to call them:

  • SmartRecruiters. https://api.smartrecruiters.com/robots.txt on 2026-11-16 allows one named bot on /v1/companies/ and says User-agent: * then Disallow: /. A generic client is told to stay away, so I do not call it.
  • Breezy HR. The robots file on breezy.hr disallows /api/, and its terms of service prohibit accessing the service by means other than its publicly supported interfaces.
  • Workday. Its job sites use an undocumented, per-tenant POST interface, and the site terms restrict scraping. Leaving it out is a judgment call. Check Workday's terms yourself if you need it.

A missing robots rule is not a permission, and terms of service apply either way. My rule: if I cannot show the access is at least not prohibited, I skip the source.

A normalized schema

Every record gets the same keys, and unknown values stay null. I never invent a value. A salary of 0 becomes null.

{
  "ats": "lever",
  "companySlug": "leverdemo",
  "jobId": "ad208490-4052-4f91-a57e-433f2d1e484b",
  "title": "Customer Success Manager",
  "location": "Atlanta, Georgia",
  "department": "Customer Success",
  "workplaceType": "hybrid",
  "postedAt": "2026-08-31T18:12:19.703Z",
  "salaryMin": 85000,
  "salaryMax": 175000,
  "salaryCurrency": "USD",
  "url": "https://jobs.lever.co/leverdemo/ad208490-4052-4f91-a57e-433f2d1e484b"
}

Design choices that matter later:

  1. A stable global id, ats:companySlug:jobId. Job ids alone collide across vendors.
  2. Keep the source label next to the normalized one. Employment types arrive as FullTime, Regular Full Time (Salary) or nothing. Map the ones you recognize to full_time, part_time, contract and so on, and keep the raw text too.
  3. remote is tri-state. true, false or null. Treat "hybrid" as not remote, and treat "unknown" as unknown.
  4. No guessing. If a source has no department, the field is null, even if you could guess from the title.

Try it without my tool

This short Node script (no dependencies, Node 18+) fetches one board and prints one normalized JSON record per line. It is in this repository: https://github.com/anhduyhaha1234-droid/job-board-endpoints .

node normalize.mjs greenhouse stripe
node normalize.mjs lever leverdemo
node normalize.mjs ashby ashby

On 2026-11-16 these returned 785, 10 and 77 records. Those counts change daily.

Finding board tokens

For name lookups I use the "ATS Company Directory" published by LastRound AI under CC BY 4.0, about 9,900 boards on these three systems (August 2026 snapshot): https://lastroundai.com/blog/salary-transparency-study-2026 . I converted the CSV to compact JSON and normalized names. Credit to LastRound AI. A snapshot goes stale, and some boards will be closed.

If you would rather not write the loop

I packaged the above, plus filters (title, location, workplace type, salary floor), an only-new mode and Personio and Teamtailor feeds, as an Apify Actor: https://apify.com/duytrinh98/career-site-jobs . It is pay per saved job. You need an Apify account to run it, and free accounts can try it. If you only need one or two boards, the script above is enough.

Questions, bug reports and board URLs that do not work are welcome in the comments or in the Actor's Issues tab.

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.