Rippling

Connect Rippling to sync people, employment status, start and end dates into the personnel register.

Connect with an API token

1. In Rippling:

   1. Sign in to Rippling as the user who will own the token. Tokens inherit the creator's permission profile and ownership cannot be transferred, so use an account whose profile can see the worker and user data Safeguard needs.
   2. Go to Tools > Developer > API Tokens and create an API token there.
   3. Give the token the scopes Safeguard needs, for example workers.read to list workers. Access is the intersection of the owner's permission profile and the token's scopes.

   Rippling's public documentation does not cover every step.

   Rippling API tokens are created in Tools → Developer → API Tokens and passed as 'Authorization: Bearer <token>' to https://rest.ripplingapis.com. Access is the intersection of the owner's permission profile and the token's scopes; a field returning null often means the token cannot see it, and a 403 or 'Insufficient oauth scopes' means add the documented scope and confirm the owner's profile can see that data. Tokens are revoked if the owner is terminated or the token is unused for 30 days, and ownership cannot be transferred. Verification (2026-10-07): the API Tokens and Permissions pages on developer.rippling.com render with JavaScript behind a Cloudflare check and could not be read; only developer.rippling.com/llms.txt was readable. The create button, the Name / Unique identifier / API version fields, the users.read and employment-types.read scope names, the required admin permissions, the direct URL and the one-time display were removed because no fetched source states them.

   Source: developer.rippling.com, developer.rippling.com, developer.rippling.com, checked 2026-10-07.

   The permissions Safeguard needs: workers:read, users:read, employment_types:read.

2. On Compliance › Connectors, open Rippling, click Connect, choose API token and fill in:

   Field	What to enter
   API token	Required. Create under Tools → Developer → API Tokens with the workers.read and users.read scopes. Stored encrypted and never shown again.

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Rippling and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• HRIS connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks