# Rippling setup for PopMCP You paste one value into PopMCP: an API token you make in Rippling under Developer, API credentials. One token belongs to one Rippling company and acts as the person who made it, within the scopes ticked on it, so there is nothing to choose afterwards. - Auth: API credentials - Setup time: 2 min - API base URL: https://rest.ripplingapis.com - Credentials screen: https://app.rippling.com/api-tokens/tokens - Provider docs: https://developer.rippling.com/documentation/rest-api/essentials/api-tokens ## Approval required before this works No one reviews you, but Rippling's documentation lists the Rippling API SKU as a requirement, and its endpoints each name the product they need. A company without API access cannot use a token. - Typical wait: None once your company has API access. Otherwise it depends on your Rippling account manager. - Cost: Rippling sets this with you. Ask your Rippling account manager. - Blocked until approved: Everything without API access. Some tools also need their own Rippling product, such as Global Payroll or Spend Management, and answer 403 without it. - Works meanwhile: Decide who should make the token, since it sees only what that person can see, and which scopes your AI should have. ## Before you begin - A Rippling account allowed to create API tokens: the permission is called Create and manage API Tokens - API access on your company's Rippling plan: Rippling's documentation lists the Rippling API SKU as a requirement - Ideally an admin makes the token, because it can only see what the person who makes it can see ## Get your credentials ### 1. Open API credentials Sign in to Rippling, open Developer, and choose API credentials. The direct link is `app.rippling.com/api-tokens/tokens`. Then choose New API token. Screen: https://app.rippling.com/api-tokens/tokens ### 2. Name the token Give it a name such as `PopMCP` and a unique identifier, which cannot be changed later. Leave the API version on the newest one offered. Screen: https://developer.rippling.com/documentation/rest-api/essentials/api-tokens ### 3. Tick the scopes Tick the scopes for what your AI should reach. Each area has a read scope and often a read and write one, such as `leave-requests.read` and `leave-requests.read-write`. Include `companies.read` so PopMCP can show your company's name. For read-only use, tick only the ones ending in `.read`. You can only tick what your own permissions allow. Screen: https://developer.rippling.com/documentation/rest-api/essentials/permissions ### 4. Copy the token Finish creating it and copy the token. Rippling shows it once. If you lose it, revoke it and make another. Rippling emails the owner and the company's admins whenever a token is created, so let them know. Screen: https://app.rippling.com/api-tokens/tokens ### 5. Connect in PopMCP In PopMCP open Rippling in the marketplace, paste the token into Rippling API token, and click Connect. PopMCP checks it with one read of your company. Screen: https://app.popmcp.com/marketplace ### 6. Check it is connected Rippling shows as Connected, labelled with your company's name. Ask your AI *how many people do we have?* to try it. Connections start read-only: to let your AI make changes, allow write actions in PopMCP and make sure the token has the read and write scopes. Screen: https://app.popmcp.com/marketplace ## Fields PopMCP asks for - Rippling API token (apiToken) [required]: In Rippling open Developer, then API credentials, and choose New API token. Give it a name, tick the scopes for what your AI should reach, then copy the token: Rippling shows it once. Stored encrypted. ## Verify PopMCP shows the Rippling connector as Connected, labelled with your company's name, after one read of your company. If the token cannot read the company, PopMCP tries the token owner's own record and then a simple list, and connects with what it can see. ## Troubleshooting ### Rippling did not accept this token Cause: The token was copied only in part, was revoked, its owner left the company, or it went 30 days without use. Fix: Make a new token under Developer, API credentials, copy all of it, and reconnect Rippling in PopMCP. ### A tool says a scope is missing Cause: The token was made without that scope, its owner's permissions do not reach that data, or your company does not have that Rippling product. Fix: Edit the token under Developer, API credentials and tick the scope. If you cannot tick it, ask an admin to make the token instead. ### A field comes back empty Cause: Rippling leaves out what the token cannot see. PopMCP names those fields as hidden_fields in the answer. Fix: Add the scope, or have someone with access to that data make the token. Compensation, for example, needs compensations.read and an owner who can see pay. ### Some people are missing from a list Cause: The token only sees people its owner can see. A manager's token reaches only their reports. Fix: Have someone whose permission profile covers the entire company make the token. ### A tool ending in _v1 is refused Cause: These use Rippling's older API. A token made for the current API may not be allowed there. Fix: Ask your AI to look for the same data with a current tool. If there is none, ask your Rippling account manager about access to the older API. --- Source: https://www.docs.popmcp.com/docs/integrations/rippling/