Rippling Jobs Scraper — Export Any ATS Board (Title, Salary, Location & Apply Links)

The Rippling Jobs Scraper extracts every open job from any company careers board hosted on Rippling ATS (ats.rippling.com/{company}/jobs). Point it at one or more company board slugs or URLs and scrape Rippling jobs into clean, flat, analysis-ready rows — role title, department, location, workplace type, structured salary range, full description and the public apply link. Because every Rippling board is backed by a public JSON API, this Rippling scraper needs no login, no API key, no browser and no coding — just the companies you care about.

Export to JSON, CSV, Excel, or API.

Built for job boards and aggregators, recruiters and sourcers, compensation / salary-benchmarking teams, talent-market analysts, sales and lead-gen teams targeting hiring companies, and anyone who needs structured Rippling ATS data at scale.

---

🔎 Why scrape Rippling?

Rippling is a fast-growing HR, IT and finance platform, and a large and growing number of startups and mid-market companies run their public hiring boards on Rippling ATS. Each board lives at ats.rippling.com/{company}/jobs and lists every currently open role — but Rippling offers no global, cross-company search and no official bulk export. If you want the jobs from twenty companies, you'd be copy-pasting from twenty separate boards by hand.

The data on those boards is genuinely valuable: live job titles, departments, every location with remote/hybrid/onsite flags, the structured salary range many boards publish (driven by US pay-transparency laws), full job and company descriptions, and a direct apply URL for every role. That's gold for hiring analytics, competitor monitoring, compensation benchmarking and candidate sourcing — but only if you can pull it reliably and in a consistent shape.

Collecting it manually is slow and error-prone: boards paginate, the same posting is repeated once per location, and the salary, description and posted-date only live on a separate per-job detail endpoint. This Rippling jobs scraper does all of that for you — it paginates every board, de-duplicates postings, merges locations, and enriches each role with its salary and description — then hands you one tidy row per job.

Common reasons people scrape Rippling:

• Feed a job board or aggregator with fresh, structured roles from dozens of company boards at once.
• Source candidates by pulling every open engineering, sales or design role across a target-account list.
• Benchmark compensation using the published salary ranges (min, max, currency, frequency) across companies and locations.
• Monitor competitors' hiring — which teams are growing, where, and for which roles.
• Build sales / lead lists of companies that are actively hiring (a strong buying-intent signal).
• Track remote vs hybrid vs onsite trends across a market or portfolio.
• Power hiring dashboards and market reports with clean, de-duplicated job data.

✨ What this Rippling scraper does

