---
title: "Rippling API"
description: "Rippling API: the partner-gated, OAuth-scoped platform API, the public ats.rippling.com careers pages, and how to reach the postings in one call."
canonical: https://jobspipe.dev/sources/rippling
---

# Rippling API

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; roles from Rippling Recruiting are public on careers pages under ats.rippling.com. 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 has no public cross-employer jobs API, and JobsPipe does not collect Rippling. This page explains what Rippling exposes and how to reach the same employers through the boards JobsPipe does collect.

**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 (LinkedIn, Indeed, Y Combinator, Naukri, Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever, Paylocity).

## 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. 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.

### Scrape individual Rippling careers pages

Possible per employer you already know. Public HTML, no directory.

### 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

### 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.

### 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?

Read that company's public careers page, hosted by Rippling under ats.rippling.com or on its own domain. It is public HTML with no feed and no directory, so each employer is a separate scrape. 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.

## Does Rippling have an API?

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. 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 this source and 30+ others, already normalized and deduplicated. Try it right now - no key, no signup:

```bash
curl -X POST https://api.jobspipe.dev/v1/sandbox/jobs/search \
  -H "Content-Type: application/json" \
  -d '{"job_title_or":["software engineer"],"limit":5}'
```

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