canonical: https://jentic.com/apis/rippling.com/rippling

# Rippling Platform API

Rippling's base platform API for managing employees, companies, departments, teams, groups, leave management, custom fields, work locations, levels, and other HR/workforce resources. The API exposes 29 endpoints secured with bearer authentication.

## For AI agents

Programmatically get current authenticated user, get companies. Covers 29 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for hr and recruiting only.

## Capabilities

- Get current authenticated user
- Manage hr recruiting data programmatically
- Integrate Rippling Platform API into automated workflows
- Query and filter Rippling Platform API records by parameters
- Monitor Rippling Platform API operational status and events

## Use cases

### HR and Recruiting Operations

Use the Rippling Platform API to perform hr recruiting operations programmatically. The API provides 29 endpoints covering core functionality including get current authenticated user, get companies, get employees.

Example prompt: Call GET /me to get current authenticated user

### Automated Employees Management

Automate employees operations by combining multiple Rippling Platform API endpoints. Agents can get companies and then get employees in a single workflow.

Example prompt: Call GET /companies to get companies, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Rippling Platform API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'get current authenticated user', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /me | Get current authenticated user |
| GET | /companies | Get companies |
| GET | /employees | Get employees |
| GET | /employees/{employeeId} | Get employee by ID |
| GET | /employees/include_terminated | Get all employees including terminated |
| GET | /departments | Get departments |
| GET | /teams | Get teams |
| GET | /levels | Get levels |

## Key resources

- **Employees** — Manage employee records and profiles
- **Companies** — Retrieve company information
- **Departments** — Manage departments within a company
- **Teams** — Manage teams within a company
- **Groups** — Manage custom groups of employees

## Why Jentic

- **Setup:** Wiring the Rippling Platform API by hand means obtaining a bearer token through Rippling's OAuth flow, sending it on every call to the platform host, and paging through employees, departments, teams, and levels yourself. Through Jentic you install once, import the Rippling Platform API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Rippling puts the resource id in the URL path (/employees/{employeeId}), so a rule can pin your agent to one employee record and its reads. You choose the operations it may call, and these HR reads give the agent no write path unless you add one.
- **Credential handling:** Your Rippling token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list employees' or 'get the current authenticated user', and Jentic returns the matching Rippling Platform API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Greenhouse** — Alternative hr recruiting API
- **Lever** — Alternative hr recruiting API
- **Workday** — Complementary hr recruiting API

## FAQ

### What authentication does the Rippling Platform API use?

The Rippling Platform API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get current authenticated user with the Rippling Platform API?

Yes. Use the GET /me endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Rippling Platform API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get current authenticated user through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get current authenticated user'. Jentic returns the matching Rippling Platform API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Rippling Platform API have?

The Rippling Platform API exposes 29 endpoints covering employees, companies, departments operations.

### Can I limit what my agent is allowed to do with the Rippling Platform API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Rippling operations and credentials your agent may use. Because Rippling puts the resource id in the URL path, such as /employees/{employeeId}, you can pin the agent to a single employee record and its reads, and you choose whether it may also call broader endpoints like /employees, /companies, /departments, or /teams. These HR reads give the agent no write path unless you explicitly grant one.