Rippling
Version
This integration utilizes the Rippling Workers API.
Base URL
The base URL used for all Rippling API endpoints contains the Environment domain (ripplingapis.com for production, ripplingpreviewapis.com for sandbox):https://rest.environment_domain
Authentication & Authorization
The DataGrail Rippling integration connects using token authentication which requires an API Key.
Scopes
The Rippling integration requires specific scopes that must be granted in order to function for a given capability.
| Scope | Base | Access |
|---|---|---|
workers.read | ✅ | ✅ |
workers.sensitive.personal.read | ✅ |
Endpoints Utilized
DataGrail uses the following endpoints to authorize and test the connection:
Limits
Limits in Rippling are calculated using the leaky
bucket algorithm. All requests that are made after rate limits have been
exceeded are throttled and an HTTP 429 Too Many Requests error is returned.
Requests succeed again after enough requests have emptied out of the bucket.
- DataGrail supports requests throttling to stay within 70-80% of specified service rate limits.
- DataGrail processes API responses with HTTP 429 status to interrupt requests, waiting and retrying (using an exponential backoff strategy).
Capabilities
Access
DataGrail's Rippling integration provides Synchronous Access capabilities for the following supported identifier category: Email.Data Interactions
For Access requests, DataGrail will take the following actions:
- Retrieve the list of workers matching the Data Subject's work email address.
Endpoints Utilized
Disclaimer: The information contained in this message does not constitute as legal advice. We would advise seeking professional counsel before acting on or interpreting any material.