Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / HR recruiting / Rippling Platform API
Rippling Platform API logo

Rippling Platform API

71
AI ReadinessAI-Aware (A-)71/100
See full scorecard
Official vendor OpenAPI document · agent-readyHR recruitingEmployee Managementbearer29 EndpointsREST

For Agents

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

Use for: I need to current authenticated user, I want to companies, Search for employees, Find all employee by id

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

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.

Jentic One on GithubView OpenAPI Document

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.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frippling.com%2Frippling" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frippling.com%2Frippling" | 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

Monitor Rippling Platform API operational status and events

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

/departments

Get departments

GET

/teams

Get teams

GET

/levels

Get levels

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

R

Rippling Platform API

- AI-Aware (A-)
71/100
99
Foundational Compliance
63
Developer Experience & Jentic Compatibility
59
AI-Readiness & Agent Experience
94
Agent Usability
60
Security
72
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

59

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C+Signals: 4
79%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

55%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

60

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1
60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

72

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1
72%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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

Alternatives and complements available in the Jentic catalogue.

Alternative

Greenhouse

→

Alternative hr recruiting API

Choose Greenhouse when you need a different approach to hr recruiting operations

Alternative

Lever

→

Alternative hr recruiting API

Choose Lever when you need a different approach to hr recruiting operations

Complementary

Workday

→

Complementary hr recruiting API

Choose Workday when you need a complementary approach to hr recruiting operations

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

GET STARTED

Start building with Rippling Platform API

Explore with Jentic One
View OpenAPI Document