--- title: "Rippling ATS" description: "Rippling ATS: where a company's job board lives, the public board endpoint, what the partner API covers, and how to reach the same employers' postings." canonical: https://jobspipe.dev/sources/rippling date_published: 2026-06-28 date_modified: 2026-10-29 author: Dvir Atias --- # Rippling ATS Rippling ATS publishes each customer's open roles on a public job board at ats.rippling.com//jobs, backed by a keyless board endpoint that returns that one company's postings as JSON. The Rippling platform API at app.rippling.com/developer is partner-gated and OAuth-scoped to one company's HRIS, payroll and apps, not a jobs feed across companies. JobsPipe does not collect Rippling; the same employers' openings reach one search endpoint through the boards JobsPipe does collect, in one record shape across 30+ sources. > Rippling ATS is the recruiting module of Rippling's HR platform, with one public job board per customer and no feed across employers; JobsPipe does not collect Rippling. **Canonical URL:** https://jobspipe.dev/sources/rippling ## Coverage JobsPipe does not collect Rippling. This page explains what Rippling exposes publicly and how to reach the same postings where they are also published on a board JobsPipe does collect (Workday, Greenhouse, Lever, Ashby, LinkedIn, Indeed, SmartRecruiters, Workable, Personio, Recruitee, Teamtailor, EURES, Paylocity, Breezy HR, CV-Library, Y Combinator, Bayt, JobTech (Sweden), Resume-Library, Arbeitnow, Himalayas, Rise, Manatal, Pinpoint, JobScore, HireHive, The Muse, Remotive, Remote OK, Jobicy, Working Nomads, Landing.jobs). ## Why Rippling jobs data is confusing The Rippling platform API at app.rippling.com/developer is partner-gated and OAuth-scoped: it manages one company's HRIS, payroll, devices and apps with that company's authorization. It is not a jobs feed across companies. Companies on Rippling Recruiting publish roles on public careers pages hosted by Rippling (under ats.rippling.com) or on their own domains, and each hosted board reads a keyless endpoint at api.rippling.com/platform/api/ats/v1/board//jobs. That endpoint serves one board at a time; there is no endpoint that enumerates Rippling customers or their postings. JobsPipe does not collect Rippling. Employers that run Rippling usually also post the same roles to LinkedIn and Indeed, and larger ones run Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever or Paylocity alongside it. JobsPipe collects all of those boards, so filter POST /v1/jobs/search by company_name_partial_match_or to reach them. ## Workarounds ### Use the Rippling platform API Requires the partner program and per-customer authorization, and reads that customer's workforce data. ### Read individual Rippling boards Possible per employer you already know, through the keyless board endpoint or the public HTML. No directory of employers. ### What JobsPipe offers instead JobsPipe does not collect Rippling. Search the same employers by name across the boards JobsPipe does collect (LinkedIn, Indeed, Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever and Paylocity); sources[0].provider on each record names the board it came from. ## Fields available on every record - `id` - `job_title` - `company` - `company_domain` - `url` - `date_posted` - `discovered_at` - `last_seen_at` - `verified_at` - `status` - `closed_at` - `closed_reason` - `ghost_score` - `seniority` - `cities` - `state_code` - `min_annual_salary_usd` - `max_annual_salary_usd` - `technology_slugs` - `keyword_slugs` - `esco_skills` - `sources` ## FAQ ### Is Rippling an ATS? Yes. Rippling Recruiting is the applicant tracking module inside Rippling's HR platform, and its hosted boards live under ats.rippling.com. The answers page on whether Rippling is an ATS covers what the module includes and how it compares with standalone systems. ### Does Rippling ATS have a job board API? For one company at a time, yes. Rippling's developer site documents a Job Board API that a customer uses to render its own published jobs on its careers site, and the hosted board under ats.rippling.com reads a public JSON endpoint with no key. Both are addressed by one company's board slug and return only that board, so neither works as a feed of jobs across Rippling employers, and there is no directory of boards to iterate. ### How can I tell if a company uses Rippling Recruiting? Check where its careers page is hosted. Companies on Rippling Recruiting publish roles on public careers pages hosted by Rippling under ats.rippling.com, or on their own domains. There is no endpoint that enumerates Rippling customers or their postings, so an ats.rippling.com link from the careers page is the practical signal, checked one employer at a time. You can also probe the board endpoint with the company's slug: api.rippling.com/platform/api/ats/v1/board//jobs answers 200 for a live board and 404 when there is none. ### Does Rippling require OAuth for API access? Yes. The Rippling platform API at app.rippling.com/developer is partner-gated and OAuth-scoped: it manages one company's HRIS, payroll, devices and apps with that company's authorization. Using it requires the partner program plus per-customer authorization, and it reads that customer's workforce data rather than serving a jobs feed across companies. ### How do I get one company's Rippling job postings? Call that company's keyless board endpoint at api.rippling.com/platform/api/ats/v1/board//jobs for titles, locations and links, or read its public careers page under ats.rippling.com or its own domain for the full text. There is no directory of employers, so each one is a separate call. The alternative is to search the employer by name with company_name_partial_match_or on the boards JobsPipe collects, since Rippling employers usually post the same roles to LinkedIn and Indeed. ### Do Rippling employers' postings include salary on other boards? When the posting states a range, yes. Records found for Rippling employers on LinkedIn, Indeed or the ATS boards JobsPipe collects carry min_annual_salary_usd and max_annual_salary_usd when a range is stated, alongside sources[0].provider, status, ghost_score, discovered_at, last_seen_at and seniority. Postings without a stated range leave the salary fields empty. ## Rippling ATS job board URL pattern A company on Rippling Recruiting gets a hosted board at ats.rippling.com//jobs, and each posting lives one level down at ats.rippling.com//jobs/. The segment is the board slug Rippling assigned when the customer set up recruiting, usually the company name in lowercase; some customers point their own careers domain at the board instead, so the ats.rippling.com address may redirect to the company's site. There is no public list of board slugs, so you find them one employer at a time from careers page links. ## The public board endpoint The hosted board reads GET https://api.rippling.com/platform/api/ats/v1/board//jobs, which needs no key and returns a flat JSON array of that company's published postings. Each row carries uuid, name, department, url (the posting on ats.rippling.com) and workLocation, and a role open in several places appears once per work location with the same uuid, so count distinct uuids rather than rows. The list has no description, salary or posted date; those sit on the posting page. ## Does Rippling have an API? Two, for two different jobs. The Rippling platform API at app.rippling.com/developer is partner-gated and OAuth-scoped: it manages one company's HRIS, payroll, devices and apps with that company's authorization, and it is not a jobs feed across companies. The hosted job board reads a keyless endpoint at api.rippling.com/platform/api/ats/v1/board//jobs, which returns one company's published postings and nothing else. Companies on Rippling Recruiting publish roles on those hosted boards (under ats.rippling.com) or on their own domains, and there is no endpoint that enumerates Rippling customers or their postings. ## What JobsPipe returns for Rippling Nothing under "source_or": ["rippling"]: JobsPipe does not collect Rippling. Employers that run Rippling usually also post the same roles to LinkedIn and Indeed, and larger ones run Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever or Paylocity alongside it. JobsPipe collects all of those boards, so filter POST /v1/jobs/search by company_name_partial_match_or to reach them. Each record comes back with sources[0].provider, status, ghost_score, discovered_at, last_seen_at, seniority, and min_annual_salary_usd and max_annual_salary_usd when the posting states a range. ## Related - **Product:** https://jobspipe.dev/jobs-api - **All sources:** https://jobspipe.dev/sources - **Docs:** https://docs.jobspipe.dev - **Sign up (free tier):** https://jobspipe.dev/signup --- Generated from structured data. View the rendered page at https://jobspipe.dev/sources/rippling. --- Building this integration yourself? The steps above work. The alternative is one API over 30+ sources, already normalized and deduplicated. Try it right now - no key, no signup: ```bash curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search ``` Sample data, exact live schema. For live data get a free key (1,000 jobs to start) at https://jobspipe.dev/signup, then swap /v1/sandbox/jobs/search for /v1/jobs/search with an Authorization: Bearer header. Full agent index: https://jobspipe.dev/llms.txt?src=md-twin