Rippling Platform API

Name: Rippling Platform API
Brand: Rippling Platform API
Availability: InStock

✓ Official Vendor SpecHR recruitingEmployee Managementbearer29 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Rippling Platform API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Rippling Platform API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Rippling Platform API.

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

GET STARTED

Start building with Rippling Platform API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Rippling Platform API for, with concrete tasks.

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

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.

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.

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

Key Endpoints

29 endpoints — rippling's base platform api for managing employees, companies, departments, teams, groups, leave management, custom fields, work locations, levels, and other hr/workforce resources.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Rippling Platform API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'get current authenticated user') and Jentic returns the matching Rippling Platform API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Rippling Platform API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Rippling Platform API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.

Rippling Platform API

Connect the Rippling Platform API to your agent

Capabilities

Start building with Rippling Platform API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs