# Rippling Jobs Scraper - ATS Board, Salary & Apply Links (`haketa/rippling-jobs-scraper`) Actor

Scrape every open role from any company's Rippling ATS board (ats.rippling.com): title, department, location, remote/hybrid/onsite, salary range, full description & apply link. No API key, no login. Filter by keyword, location, workplace type, country & salary.

- **URL**: https://apify.com/haketa/rippling-jobs-scraper.md
- **Developed by:** [Haketa](https://apify.com/haketa) (community)
- **Categories:** Jobs
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Rippling Jobs Scraper

Scrape **every open job** from any company that runs its hiring on **Rippling ATS** (`ats.rippling.com/{company}/jobs`). The board is backed by a public JSON API, so this actor needs **no API key, no login and no browser** — give it the companies you care about and get a clean, flat, analysis-ready row per role, with the **structured salary range** Rippling boards publish well.

Great for **job boards and aggregators**, **recruiters and sourcers**, **compensation / market intelligence** (who's hiring, where, and for how much), and **hiring analytics**.

### What you get per job

| Field | Description |
|---|---|
| `title` | Role title |
| `board` | Rippling board slug |
| `department` | Department name |
| `locations`, `primaryLocation` | Every location — name, city, state, country, ISO code |
| `workplaceTypes`, `isRemote` | `remote` / `hybrid` / `onsite` (a role can list several) + boolean flag |
| `employmentType` | Full-time / contract / intern … *(detail)* |
| `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryInterval` | Structured pay range *(detail)* |
| `payRanges` | All published ranges (per location, with currency & frequency) *(detail)* |
| `postedAt` | When the role was posted *(detail)* |
| `companyName`, `descriptionText` | Company name + full job/company description as clean text *(detail)* |
| `url` | The public posting URL |

### How it works (two-tier, no wasted requests)

Rippling's board API is split in two: a **cheap list** endpoint (title, department, locations) and a **rich detail** endpoint (salary, description, dates). This actor fetches each board's full list, applies the cheap filters **first**, then enriches only the surviving roles with a **concurrent batch** of detail calls. Turn off **Fetch job details** for a fast, list-only pass.

### Input

```json
{
  "boards": ["gather", "https://ats.rippling.com/framework/jobs", "rippling"],
  "searchTerm": "engineer",
  "workplaceType": "remote",
  "country": "US",
  "minSalary": 150000,
  "maxItems": 200
}
```

- **boards** — slugs or any `ats.rippling.com` URL, one per line. Paste a full board/posting URL and the slug is parsed out automatically.
- **searchTerm / location / department / workplaceType / country** — list-level filters (applied before detail calls).
- **employmentType / minSalary** — detail-level filters (force details on; roles without a published salary are dropped when `minSalary` is set).
- **fetchDetails / includeDescription** — control enrichment and dataset size.
- **maxItems** — total cap; also bounds how many roles get detail calls.

### How to find the companies

Rippling does **not** offer a global search across companies. Bring your own list: a target-account or competitor list, a VC/accelerator portfolio page, or a careers link that points at `ats.rippling.com/<slug>/jobs` — that `<slug>` is what you paste.

### Notes

- No key and no anti-bot, but running through **Apify Proxy** (default) spreads requests across IPs and avoids rate-limiting on large boards (some boards list hundreds of roles).
- Boards that don't exist or are empty are skipped with a warning — they don't fail the run.
- The list endpoint carries no salary/description/dates by design; those only exist on the detail endpoint, which is why enrichment is a separate, concurrent step.

# Actor input Schema

## `boards` (type: `array`):

Companies whose Rippling board you want to scrape. Paste the slug (e.g. `gather`) or any ats.rippling.com URL (e.g. `https://ats.rippling.com/gather/jobs`) — one per line. Rippling has no cross-company search, so bring your own list. The slug is the first path segment after ats.rippling.com.

## `searchTerm` (type: `string`):

Keep only roles whose title or department contains this text (case-insensitive). Leave empty for all roles.

## `location` (type: `string`):

Keep only roles with a location (city / state / country) containing this text, e.g. `New York`, `United States`, `London`. Case-insensitive substring match.

## `department` (type: `string`):

Keep only roles whose department contains this text, e.g. `Engineering`, `Sales`. Case-insensitive.

## `workplaceType` (type: `string`):

Keep only roles that offer this workplace type (a role can list several).

## `employmentType` (type: `string`):

Keep only roles whose employment type contains this text, e.g. `full-time`, `contract`, `intern`. Requires details to be fetched. Case-insensitive.

## `country` (type: `string`):

Keep only roles with a location in this country, given as a 2-letter ISO code, e.g. `US`, `GB`, `CA`. Case-insensitive.

## `minSalary` (type: `integer`):

Keep only roles whose salary range top end is at least this amount (in the posting's own currency). Roles without a published salary are dropped. Setting this forces details to be fetched. 0 = no salary filter.

## `fetchDetails` (type: `boolean`):

Call the per-job detail endpoint to add salary range, employment type, posting date, company name and full description. Turn off for a fast, list-only run (title, department, locations & links only).

## `includeDescription` (type: `boolean`):

Include the full job + company description text in each row (requires 'Fetch job details'). Turn off for a leaner dataset.

## `maxItems` (type: `integer`):

Maximum number of jobs to save across all boards. Also caps how many roles get detail calls, keeping cost bounded. 0 = no limit.

## `maxConcurrency` (type: `integer`):

How many requests to run in parallel (boards and detail calls). Higher = faster on big boards.

## `proxyConfiguration` (type: `object`):

Proxy settings. Apify Proxy (default) spreads requests across IPs and keeps Rippling's rate-limiting at bay on large boards.

## Actor input object example

```json
{
  "boards": [
    "gather",
    "https://ats.rippling.com/framework/jobs",
    "rippling"
  ],
  "searchTerm": "engineer",
  "workplaceType": "any",
  "country": "US",
  "minSalary": 0,
  "fetchDetails": true,
  "includeDescription": true,
  "maxItems": 50,
  "maxConcurrency": 8,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `jobs` (type: `string`):

Job postings scraped from the Rippling ATS boards — role, department, location, workplace type, salary range, description and apply links.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "boards": [
        "rippling",
        "gather",
        "framework"
    ],
    "maxItems": 50,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("haketa/rippling-jobs-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "boards": [
        "rippling",
        "gather",
        "framework",
    ],
    "maxItems": 50,
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("haketa/rippling-jobs-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "boards": [
    "rippling",
    "gather",
    "framework"
  ],
  "maxItems": 50,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call haketa/rippling-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,haketa/rippling-jobs-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/E6c2P3OYnOP33l7yn/builds/2YiAI7IBSaboP6qsz/openapi.json