Rippling job board API: the public list, the job record and pay by tier

A Rippling job board, ats.rippling.com/{slug}/jobs, loads its jobs from api.rippling.com in two steps: one paged list of postings, then one record per posting for the facts the list leaves out. Rippling's developer site has a Job Board API page, but it asks for a Rippling sign-in (checked 6 October 2026). This page describes the two endpoints the public board itself calls, as we measured them.

The list

curl "https://api.rippling.com/platform/api/ats/v2/board/rippling/jobs?groupJobsByLocation=true&page=0&pageSize=1000"

The response is {"items", "page", "pageSize", "totalItems", "totalPages"}. Each item is one posting: id, name (the title), url, department.name, language and locations. Every location carries the label the board shows, a country name and its ISO code, a state and its code, a city, and a workplaceType of ON_SITE, HYBRID or REMOTE. Checked against the live API on 24 September 2026:

Paging. pageSize goes to 1,000; 5,000 answered HTTP 400. totalItems and totalPages give the size, so a board of 1,000 postings or fewer is one request.
The older list, /platform/api/ats/v1/board/{slug}/jobs, ignores paging and returns one entry per posting and location, with the location as a label only: 601 entries for 328 postings on Rippling's own board.
Case counts. rippling is a board; Rippling answers 404. An unknown slug answers HTTP 404 with {"error_code":"RESOURCE_NOT_FOUND","message":"Job Board not found"}.

Two habits of the locations: a remote location's state and city can name a place its label does not (Rippling files "Canada" under British Columbia), and one posting can list the same label twice with different workplace types.

The job record

curl "https://api.rippling.com/platform/api/ats/v1/board/rippling/jobs/{id}"

The list has no date, no pay and no employment type. The record has all three, with the company's name and the text (read 6 October 2026):

createdOn: an ISO timestamp with its offset and microseconds, such as 2026-03-31T17:37:26.093000-07:00. No field records an edit.
payRangeDetails: an empty list or up to three ranges, each with a location label (a pay tier or a place), currency, frequency (YEAR, HOUR or MONTH on the postings we read), rangeStart, rangeEnd and isRemote.
employmentType: {"label": "SALARIED_FT", "id": "Salaried, full-time"}. The two names are the other way round from what they hold: the code is in label and the words are in id.
companyName, department with base_department and department_tree, workLocations as labels, and description in two HTML parts, company and role.

The record also carries the board's settings and the application form's questions, which a jobs table has no use for. An unknown posting id on a real board answers HTTP 404 with {"ok": false, "error": "There was a client validation error"}.

Measured on Rippling's own board

Rippling's own board listed 336 postings on Tuesday 6 October 2026. Reading all of it took 337 requests, the list in one page and then one record per posting, all answered at the first attempt, in 3 minutes 17 seconds at 90 requests a minute (run EU4a9hI5P4wnjwxBr). On 30 September the same board listed 327 (run jIgYO66xS7qIfnwLc).

Rippling's own board, 336 postings, 6 October 2026
Fact	Postings with it	Notes
Country	336 of 336	17 countries: the United States 195, India 80, Ireland 21, Australia 9, Canada 6
Work arrangement	336 of 336	On-site 242, remote 78, hybrid 16
Employment type	336 of 336	Full-time 327, internship 5, contract 4
City	283 of 336	All 53 without one are remote postings
Pay range	164 of 336	156 of the 195 in the United States; none of the 80 in India or the 21 in Ireland
Created date	336 of 336	99 created in September 2026 and 21 so far in October; the oldest still open dates from July 2023

Pay is often more than one range. Of the 164 postings with pay, 59 give two or three, by location tier ("US Tier 1", "US Tier 2", "US Tier 3") or by office. By posting, pay is yearly on 160, hourly on 2 and monthly on 2.

Where it stops

The list is cheap and the records are not. A full read costs one request per posting, 337 for Rippling's own board, because the date and the pay live only in the record. Read a board in full every day and most of those requests confirm that nothing changed, and nothing in either response says which postings did. Pay by tier is the other piece of work: a table needs a rule for which range counts, or a place to keep them all.

Rippling Jobs Scraper reads the list first and requests a record only for a posting it will save, so a posting your filters leave out costs no request. In incremental mode it compares each posting's title, department and locations in the list with the last run; an unchanged posting is skipped, costs no record request and is not charged. The price of that saving: an edit only to a posting's text, pay, employment type or date is not reported as a change. Several ranges give the lowest minimum and the highest maximum in one currency and period, with every range kept as the job page words it. Its page has the price and every field. To read Rippling with fourteen other systems in one run, see the measured run of the Career Site Jobs Scraper, where Rippling's own board gave 327 of the 869 roles.

The same reference for other systems

Published 2026-10-06.