--- title: "How to get a Rippling API key?" description: "**Canonical URL:** https://jobspipe.dev/answers/how-to-get-rippling-api-key" canonical: https://jobspipe.dev/answers/how-to-get-rippling-api-key last_updated: 2026-09-18 --- # How to get a Rippling API key? > A Rippling API key is an API token that someone inside a Rippling customer account creates for that company's own data. In Rippling, open the tools menu, go to the developer section, choose API tokens, create a token and select its scopes. Software vendors serving many customers do not use tokens: they register as App Shop partners and receive OAuth credentials instead. **Canonical URL:** https://jobspipe.dev/answers/how-to-get-rippling-api-key **Topic:** Job board and ATS APIs (https://jobspipe.dev/sources/rippling) Rippling's documentation states that a token's access is the intersection of two things: the permission profile of the person who created it and the scopes selected on the token. A token therefore cannot see more than its owner can in the product, which is why it is normally created by an administrator with broad permissions. When a field comes back empty, the usual cause is that the owner's profile or the token's scopes do not cover it. Tokens are tied to their owner. Rippling revokes a token when its owner leaves the company or when it goes unused for a period, and ownership cannot be transferred, so choose the owner with continuity in mind. The partner route is separate: create a partner company in the developer portal, build against a test company, pass Rippling's review and publish a listing. Each customer that installs the app grants scopes, and the resulting access token maps to that one company. Neither route reads data across companies, and Rippling's guidance calls using a key on behalf of another organization a terms of service violation. That matters if the goal is job postings. JobsPipe does not collect Rippling, and a search with source_or set to rippling returns no rows. Rippling employers publish roles on public careers pages and usually syndicate them to LinkedIn and Indeed, which JobsPipe does collect. POST /v1/jobs/search with company_name_partial_match_or finds those employers, and the sources field names the board each record came from. Decide which case you are in first. For your own company's Rippling data, ask an administrator to create a scoped token and store it as a secret, never in source code. To integrate with customers' accounts, start the App Shop partner process. For hiring data across employers, no Rippling key will help, and the JobsPipe sandbox search endpoint shows the alternative without a key. ## Related questions ### Who can create a Rippling API token? Someone inside the customer's Rippling account who can reach the API tokens tool in the developer section. Because a token inherits its creator's permission profile, the useful choice is a person whose profile already covers the data the integration needs, typically an administrator. Outside vendors cannot create tokens for a customer and use the App Shop OAuth route instead. ### Why does my Rippling API token return empty fields? Rippling's documentation says an empty value often means the token cannot see the field, not that the field is blank. Access is the overlap between the owner's permission profile and the token's scopes. Check that the scope for that resource is selected and that the token's owner can see the same data inside the product. ### Do Rippling API tokens expire? Rippling's developer documentation says tokens are revoked when their owner leaves the company or when the token goes unused for a period, and that ownership cannot be transferred. An integration that must run unattended should therefore be owned by a stable account and called regularly. Check the documentation for the current inactivity window before relying on it. ### Can a Rippling API key read another company's data? No. A customer token reaches only the company where it was created, and a partner's OAuth access token maps to the one customer that installed the app. Rippling's guidance treats using a key on behalf of another organization as a terms of service violation. Data across employers, such as job postings, has to come from public sources. ## More answers - [Does Rippling have an API?](https://jobspipe.dev/answers/does-rippling-have-an-api) - [Where to find API key?](https://jobspipe.dev/answers/where-to-find-your-api-key) - [Does LinkedIn have an API?](https://jobspipe.dev/answers/does-linkedin-have-an-api) Data behind these answers is published as shares only; every figure can be reproduced against the JobsPipe API (https://jobspipe.dev/jobs-api). --- AI agents: the full machine-readable index of this site is https://jobspipe.dev/llms.txt?src=md-twin - API quickstart, no-key sandbox (POST https://api.jobspipe.dev/v1/sandbox/jobs/search), MCP server, pricing. Free key: https://jobspipe.dev/signup