Rippling Jobs Scraper — 1,298 Company Career Sites

Rippling's applicant tracking system sits behind the careers page of a lot of US startups, clinics and multi-site operators. This Actor reads those boards — one company you name, or a bundled registry of 1,298 live Rippling career sites carrying 18,647 open postings.

{ "keywords": ["manager"], "locations": ["texas"], "maxJobs": 200 }

{ "companies": ["https://ats.rippling.com/carbon-health/jobs"] }

No login, no cookies, no proxies, no API key.

What you get, and what you do not

Be clear about this before building on it: Rippling's public board endpoint is the thinnest in this family. It returns four things per posting, and it returns them reliably.

Field	Description	Coverage
provider	Always rippling	100%
company / companySlug	Employer board slug	100%
jobId	Rippling requisition uuid — stable across runs	100%
title	Job title	100%
location	Work location, e.g. North Little Rock, AR	100%
department	Department label, e.g. Club, Engineering	100%
applyUrl	Direct link to the posting	100%
scrapedAt	When this row was read	100%

Not available at all: description text, employment type, salary, and posting date. Those fields are absent from the payload — not empty, absent. descriptionText, employmentType, salary and postedAt come back null on every row, and no setting changes that.

Because there is no date, postedWithinDays keeps Rippling rows rather than dropping them. Their age is unknown, not old.

If you need body text, Greenhouse, Workable, Ashby and Pinpoint publish it — the Career Site Job Feed covers those in this same output schema.

What it is good for

Title, location, department and a direct apply link, across 1,298 employers, is enough for:

• A hiring signal. Which companies are opening roles, in which function, in which city.
• A sourcing list. Filter by title, keep company and applyUrl, work from a spreadsheet.
• Change detection. companySlug:jobId is stable, so diffing between runs tells you exactly what opened and what closed.

It is not enough for keyword analysis of job text or salary benchmarking. Use a platform that publishes those.

Input

Option	What it does
keywords	Keep only titles containing one of these. Case-insensitive.
excludeKeywords	Drop titles containing any of these, e.g. senior, intern.
locations	Keep only locations containing one of these.
remoteOnly	Keep only postings whose location looks remote.
postedWithinDays	Freshness filter. Rippling rows have no date and are always kept.
companies	Board slugs or careers URLs. Leave empty to search all 1,298.
maxBoards	How many boards to scan, largest-first.
maxJobs	Hard cap on rows, so a run costs what you expect.

Finding a company slug

The board lives at ats.rippling.com/<slug>/jobs, so the slug is the first path segment. Paste the whole URL and the Actor extracts it. Or run without companies and read the companySlug column.

Pricing

Pay per result — you are charged per job row delivered. A board that fails or returns nothing costs you nothing. Platform usage is included rather than billed on top.

Beyond Rippling

Companies move between applicant tracking systems, and most job-data projects need more than one:

• Career Site Job Feed — the same engine across every platform in this family, in one run, with an identical output schema.
• New Job Alerts — the same coverage, but each run returns only what appeared since the previous run.

Notes

• A dead slug never aborts the run. Failures land in a FAILED_BOARDS record in the key-value store, with the reason for each.
• companySlug:jobId is a stable key, safe for detecting what opened and closed between runs.
• No login, no proxies, no API key. Rippling publishes this endpoint openly. Private boards are invisible to every scraper, including this one.