Rippling APIats.rippling.com ↗
List open jobs and retrieve full application form definitions from any public Rippling ATS job board. Access fields, sections, locations, and job metadata.
What is the Rippling API?
This API exposes 2 endpoints that cover public Rippling ATS job boards: list_jobs pages through all open postings on a board, and get_application_form returns the complete form definition for a single listing — every section, field type, required flag, and answer choices — alongside job metadata like department, work locations, and employment type.
curl -X GET 'https://api.parse.bot/scraper/5ccffe03-1ea1-46bb-b09f-7122bd03bb05/get_application_form?job_id=0fcbe748-d014-44b2-99a9-0b00a72c5eef&job_board_slug=camlin-careers' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns the application form definition for one Rippling job listing in a single request. The result carries basic job metadata (title, company, department, work locations, employment type) and an ordered list of `sections`; the first section is the built-in personal-information block (name, email, pronouns, phone, location, résumé, cover letter, ...) and each following section is an employer questionnaire attached to the posting (e.g. one shape: a country-specific screening questionnaire with visa, salary and hybrid-work questions). Each field carries a stable `key`, `title`, `description`, `field_type` (e.g. SHORT_ANSWER, PHONE_NUMBER, PRONOUN, FILE), `data_type` (null for built-in fields), `required`, `choices` (empty for free-text fields), `multi_select` and `other_enabled`. Also reports whether an EEOC questionnaire is enabled and any video screening questions. A job id that does not exist on the board (including a listing that has since closed) yields an input-not-found error.
| Param | Type | Description |
|---|---|---|
| job_idrequired | string | Job listing UUID: the segment that follows /jobs/ in the listing URL, as emitted by list_jobs.jobs[*].job_id. |
| job_board_slugrequired | string | Job-board slug: the path segment that follows ats.rippling.com/ in a job listing URL. |
{
"type": "object",
"fields": {
"job_id": "UUID of the job listing",
"sections": "ordered array of form sections, each {id, name, fields[]}; fields carry key, title, description, field_type, data_type, required, choices, multi_select, other_enabled",
"job_title": "listing title",
"department": "department name",
"company_name": "hiring company",
"total_fields": "integer count of fields across all sections",
"job_board_slug": "slug of the job board the listing belongs to",
"work_locations": "array of location strings",
"employment_type": "employment type label (e.g. Full-Time)",
"video_screening_questions": "array of video screening questions attached to the posting (empty when none)",
"eeoc_questionnaire_enabled": "boolean, whether an EEOC self-identification questionnaire is part of this application"
},
"sample": {
"data": {
"job_id": "72d072b5-fbc0-4e67-b6d9-58edb3873efb",
"sections": [
{
"id": "basic",
"name": "Personal information",
"fields": [
{
"key": "first_name",
"title": "First name",
"choices": [],
"required": true,
"data_type": null,
"field_type": "SHORT_ANSWER",
"description": "",
"multi_select": false,
"other_enabled": false
},
{
"key": "resume",
"title": "Resume",
"choices": [],
"required": true,
"data_type": null,
"field_type": "FILE",
"description": "",
"multi_select": false,
"other_enabled": false
}
]
},
{
"id": "6a903ade3a012ec93c6ae518",
"name": "Spain Questionnaire",
"fields": [
{
"key": "a2850f77-7c71-41be-b838-d7a7ab304a31",
"title": "Do you require a company sponsored VISA (either now or in the future)?",
"choices": [],
"required": true,
"data_type": "Text",
"field_type": "SHORT_ANSWER",
"description": "",
"multi_select": false,
"other_enabled": false
}
]
}
],
"job_title": "Regional Marketing Manager - Europe",
"department": "Marketing",
"company_name": "Camlin Energy Ltd",
"total_fields": 12,
"job_board_slug": "camlin-careers",
"work_locations": [
"Málaga, Spain"
],
"employment_type": "Full-Time",
"video_screening_questions": [],
"eeoc_questionnaire_enabled": false
},
"status": "success"
}
}About the Rippling API
Listing Jobs on a Rippling Board
list_jobs takes a job_board_slug (the path segment after ats.rippling.com/ in any listing URL) and an optional 0-based page integer. Each page holds up to 20 rows. The response includes jobs, an array where each entry carries job_id, job_title, department, work_locations, workplace_types, and a direct url. A posting open in multiple locations appears as a separate row per location, matching how the board itself renders listings. Top-level fields total_jobs, total_pages, has_more, board_title, and company_name give you enough context to paginate without guessing.
Retrieving Application Form Structure
get_application_form accepts a job_id (the UUID segment after /jobs/ in a listing URL, or taken directly from list_jobs) and the same job_board_slug. It returns an ordered sections array; the first section is always the built-in personal-information block. Each section has an id, a name, and a fields array. Individual fields carry key, title, description, field_type, data_type, required, and where applicable an array of choices. The response also surfaces video_screening_questions attached to the posting — an empty array when none are present — plus top-level employment_type, work_locations, department, and total_fields.
Combining the Two Endpoints
The typical workflow is to call list_jobs to collect job_id values across pages, then call get_application_form for any listing you want to inspect in detail. Because job_board_slug is required by both endpoints, you can target any publicly accessible Rippling-hosted board, not just a single company's.
The Rippling API is a managed, monitored endpoint for ats.rippling.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when ats.rippling.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official ats.rippling.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Aggregate open roles across multiple Rippling-hosted company boards into a unified job feed.
- Audit application form complexity by comparing
total_fieldsand section counts across postings. - Extract
work_locationsandworkplace_typesto filter remote vs. on-site roles programmatically. - Map
departmentandemployment_typedistributions across a company's current openings. - Detect video screening questions on postings to flag roles with additional screening steps.
- Track when new listings appear on a board by polling
list_jobsand comparingjob_idsets. - Pull form field choices (e.g. dropdown options) to understand what answers a specific application accepts.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Rippling provide an official public API for its ATS job boards?+
How does `list_jobs` handle a posting that is open in more than one location?+
jobs array, matching how the board itself lists them. The work_locations field on each row identifies the specific location. Use total_jobs and total_pages to understand the true row count, which may exceed the number of unique postings.Can I retrieve closed, draft, or expired job postings?+
list_jobs returns only the postings currently visible on the public board — closed, draft, and expired listings are not included. You can fork this API on Parse and revise it to add an endpoint that tracks historically observed job IDs if you need to monitor listings over time.Does `get_application_form` return submitted applications or applicant data?+
get_application_form returns only the form definition: sections, field metadata, required flags, choices, and video screening questions attached to the posting. Submitted application data requires authenticated access and is not covered. You can fork this API on Parse and revise it to add endpoints if Rippling exposes relevant authenticated routes you have access to.Is there a way to search or filter jobs by keyword, department, or location within a single request?+
list_jobs endpoint does not accept filter parameters — it returns all open listings on a board paginated by page. Filtering by department, work_locations, or other fields must be done client-side after retrieving pages. You can fork this API on Parse and revise it to add server-side filtering logic if needed.