• ✅ Scrapes any Rippling board — paste company slugs (e.g. gather) or any ats.rippling.com URL (e.g. https://ats.rippling.com/framework/jobs), one per line. The slug is parsed out of full board or posting URLs automatically.
• ✅ Scrapes multiple boards in one run — give it a whole target-account or competitor list; boards are fetched in parallel.
• ✅ Automatic pagination — walks every page of each board's API and returns hundreds to thousands of roles across your boards, bounded by your maxItems cap.
• ✅ De-duplicates postings — Rippling repeats the same role once per location; this scraper collapses them into a single row and merges every location.
• ✅ Rich, structured fields per job — role title, department, companyName; full locations array (name, city, state, country, ISO countryCode, workplace type) plus a primaryLocation; workplaceTypes and a derived isRemote flag; employmentType; structured salary (salaryMin, salaryMax, salaryCurrency, salaryInterval) plus the full payRanges array; postedAt date; clean descriptionText; and the public apply url.
• ✅ Built-in filters — keyword, location, department, workplace type (remote / hybrid / onsite), country (ISO code), employment type and minimum salary. Cheap list filters run before the expensive detail calls, so you only pay to enrich the roles you actually want.
• ✅ Two-tier, no wasted requests — a cheap list pass collects and filters, then a concurrent batch of detail calls enriches only the survivors. Turn Fetch job details off for a fast, list-only run.
• ✅ No key, no login, no browser — a lightweight HTTP + JSON scraper that runs through Apify Proxy to spread requests across IPs and avoid rate-limiting on large boards.
• ✅ Export anywhere — download as JSON, CSV or Excel, or pull straight from the Apify API / dataset; integrate with Make, Zapier, Google Sheets or a webhook.

🎯 Use cases

• Recruiters & sourcers — build candidate-facing lists of every open role across a set of companies, filtered by keyword, location and workplace type.
• Job boards & aggregators — ingest fresh, de-duplicated Rippling jobs with apply links to keep listings current.
• Compensation & HR analysts — benchmark published salary ranges by role, level, location and company.
• Sales & lead generation — target companies that are actively hiring (and for which functions) as a buying-intent signal.
• Talent-market & labor-market researchers — quantify remote vs hybrid vs onsite, department growth and geographic spread.
• Competitive intelligence — track a competitor's open headcount, new teams and location strategy over time.
• Executive search & RPO firms — monitor client or prospect boards and surface new mandates automatically.
• Founders & operators — study how peer companies structure roles, departments and pay.

📥 Input

Give the actor at least one Rippling board (slug or URL). Everything else is an optional filter or performance setting. All filters are case-insensitive substring matches unless noted.

Field	Type	Description
boards	array (required)	Company board slugs (e.g. gather) or any ats.rippling.com URL, one per line. Rippling has no cross-company search, so bring your own list.
searchTerm	string	Keep only roles whose title or department contains this text (e.g. engineer).
location	string	Keep only roles with a location (city / state / country) containing this text (e.g. New York, London).
department	string	Keep only roles whose department contains this text (e.g. Engineering, Sales).
workplaceType	select	any, remote, hybrid or onsite. A role can list several workplace types.
employmentType	string	Keep only roles whose employment type contains this text (e.g. full-time, contract, intern). Requires details.
country	string	2-letter ISO code, e.g. US, GB, CA.
minSalary	integer	Keep only roles whose salary top end is at least this amount (in the posting's own currency). Forces details on; roles without a published salary are dropped.
fetchDetails	boolean	Call the per-job detail endpoint to add salary, employment type, posted date, company name and description. Default true. Turn off for a fast, list-only run.
includeDescription	boolean	Include the full job + company description text (requires details). Default true.
maxItems	integer	Maximum jobs to save across all boards; also caps how many roles get detail calls. 0 = no limit.
maxConcurrency	integer	How many requests run in parallel (boards and detail calls). Default 8.
proxyConfiguration	object	Proxy settings. Apify Proxy (default) spreads requests across IPs and avoids rate-limiting on large boards.

Example input

{
  "boards": [
    "gather",
    "https://ats.rippling.com/framework/jobs",
    "rippling"
  ],
  "searchTerm": "engineer",
  "workplaceType": "remote",
  "country": "US",
  "minSalary": 150000,
  "fetchDetails": true,
  "includeDescription": true,
  "maxItems": 200,
  "maxConcurrency": 8,
  "proxyConfiguration": { "useApifyProxy": true }
}

📤 Output

Each open role becomes one clean, flat JSON row. Here is a representative item (truncated description):

{
  "board": "framework",
  "id": "fa347c96-839e-42a0-9f2c-91d37428767c",
  "title": "Manager, Business Systems",
  "url": "https://ats.rippling.com/framework/jobs/fa347c96-839e-42a0-9f2c-91d37428767c",
  "department": "Finance",
  "locations": [
    {
      "name": "Remote (United States)",
      "city": null,
      "state": null,
      "country": "United States",
      "countryCode": "US",
      "workplaceType": "remote"
    }
  ],
  "primaryLocation": "Remote (United States)",
  "workplaceTypes": ["remote"],
  "isRemote": true,
  "country": "US",
  "employmentType": "Salaried, full-time",
  "salaryMin": 170000,
  "salaryMax": 190000,
  "salaryCurrency": "USD",
  "salaryInterval": "year",
  "payRanges": [
    { "location": "Remote (United States)", "currency": "USD", "frequency": "year", "min": 170000, "max": 190000, "isRemote": true }
  ],
  "postedAt": "2026-10-13T02:05:06.408Z",
  "companyName": "Framework",
  "descriptionText": "The Position\nWe're looking for a Manager, Business Systems to own and evolve the systems that run Framework behind the scenes...",
  "scrapedAt": "2026-10-19T20:30:04.847Z"
}

Field reference

Field	Description
board	The Rippling board slug the role came from.
id	Rippling's unique job ID (UUID).
title	Role title.
url	Public posting / apply URL.
department	Department name.
locations	Array of every location: name, city, state, country, ISO countryCode, workplaceType.
primaryLocation	Name of the first location (a quick single-value location).
workplaceTypes	De-duplicated list of remote / hybrid / onsite across the role's locations.
isRemote	Boolean — true if any location is remote (null when no workplace type is listed).
country	ISO country code of the primary location.
employmentType	Full-time / contract / intern, etc. (present when details are fetched)
salaryMin, salaryMax	Structured pay-range bounds. (present when the board publishes a structured range)
salaryCurrency, salaryInterval	Currency and frequency (e.g. USD, year) of the range. (present when available)
payRanges	All published ranges, one per location (currency, frequency, min, max, remote flag). (present when available)
postedAt	ISO date the role was posted. (present when details are fetched)
companyName	Company name from the detail payload. (present when details are fetched)
descriptionText	Full job + company description as clean plain text. (present when details are fetched)
scrapedAt	ISO timestamp of when the row was scraped.

A note on salary honesty: Rippling's structured pay fields (salaryMin / salaryMax / payRanges) are populated only when the board itself publishes a machine-readable range — common for US pay-transparency roles, but not universal. Some postings state a salary only inside the free-text description; in those cases the structured fields stay null and you'll find the figure in descriptionText. This is a property of the Rippling data, not a scrape error, which is why these fields are marked present when available.

🔁 Pagination & scale

The actor paginates each board through Rippling's list API (GET /api/v2/board/{slug}/jobs?page=N&pageSize=100), reading totalPages from the response and advancing page by page until the last page is reached — so it collects every posting on a board, not just the first page. Across several boards that adds up to hundreds to thousands of roles per run.

Scraping is two-tier for efficiency: the cheap list pass collects and de-duplicates postings and applies your list-level filters (keyword, location, department, workplace type, country) first; only the surviving roles are then enriched with concurrent per-job detail calls (GET /api/v2/board/{slug}/jobs/{id}) for salary, description and dates. The total result set is bounded by maxItems, which also caps how many roles get detail calls — keeping both runtime and cost predictable. Requests run concurrently (maxConcurrency, default 8) and rotate through Apify Proxy to stay under Rippling's rate limits on large boards. Boards that don't exist or are empty are skipped with a warning instead of failing the run, and every failed request is retried with back-off.

⚙️ How to use

1. Open the Rippling Jobs Scraper on the Apify Console.
2. Paste your board slugs or ats.rippling.com URLs into Rippling boards (one per line).
3. (Optional) Add filters — keyword, location, department, workplace type, country, employment type, minimum salary — and set Max jobs.
4. Click Start and watch the live log count postings, filter, and enrich.
5. When the run finishes, open the Output / Storage tab and export to JSON, CSV or Excel, or pull the dataset from the Apify API.
6. Automate it: run on a schedule, trigger it via API, or wire the dataset into Make, Zapier, Google Sheets or a webhook to keep a live feed of Rippling jobs.

💡 Tips

• Find the slug from any company careers link that points at ats.rippling.com/<slug>/jobs — that <slug> is all you paste. VC/accelerator portfolio pages and competitor career pages are great sources of board lists.
• Fast list-only pass: turn off Fetch job details (and Include full description) for a quick inventory of titles, departments, locations and apply links without the detail calls.
• Only paying for what you need: list-level filters (keyword, location, department, workplace type, country) run before detail calls, so narrowing them keeps runs cheap.
• Salary filtering: setting minSalary automatically forces details on and drops roles without a published structured range — expect a smaller, pay-transparent subset.
• Leaner rows: keep details on but turn Include full description off when you only need the structured fields (salary, dates, employment type).
• Big boards: raise maxConcurrency (up to 20) to speed up boards with hundreds of roles; keep Apify Proxy on to avoid rate-limiting.

❓ FAQ

Is scraping Rippling legal? This Rippling scraper collects only publicly available job postings from company boards that are open to anyone on the web, via Rippling's own public board API — no login, no account and no protected data. As with any scraping, use the data responsibly and in line with Rippling's terms and applicable laws; for compliance-sensitive use, consult your legal team.

Do I need a Rippling account, API key or login? No. Rippling's board API is public, so the scraper needs no API key, no login and no browser.

How many jobs can it return and how fast is it? It paginates every board fully and can return hundreds to thousands of roles across your board list, bounded by maxItems. A list-only pass is very fast; enrichment adds one concurrent detail call per surviving role, so speed scales with how many roles you keep and your maxConcurrency.

Does Rippling have a global job search? No — Rippling has no cross-company search. You must supply the specific company boards (slugs or URLs) you want. That's why the boards input is required.

Which export formats are supported? JSON, CSV and Excel downloads, plus the Apify API / dataset endpoint for programmatic access and integrations.

Is there a Rippling API I can use instead? Each board is served by an undocumented public JSON API; this actor wraps it, handles pagination, de-duplication, the two-tier detail enrichment, retries and proxy rotation, and returns a clean normalized schema — so you don't have to reverse-engineer or maintain it yourself.

Why are salary fields empty on some roles? The structured salaryMin / salaryMax / payRanges fields are populated only when the board publishes a machine-readable range. Many roles (especially outside US pay-transparency states) list pay only inside the description text, or not at all — so these fields are null for them. Check descriptionText for free-text salary mentions.

Can I filter by keyword, location, department or salary? Yes — filter by searchTerm (title/department), location, department, workplaceType (remote/hybrid/onsite), country (ISO code), employmentType and minSalary. Cheap filters run before the detail calls to keep runs efficient.

How fresh is the data? Every run hits the live Rippling boards, so results reflect the roles open at that moment. Run it on a schedule to keep a continuously fresh dataset; each row carries a scrapedAt timestamp.

What happens if a board doesn't exist or is empty? It's skipped with a warning and does not fail the run — so you can pass a long list of boards without worrying about the occasional dead or private slug.

🔗 Related scrapers

Building a cross-platform jobs or talent-intelligence dataset? Pair this with the other job-board scrapers from the same author:

• Seek Scraper
• Workana Scraper
• ZipRecruiter Scraper
• Xing Jobs Scraper
• Naukri Scraper
• GulfTalent Jobs Scraper

---

Ready to export Rippling jobs? Add your company boards, hit Start, and get clean, de-duplicated roles with salary, location and apply links in JSON, CSV or Excel — no login, no API key, no coding.