Rippling jobs API

Employers who run Rippling for HR and turned on its hiring module — mostly small, mostly US. A thin endpoint, but a clean one.

The endpoint

GET https://api.rippling.com/platform/api/ats/v1/board/{company}/jobs

No key, no login. The slug is the path segment in ats.rippling.com/{company}.

curl -s 'https://api.rippling.com/platform/api/ats/v1/board/acme/jobs'

What it returns, measured

Measured across every live Rippling board in our registry — 18,701 postings from 1,298 boards, not a sample. yes means 99.5% or more; no means the field does not exist on this endpoint.

Field	Rippling
Posting date	no
Description	no
Pay	no
Marked remote	17.4%

Title, company, location and an apply URL come back on every row.

What it is good at

Department is present on 100% of rows, and a work-arrangement label resolves on every posting with 17.4% marked remote. The response shape is a flat array with no pagination to get wrong.

Where it falls short

No date, no description, no pay, and no employment type. This tells you who is hiring and for what title, and stops there.

Mistakes that cost us time

The response is a bare array.: Not an object with a jobs key like most of the others. Code written against the common shape will read undefined.
The API host is not the board host.: Boards live at ats.rippling.com/{company} but the JSON is served from api.rippling.com.

So should you use it

Yes, for a cheap signal that a small US company is hiring.

No, for almost any enrichment. Pair it with something else.

How Rippling compares with the other eleven on the same four fields is on the comparison page. If you would rather not write and maintain a client, this Actor reads Rippling and emits the same row shape as the other eleven, and ATS Database is a free lookup for finding which platform a given company is on.

Finding the boards

Rippling boards sit at ats.rippling.com/{company}, a path segment, and the platform is recent enough that archive coverage is thin but clean — 1,298 live boards. The trap is elsewhere: the board host and the API host are different names, so a harvester that derives the API URL from the page URL will build something that does not resolve.