Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: API key.
  • Connection: The key from RIPPLING_API_TOKEN is sent as the Bearer prefixed Authorization header.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration.

​
Setup

  1. 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.
  2. 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.
  3. 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.
  4. 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.

​
Provider notes

  • 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
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as rippling__list_employees with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.