# Rippling Jobs Scraper & API: Any Rippling Careers Board (`mrslm_data/rippling-jobs`) Actor Scrape open roles from any company's Rippling ATS job board: title, department, team, locations, employment type, pay range, posted date and apply link. - **URL**: https://apify.com/mrslm_data/rippling-jobs.md - **Developed by:** [MRSLM Data](https://apify.com/mrslm_data) (community) - **Categories:** Jobs - **Security:** Limited permissions - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.80 / 1,000 jobs 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 & API: Any Rippling Careers Board **Open roles from any company's Rippling ATS careers board (ats.rippling.com): title, department and team, all locations, employment type, pay range, posted date and apply link. $1.00 per 1,000 jobs.** Rippling Recruiting is the applicant tracking system inside Rippling's HR platform. Thousands of fast-growing US and European companies post their jobs on `ats.rippling.com//jobs`. This Actor turns any of those boards into clean rows you can filter, export and schedule. ### Quick start 1. Press **Start**. The form is already filled with this example input, so the first run returns real rows in under a minute: ```json { "companies": [ "rippling", "https://ats.rippling.com/useorigin/jobs" ], "maxJobsPerCompany": 10 } ``` 2. Swap in your own values, or call the Actor through the Apify API, Make, Zapier, n8n or the Python/JS clients with the same JSON. 3. Download the results as JSON, CSV or Excel from the **Output** tab, or schedule the run to repeat. **Full guide: How to Scrape Rippling ATS Job Postings, with Pay Ranges by Location** ### What the Rippling Jobs Scraper does You give the Actor Rippling board names (`rippling`) or careers URLs (`ats.rippling.com/useorigin/jobs`, job links and locale links such as `/en-GB//jobs` also work). It reads the board's public job list, applies your title, location and department filters, then opens each remaining job's public page for the details. Rippling lists a job once per office. The Actor merges those copies into a single row with every location, so you never pay twice for the same job. You only pay for jobs saved after your filters. - Pay ranges by location tier in `payRanges`, plus the first range in a simple `salary` column. - The full department tree in `departmentPath`, such as Engineering > HR Products > HRIS. - Posted date, employment type and its label ("Salaried, full-time", "Temporary / Intern"). - Set `includeDetails` to false for a faster, list-only run when you only need titles and links. ### Who it is for - **Recruiters and staffing agencies**: track openings at Rippling-hosted companies alongside your other target accounts. - **Compensation analysts**: collect published pay ranges per location tier, such as US San Francisco Bay Area versus US Tier 1. - **Sales teams**: spot companies hiring in a department you sell to. - **Job seekers**: follow specific companies and see the published pay before applying. ### Real example: engineering roles on two Rippling boards Say you want the engineering openings at Rippling itself and at Origin (`useorigin`), a smaller company that also hires through Rippling ATS. You want up to ten roles per company, with pay where it is published. #### Step 1: Enter the input Open the [Rippling Jobs Scraper](https://apify.com/mrslm_data/rippling-jobs) in Apify Console, switch the input form to **JSON** and paste this. It is the exact input used for the run in this guide: ```json { "companies": [ "rippling", "https://ats.rippling.com/useorigin/jobs" ], "titleKeywords": [ "engineer" ], "maxJobsPerCompany": 10 } ``` What each setting does: - `companies`: a bare board name and a full careers URL. Both forms work. - `titleKeywords`: keep jobs whose title contains any of these words, ignoring case. - `maxJobsPerCompany`: save at most ten jobs per company. #### Step 2: Run it Press **Start**. On 30 October 2026 this input finished with status `SUCCEEDED` in about 6 seconds and saved 10 rows to the run's dataset. The run was charged 10 `job` events plus one start event, so the bill was $0.01 on the Free/Bronze tier. The summary shows Rippling with 371 open jobs, of which 10 matched "engineer" before the cap, and Origin with 5 open jobs and 0 matches. Origin's board was found and read correctly; it simply had no engineering roles that day, so it cost nothing. #### Step 3: Read the output Here are the first rows of the real dataset, cut to the most useful columns: | title | location | employmentTypeLabel | salary | postedAt | |---|---|---|---|---| | Director of Engineering, HRIS Core Flows | San Francisco, CA | Salaried, full-time | | 2026-08-31T19:57:46.391Z | | Engineering Leader - Agentic Talent Products | San Francisco, CA | Salaried, full-time | {"min": 207000, "max": 345000, "currency": "USD"… | 2026-08-04T16:05:14.440Z | | Engineering Leadership | Bangalore, India | Salaried, full-time | | 2026-05-26T03:36:30.983Z | | Engineering Manager | Bangalore, India | Salaried, full-time | | 2026-09-07T08:20:08.749Z | | Engineering Manager - Financial Integrity | Bangalore, India | Salaried, full-time | | 2026-08-13T08:43:40.506Z | | Engineering Manager, HRIS Flow Platform | Toronto, Canada | Salaried, full-time | {"min": 186000, "max": 310000, "currency": "USD"… | 2026-05-27T23:53:05.205Z | | Engineering Manager - Inventory Management - IT | Seattle, WA | Salaried, full-time | {"min": 186000, "max": 310000, "currency": "USD"… | 2026-09-01T20:39:43.678Z | | Engineering Manager, Time Products | San Francisco, CA | Salaried, full-time | {"min": 186000, "max": 310000, "currency": "USD"… | 2026-03-27T15:49:56.178Z | | Full Stack Software Engineer Intern - Summer 202… | San Francisco, CA | Temporary / Intern | {"min": 10500, "max": 10500, "currency": "USD",… | 2026-09-21T16:23:18.392Z | | Machine Learning Software Engineer Intern - Summ… | San Francisco, CA | Temporary / Intern | | 2026-09-21T23:47:40.442Z | And one full row as JSON (long text shortened with …): ```json { "platform": "Rippling", "company": "rippling", "companyName": "Rippling", "jobId": "001c7945-723f-4062-be44-80e1e18276a3", "title": "Engineering Manager - Inventory Management - IT", "department": "Engineering", "departmentPath": [ "Engineering", "IT Products", "Device Management" ], "location": "Seattle, WA", "locations": [ "Seattle, WA", "San Francisco, CA" ], "workplaceType": "on-site", "employmentType": "salaried-ft", "employmentTypeLabel": "Salaried, full-time", "salary": { "min": 186000, "max": 310000, "currency": "USD", "period": "year", "text": null }, "payRanges": [ { "location": "US Tier 1", "min": 186000, "max": 310000, "currency": "USD", "period": "year", "isRemote": false } ], "postedAt": "2026-09-01T20:39:43.678Z", "url": "https://ats.rippling.com/rippling/jobs/001c7945-723f-4062-be44-80e1e18276a3", "applyUrl": "https://ats.rippling.com/rippling/jobs/001c7945-723f-4062-be44-80e1e18276a3/apply" } ``` What the ten real rows show: - **Half of them carry pay.** 5 of 10 rows have a published range. Engineering Leader - Agentic Talent Products in San Francisco is $207,000 to $345,000 a year. Three Engineering Manager roles (HRIS Flow Platform, Inventory Management - IT, Time Products) are $186,000 to $310,000. The three Bangalore roles have no range, which is typical because pay transparency laws are mostly a US matter, but neither do the San Francisco Director of Engineering and the Machine Learning intern, so do not assume every US role is covered. - **Ranges belong to a location tier.** In `payRanges`, each range names its tier: "US San Francisco Bay Area", "US Tier 1" or just "US". The Full Stack intern role lists a range per office: $10,500 a month in each of the San Francisco, New York and Seattle offices. `salary` holds the first range for quick sorting; use `payRanges` when you need them all. - **Read the tier, not just the city.** The Toronto-based Engineering Manager, HRIS Flow Platform shows a USD range whose tier is "US". The range applies to the US hiring tier, not to Toronto. That is how the company published it, and the Actor keeps it exactly as given. - **The department tree is useful.** `departmentPath` goes as deep as Engineering > HR Products > Workforce Management > Leave Management, which is much better than a single "Engineering" label for mapping where a company is investing. - **Order is the board's own.** With `newestFirst` off (the default for Rippling), the ten rows are the first ten matches in board order, with posted dates from March to September. Turn `newestFirst` on to sort by date first; it is slower on big boards because the Actor must read every matching job's page. ### Why the details step matters Rippling's public list page gives a title, a location and a link. The posted date, the employment type, the department tree, the company name and the pay ranges are only on each job's own page. With `includeDetails` on (the default), the Actor opens each saved job's page and fills those columns. With it off, the run is faster and you get the list-level columns only. Date-based options need the details of every matching job, not just the saved ones: `postedWithinDays` must know each job's date before it can drop it, and `newestFirst` must know every date to sort. Title, location and department filters run first to keep this quick, so combine them with a date filter on large boards. ### Output fields Each row in the dataset has these fields. The example column shows a value from the run above. | Field | What it means | Example from this run | |---|---|---| | `platform` | The ATS the job came from, e.g. Greenhouse, Lever or Workable. | Rippling | | `company` | The board name you gave, or the one the Actor detected. | rippling | | `companyName` | The company display name, when the board publishes it. | Rippling | | `jobId` | The ATS job ID. Stable from run to run, so use it to spot new jobs. | 98b559a6-c8b2-4ede-85d9-cbf4883da996 | | `title` | The job title as posted. | Director of Engineering, HRIS Core Flows | | `department / team` | Department and team, when the company sets them. | Engineering / HR Products | | `location / locations` | The main location text, plus every location for multi-office roles. | San Francisco, CA / San Francisco, CA | | `country` | Country, when the platform gives one. | (empty in this run) | | `workplaceType / isRemote` | remote, hybrid or on-site, plus a true/false remote flag. | on-site / no | | `employmentType` | full-time, part-time, intern and so on, when published. | salaried-ft | | `seniority` | Experience level, when the platform publishes one. | (empty in this run) | | `salary` | Structured pay range (min, max, currency, period, text) when the company publishes it; otherwise empty. | {"min": 207000, "max": 345000, "currency": "USD", "period":… | | `postedAt / updatedAt` | When the job was first published and last edited (ISO dates). | 2026-08-31T19:57:46.391Z / (empty in this run) | | `url / applyUrl` | The public job page and the application page. | https://ats.rippling.com/rippling/jobs/98b559a6-c8b2-4ede-85… / https://ats.rippling.com/rippling/jobs/98b559a6-c8b2-4ede-85… | | `boardUrl` | The company's careers board. | https://ats.rippling.com/rippling/jobs | | `scrapedAt` | When the row was read (UTC). | 2026-10-30T16:11:59.268Z | | `departmentPath` | The full department tree, top level first. | Engineering, HR Products | | `employmentTypeLabel` | Rippling's own label, such as "Salaried, full-time". | Salaried, full-time | | `payRanges` | Every published pay range, each with location tier, min, max, currency, period and remote flag. | {"location": "US San Francisco Bay Area", "min": 207000, "ma… | ### Export Rippling jobs to CSV, Excel or Google Sheets Every run saves its rows to a dataset, and a dataset can be downloaded in any common format. You do not need to write code for this. **From Apify Console.** Open the run, go to the **Output** tab and click **Export**. Pick CSV, Excel (XLSX), JSON, XML, HTML or RSS. You can tick only the columns you want, for example `company`, `title`, `location`, `employmentTypeLabel`, `salary`. Nested values such as lists are flattened into columns like `payRanges/0/min` in CSV and Excel. **From a URL.** The same export is a plain HTTPS link. Replace `` with the dataset ID shown on the run's Storage tab: ```bash ## CSV with just the columns you need curl -H "Authorization: Bearer $APIFY_TOKEN" \ "https://api.apify.com/v2/datasets//items?format=csv&clean=1&fields=company,title,location,employmentTypeLabel,salary,postedAt,url" -o rippling-jobs.csv ## Excel curl -H "Authorization: Bearer $APIFY_TOKEN" \ "https://api.apify.com/v2/datasets//items?format=xlsx&clean=1" -o rippling-jobs.xlsx ``` **Into Google Sheets.** You have three good options: 1. **One-off:** download the CSV and use **File > Import > Upload** in Google Sheets. Choose "Replace current sheet" to refresh an existing tab. 2. **Automatic, no code:** in Make, Zapier or n8n, use the Apify app's "Watch Actor runs" (or "Run Actor") trigger, then "Get dataset items", then the Google Sheets "Add row" action. Every scheduled run then lands in your sheet. Apify's own [Google Sheets Import & Export](https://apify.com/lukaskrivka/google-sheets) Actor can also append a dataset to a sheet, and you can chain it to this Actor's runs with an integration. 3. **Formula:** `=IMPORTDATA("https://api.apify.com/v2/actor-tasks/~/runs/last/dataset/items?status=SUCCEEDED&format=csv&token=")` always pulls the latest successful run of a saved task. The token sits in the formula, so anyone who can open the sheet can see it. Only use this in a private sheet. ### Schedule it to run every day at 7:00 Job boards change every day. A daily run with `postedWithinDays` set to 1 or 2 gives you only the new roles, which keeps each run small and cheap. Because `jobId` is stable, you can also keep the full list and compare it with yesterday's to see which roles closed. 1. In the Actor's input form, set up the input from Step 1 and click **Save as new task**. Give it a clear name such as `rippling-engineering-daily`. 2. Go to **Schedules > Create new**, set the cron expression to `0 7 * * *` and pick your timezone, so it runs every day at 7:00. 3. Add the task to the schedule and save. Each run gets its own fresh dataset. 4. Optional: on the task's **Integrations** tab, add a webhook, Slack or email notification for "Run succeeded", or connect Make, Zapier or n8n, so the new rows go where you need them. To fetch the newest results without looking up a run ID, use the task's last-run link: `https://api.apify.com/v2/actor-tasks/~rippling-engineering-daily/runs/last/dataset/items?status=SUCCEEDED&format=json`. ### Call it from the API (Python, JavaScript or curl) You can start the Actor from your own code with the official Apify clients. Put your API token (Console > Settings > API & Integrations) in an environment variable called `APIFY_TOKEN` rather than in the code. **Python** (`pip install "apify-client>=3"`). Tested with apify-client 3.4: ```python import os from apify_client import ApifyClient client = ApifyClient(os.environ["APIFY_TOKEN"]) run_input = { "companies": [ "rippling", "https://ats.rippling.com/useorigin/jobs" ], "titleKeywords": [ "engineer" ], "maxJobsPerCompany": 10 } run = client.actor("mrslm_data/rippling-jobs").call(run_input=run_input) ## apify-client 3.x returns a Run object, so use run.default_dataset_id for item in client.dataset(run.default_dataset_id).iterate_items(): print(item["title"], item["salary"]) ``` In apify-client 3.x, `call()` returns a typed object. Older examples that use `run["defaultDatasetId"]` were written for 1.x and 2.x and fail in 3.x with `TypeError: 'Run' object is not subscriptable`. **JavaScript / Node.js** (`npm install apify-client`): ```javascript import { ApifyClient } from 'apify-client'; const client = new ApifyClient({ token: process.env.APIFY_TOKEN }); const input = { "companies": [ "rippling", "https://ats.rippling.com/useorigin/jobs" ], "titleKeywords": [ "engineer" ], "maxJobsPerCompany": 10 }; const run = await client.actor('mrslm_data/rippling-jobs').call(input); const { items } = await client.dataset(run.defaultDatasetId).listItems(); console.log(items.length, items[0]); ``` **curl**, one request that runs the Actor and returns the rows as CSV (it waits up to 5 minutes, so keep the input small): ```bash curl -X POST "https://api.apify.com/v2/acts/mrslm_data~rippling-jobs/run-sync-get-dataset-items?format=csv" \ -H "Authorization: Bearer $APIFY_TOKEN" -H "Content-Type: application/json" \ -d '{"companies": ["rippling", "https://ats.rippling.com/useorigin/jobs"], "titleKeywords": ["engineer"], "maxJobsPerCompany": 10}' -o rippling-jobs.csv ``` ### What it costs The Actor uses pay-per-event pricing. **Job**: $1.00 per 1,000 on the Free and Bronze tiers, $0.90 on Silver and $0.80 on Gold. Each run also has a start fee of $0.00005 per GB of memory (one event at the default memory). You are not billed separately for compute on normal runs: the event prices are the whole bill. #### Price per event Current pay-per-event prices for this Actor on Apify, by Apify subscription plan: | Event (per 1,000) | Free / Bronze | Silver | Gold / Platinum / Diamond | |---|---|---|---| | Job (`job`) | $1.00 | $0.90 | $0.80 | | Actor start (once per run at the default memory, not per 1,000) | $0.00005 | $0.00005 | $0.00005 | You are charged only for the events in this table: nothing for compute, and nothing for searches that return no rows beyond the start fee. | Scenario | Free / Bronze | Silver | Gold | |---|---|---|---| | The run in this guide (10 jobs) | $0.01 | $0.00905 | $0.00805 | | Full export of Rippling's 371 open roles | $0.37 | $0.33 | $0.30 | | Daily new-roles feed over 40 Rippling boards, about 20 jobs a day (30 runs, 600 a month) | $0.60 | $0.54 | $0.48 | To cap spending, set **Maximum cost per run** in the run options (or `maxTotalChargeUsd` in the API). The Actor stops cleanly at the cap and you are never billed past it. ### Limits - It reads open jobs only. Closed roles are gone from the public board, so keep your own history if you need it. - Filters are plain keyword matches on the title, location or department text. `engineer` also matches "Engineering Manager" and "Solutions Engineer"; use `excludeTitleKeywords` to trim. - Descriptions are capped at 5,000 characters of plain text when `includeDescription` is on. - Rippling ATS boards only (ats.rippling.com). For other systems use the [ATS Jobs Scraper](https://apify.com/mrslm_data/ats-jobs). - Pay only where the company publishes it. Ranges are tied to the company's location tiers, which do not always match the job's office. - `postedWithinDays` and `newestFirst` read every matching job's page, so they are slower on boards with hundreds of roles. ### FAQ **Why is salary sometimes empty?** Rippling only shows pay where the company publishes it, which is often required in US states such as California, New York, Colorado and Washington. When it is published you get every range, per location tier. **Why do I get one row when the job is listed in five offices?** Rippling lists a job once per office. The Actor merges those into one row with all locations in `locations`, so you pay once. **Is a date filter slower?** A bit. The posted date is only on each job's own page, so with `postedWithinDays` or `newestFirst` the Actor reads every matching job before it picks the newest ones. **Do I need an API key or a login for the job board?** No. Every board this Actor reads is the public one behind the company's careers page. You only need your own Apify token to run the Actor. **Does it include recruiter or applicant data?** No. Only the public job ad. Application questions, recruiters and candidates are never read, and email addresses and phone numbers in descriptions are removed. **How fresh is the data?** Live. Each run reads the boards at that moment, so closed jobs disappear and new ones appear. **What happens if I mistype a company name?** That company is reported as not found in the run summary and costs nothing. The rest of the run carries on. **How do I get only new jobs every day?** Save your input as a task with `postedWithinDays` set to 1 and give it a daily schedule. For boards with irregular dates, set it to 2 and drop duplicates by `jobId`. **Can I run it on a schedule?** Yes. Save your input as a task and attach a schedule, as shown above. Each run is independent and returns the Rippling jobs available at that moment. **Does it work with Make, Zapier or n8n?** Yes. All three have an Apify app. Use "Run Actor" (or run a saved task), then "Get dataset items" to pass the rows to the next step, such as Google Sheets, Airtable, a CRM or Slack. **Can AI agents use it through MCP?** Yes. Apify's hosted MCP server can expose this Actor as a tool to any MCP client (Claude Desktop, Cursor, VS Code and others). Add `https://mcp.apify.com/?tools=mrslm_data/rippling-jobs` as a remote MCP server and sign in with your Apify account or API token. The agent fills in the same input fields shown above and gets the same rows back, billed at the same per-event prices. **Can I get ats.rippling.com jobs through an API?** Yes. You can run the Actor through the Apify API and retrieve its dataset; you do not need a Rippling board API key or login. Add board names or careers URLs to `companies` and set `maxJobsPerCompany` to limit results per company. **How do I export Rippling job postings to CSV or Google Sheets?** Download CSV from the run's Output tab, then import it into Google Sheets. You can also use Make, Zapier or n8n to send dataset rows to a sheet after each run. **How can I find pay ranges in Rippling job postings?** Leave `includeDetails` on to collect published ranges in `payRanges`, with the first range also in `salary`. Ranges are only available where the company publishes them and may be tied to a location tier. ### Related job board scrapers - [ATS Jobs Scraper](https://apify.com/mrslm_data/ats-jobs): Greenhouse, Lever, Workable, Recruitee, Personio, Breezy HR and Teamtailor in one format. - [Greenhouse Jobs Scraper](https://apify.com/mrslm_data/greenhouse-jobs), [Lever Jobs Scraper](https://apify.com/mrslm_data/lever-jobs) and [Workable Jobs Scraper](https://apify.com/mrslm_data/workable-jobs) for single-ATS boards. ### Is it legal? This Actor only reads pages and feeds that the website itself publishes to every visitor without a login. It obeys each site's robots.txt, keeps a polite request rate, and never tries to get past logins, paywalls, captchas or bot checks. It does not collect personal data such as emails, phone numbers or names of private individuals. You are responsible for how you use the data: follow the source site's terms, copyright and the privacy laws that apply to you (GDPR, CCPA, etc.). This tool is independent and not affiliated with or endorsed by Rippling or the companies whose boards it reads. # Actor input Schema ## `companies` (type: `array`): Rippling board names or careers URLs (ats.rippling.com//jobs, job links and locale links like /en-GB//jobs work too). One per line. ## `titleKeywords` (type: `array`): Keep jobs whose title contains any of these words (e.g. engineer, sales). Empty = all jobs. ## `excludeTitleKeywords` (type: `array`): Drop jobs whose title contains any of these words (e.g. intern). ## `locationKeywords` (type: `array`): Keep jobs whose location contains any of these (e.g. New York, London, remote). ## `departmentKeywords` (type: `array`): Keep jobs whose department or team contains any of these (e.g. engineering, sales). ## `remoteOnly` (type: `boolean`): Keep only jobs whose location says remote. ## `includeDetails` (type: `boolean`): Open each saved job for its posted date, employment type, pay ranges, company name and department tree. Turn off for a faster list-only run. ## `includeDescription` (type: `boolean`): Add the role description as plain text (up to 5,000 characters). Makes rows larger. ## `postedWithinDays` (type: `integer`): Keep only jobs posted in the last N days. 0 = any date. Needs the details of every matching job, so big boards take longer. ## `newestFirst` (type: `boolean`): Sort each company's jobs by posting date before the per-company limit. Needs the details of every matching job, so big boards take longer. ## `maxJobsPerCompany` (type: `integer`): 0 = all open jobs. ## `maxResults` (type: `integer`): Safety cap on saved jobs across the whole run. 0 = no cap. Your max cost per run is always respected. ## Actor input object example ```json { "companies": [ "rippling", "https://ats.rippling.com/useorigin/jobs" ], "remoteOnly": false, "includeDetails": true, "includeDescription": false, "postedWithinDays": 0, "newestFirst": false, "maxJobsPerCompany": 10, "maxResults": 0 } ``` # Actor output Schema ## `results` (type: `string`): All jobs as a dataset (JSON, CSV, Excel and more via the API or Console). ## `summary` (type: `string`): Jobs per board, boards that failed, and the stop reason. # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "companies": [ "rippling", "https://ats.rippling.com/useorigin/jobs" ], "maxJobsPerCompany": 10 }; // Run the Actor and wait for it to finish const run = await client.actor("mrslm_data/rippling-jobs").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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "companies": [ "rippling", "https://ats.rippling.com/useorigin/jobs", ], "maxJobsPerCompany": 10, } # Run the Actor and wait for it to finish run = client.actor("mrslm_data/rippling-jobs").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 '{ "companies": [ "rippling", "https://ats.rippling.com/useorigin/jobs" ], "maxJobsPerCompany": 10 }' | apify call mrslm_data/rippling-jobs --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,mrslm_data/rippling-jobs" } } } ``` 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 ` 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/FT2c757cTsRDxAFjN/builds/IOLCSs8RROH2qbKII/openapi.json