At a glance
- Availability: Experimental (how to enable).
- Auth: API key.
- Connection: The key from
RIPPLING_API_TOKENis sent as theBearerprefixedAuthorizationheader. - Docs: https://developer.rippling.com/documentation/base-api
Credentials
Set these per environment. See Connect an integration.Setup
- Confirm API access: Rippling API access is not open by default. Customers can obtain an API token for custom integrations through their Rippling account (API access may require a plan add-on); software vendors register an app at https://developer.rippling.com and receive tokens once approved.
- Get your API token: As a Rippling admin, create or retrieve your company API token from the Rippling admin console (Settings → Company API / custom integration settings), or use the access token issued for your approved app integration.
- Store the token: Add RIPPLING_API_TOKEN=<your token> to your .env file. Requests are sent to https://api.rippling.com/platform/api with an Authorization: Bearer header.
- Verify access: Run the List Employees tool. The token’s scopes (granted at creation/approval) determine which resources are readable; a 403 means the token lacks the scope for that endpoint.
- This connector targets the token-authenticated platform API (api.rippling.com/platform/api); Rippling’s newer REST API for App Shop partners uses OAuth app installs and is not covered here
- List endpoints paginate with limit/offset (recommended max limit 100)
- Returned data is limited by the scopes granted to your token or app
Tools
Example prompts
- List employees from Rippling and summarize headcount by department and team.
- Check Rippling for approved leave requests overlapping this week and tell me who is out of office.
- Look up an employee I specify in Rippling and summarize their role, department, and work location.