Adderley Data Apify Store

Adderley Data / Guides

Ashby job board API: endpoint, fields and pay data, measured

A company's Ashby job board is one public JSON document: GET https://api.ashbyhq.com/posting-api/job-board/{board_name}. One request returns every posting with its full text, and one query parameter adds the pay range. This page covers what comes back, what we measured on Ashby's own board, and what is left to build when you watch boards over time.

The request

curl "https://api.ashbyhq.com/posting-api/job-board/ashby?includeCompensation=true"

Ashby's developer documentation describes the parameter this way: "Optionally, you can add includeCompensation=true as a query parameter to include compensation data in the response." Our requests carry no key.

The board name is the first part of the path in a company's Ashby links, such as jobs.ashbyhq.com/{board_name} or the embed at jobs.ashbyhq.com/{board_name}/embed. Three behaviours checked against the live API on 23 September 2026:

  • The name is not case-sensitive: Ashby and ashby return the same postings.
  • The API writes the name into every posting's jobUrl exactly as you sent it, so send it in lower case if you want stable links.
  • An unknown name answers HTTP 404 with the plain-text body Not Found, not JSON.

What a posting holds

The fields of each posting, from Ashby's documentation (read 6 October 2026):

  • title, department and team: the role and where it sits.
  • location, secondaryLocations and address: the main location, any others, and a postal address.
  • workplaceType and isRemote: OnSite, Remote or Hybrid, and a remote flag.
  • employmentType: FullTime, PartTime, Intern, Contract or Temporary.
  • descriptionHtml and descriptionPlain: the full posting, both ways.
  • publishedAt, jobUrl and applyUrl: when it went up, and its links.
  • isListed: whether the posting is shown on the board.
  • compensation: the pay range, only with includeCompensation=true.

Unlike most job board APIs, this one carries the work arrangement and the employment type as fields, and the pay range as data rather than text.

Measured on Ashby's own board

Ashby's own board listed 62 postings on Tuesday 6 October 2026, read in one request (run GZe1QssLx1YwBSYhC). The fuller read is from Wednesday 30 September 2026 (run jIgYO66xS7qIfnwLc), when it listed 67:

Ashby's own board, 67 postings, 30 September 2026
FactPostings with itNotes
Pay range67 of 67All yearly. US dollars 37, euros 13, pounds 7, Canadian dollars 5, Australian dollars 2, Singapore dollars 2, yen 1
Work arrangement67 of 67Every posting on the board was remote
Country60 of 67The United States 37, the United Kingdom 8, Canada 5, Australia 4, Germany 2, Portugal 2, France 1, Singapore 1
City0 of 67None to give: the postings were all remote
Published date67 of 6713 posted in September 2026; the oldest still open dated from March 2024

Where the API stops

The API answers "what is on this board now". It does not answer "what changed since yesterday", and that is the question a recruiter, an investor or a sales team watching hiring is asking. To get there yourself you keep each read, compare by posting ID, and decide what counts as a change, then repeat for every company you watch, each with its own name.

Ashby Jobs Scraper does that on top of this API: any number of board names or links, postings with isListed false left out, one row per posting in a fixed schema, and in incremental mode it returns, and charges for, only postings that are new, changed, back or gone. Its page has the price and every field. For Ashby next to Greenhouse, Lever, Workday and eleven more systems in one table, use the Career Site Jobs Scraper.

The same reference for other systems

Published 2026-10-06.