Rippling MDM

Record your Rippling MDM connection as hris evidence. Automated collection is not available for this provider yet.

Connect with an API token

1. In Rippling MDM:

   1. Sign in to Rippling as the user who will own the token. The token inherits the owner's permission profile, and ownership can't be transferred later, so use a stable admin or integration user.
   2. Go to Tools › Developer › API Tokens and create an API token, selecting only read scopes (for example workers.read for the employee roster).
   3. Copy the token and paste it into API token / Personal access token. Rippling sends it as Authorization: Bearer <token>.
   4. Effective access is the intersection of the token owner's permission profile and the token's scopes. Grant read-only scopes and use an owner whose permission profile can see the device and employee data you need.

   Where to find the other values:

   • Base URL (optional): REST Platform API v2: https://rest.ripplingapis.com.
   • Account / Org / Workspace (optional): Tokens are bound to one company. Call List companies (GET https://rest.ripplingapis.com/companies) with the token to see the company ID.

   Rippling MDM's public documentation does not cover every step.

   The menu path, token behavior and base URLs come from Rippling's official developer index; the token page itself is client-rendered and could not be read, so the create-button label, the scope-picker labels and whether the token is shown only once are unconfirmed. Tokens are revoked if the owner is terminated or the token goes unused for 30 days. No device/MDM inventory endpoint or device read scope appears in Rippling's public v2 index, so automated MDM evidence may not be reachable through this token. Verification: the V1 base URL and the API Scope Reference were not found in the readable source, so they were removed.

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

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

   Field	What to enter
   API token / Personal access token	Required. Stored encrypted and never shown again.
   Base URL (optional)	—
   Account / Org / Workspace (optional)	—

3. Click Connect with token.

Frameworks

Rippling MDM publishes no API for what these tests check, so its evidence is an attestation: connect it to record the connection, then attest the result. An accepted attestation counts toward each control below.

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