Rippling Jobs Scraper: Any Board, No API Key

Every open role from any Rippling ATS job board, by company domain or board token. Titles, locations and departments as clean JSON, no API key and no proxy. Rippling's board API publishes no descriptions, which is stated up front.

Features

• Any rippling board, from the URL or token you already have. No API key, no login, no cookies, no proxy: this reads the public feed rippling publishes so that job boards can index it.
• Every posting, not the first page. Paging is handled, including the places where rippling reports a total it does not honour.
• One row per job, as clean JSON, with the same field names on every run.
• Filters that cost you nothing. Rows dropped by titleKeywords, locationKeywords or remoteOnly are never charged for.
• Errors are per company. One bad id does not end the run, and error rows are not charged.
• Run it on a schedule and the rows become a record of who started hiring and when.

How to use it

1. Click Try for free, or add this Actor to a task.
2. Put one or more companies or board ids in the input. The example below is a real one.
3. Optionally narrow it with titleKeywords, locationKeywords or remoteOnly. Filtered rows are not billed.
4. Run it. Results appear in the dataset and can be exported as JSON, CSV, Excel or fetched from the API.

Input

Input	Type	Default	What it does
companies	array of strings	none	Company domains or names, one per line, e.g. rippling.com
boards	array of strings	none	Board tokens to read, one per line, e.g. rippling
titleKeywords	array of strings	none	Keep only roles whose title contains any of these, one per line, e.g. security or staff engineer
locationKeywords	array of strings	none	Keep only roles whose location contains any of these, one per line, e.g. London or Israel
remoteOnly	true or false	false	Keep only roles flagged remote by the ATS, or whose title or location says remote or anywhere
includeDescription	true or false	false	Rippling's board API returns no description at any setting, so this changes nothing here
maxResultsPerCompany	number	1000	Ceiling on roles taken from any single board
maxItems	number	none	A hard ceiling on rows for the entire run, across every company

{
  "boards": ["rippling"],
  "titleKeywords": ["engineer"],
  "remoteOnly": true
}

Output

One row per job. This is the shape, with the fields rippling actually publishes:

{
  "title": "Senior Software Engineer",
  "location": "Berlin, Germany",
  "url": "https://boards.example.com/jobs/8130725",
  "jobId": "8130725",
  "departments": ["Engineering"],
  "company": "rippling",
  "atsPlatform": "rippling",
  "boardToken": "rippling",
  "boardUrl": "https://boards.example.com/rippling"
}

Field
title	the role as the company wrote it
location	as published, not normalised
url	the public posting, ready to open
jobId	the ATS's own id, stable across runs
departments	list
company	what you asked for, echoed back
atsPlatform	which system it came from
boardToken	the board id used
boardUrl	the public board this came from

What people use this for

Hiring data is not really about jobs. It is the earliest public signal a company gives that something changed, and it is why three different kinds of buyer end up on the same dataset:

• Sales and go-to-market. A company that opens six engineering roles this month is a company with new budget. Job postings say which team is growing and in which city, weeks before anything shows up in a funding announcement.
• Investors and market research. Headcount by function, tracked over time, across a whole portfolio or a whole sector. Every row carries the company, the team and the date, so a weekly run is a time series.
• Recruiting and talent. Where a competitor is hiring, which roles they have been trying to fill for months, and how fast a team is growing. Rippling does not publish pay, so no row here claims to know it.

Run it once for a snapshot. Run it on a schedule and the same rows become a record of who started growing and when.

You do not need the board token

{ "companies": ["rippling.com"] }

Every other rippling Actor asks you for a board token, and there is no directory mapping a company to its token. This one derives candidates from the domain and verifies each against the live API, which is sound because rippling answers 404 for a board that does not exist and 200 for one that exists with nothing open. A 200 is proof, not a maybe.

Measured across 30 companies, deriving and verifying resolved 90% against 50% for reading the careers page for a link. Stripe's careers page is a JavaScript app that names no board at all, and it still resolves.

What makes rippling different

• Measured: rippling 768 open roles, which is larger than most Greenhouse boards.

• Rippling's board API returns five fields per job and no description at any setting: uuid, name, url, department, workLocation. Rows carry no description because the source has none, not because it was missed. Turning includeDescription on changes nothing here, and saying so is better than shipping an empty field that reads as a bug.

Filters that cost you nothing

Filtered rows are not charged. Keywords match as plain text, so c++ and node.js mean exactly that rather than being read as regular expressions.

Integrations and API

Every run writes to a dataset you can export as JSON, CSV or Excel, or read from the Apify API. The Actor can be scheduled, called from another Actor, or wired into Make, Zapier, Slack, Google Sheets and the rest of Apify's integrations. It is also callable by an AI agent through the Apify MCP server, and the output schema means the agent gets field descriptions rather than raw JSON.

Looking for an Indeed or Glassdoor API? There isn't one, and this is why you don't need it

Indeed has no public jobs API. Neither does Glassdoor, ZipRecruiter or LinkedIn Jobs, and all four block you at the edge. Measured from an ordinary residential address on 2026-08-01, with normal browser headers:

indeed.com/jobs          403      0 bytes
glassdoor.com/Job/...    403      0 bytes
ziprecruiter.com         403      0 bytes
upwork.com/nx/search     403      0 bytes

Zero bytes. Cloudflare rejects the request before it reaches an application, so there is nothing to parse and no proxy budget that fixes it.

But none of those four originate job data. They aggregate it from company career pages, and those pages run on systems like rippling that publish a free, keyless, public API, because companies want their openings indexed. That API answered with real jobs from the same connection, in the same minute.

Going to the source is also fresher. An aggregator shows you its last crawl. This shows you the board.

FAQ

Do I need an API key or an account with rippling? No. This reads the public feed rippling publishes for indexing. Nothing here is behind a login, a paywall or a bot wall.

What am I charged for? Rows returned. Rows removed by your filters are not charged, and neither are error rows.

Can I get only what changed since my last run? Run it on a schedule and compare jobId, which is stable across runs. For change tracking with the work already done, see the sibling Actors below.

A board came back empty. Is the company not hiring? An empty board is a real answer here and is reported as one.

Notes

• The source is a public API that companies publish deliberately. Nothing here is behind a login, a paywall or a bot wall.
• An empty board is a real answer and is reported as one.
• Errors are per company. One bad token does not end the run, and error rows are not charged.