Rippling · Rate Limits
Rippling Rate Limits
Rippling enforces per-token rate limits across the Platform API. Limits are documented per partner tenant and are typically applied as a sliding window on requests-per-minute. When exceeded, Rippling returns HTTP 429 and clients must back off and honor any Retry-After header.
4 Limits
Throttle: 429
HRHCMITPayrollRate LimitingThrottling
Limits
Per Token Default token
Default sliding-window limit applied per access token. 429 returned with Retry-After header when exceeded.
Listing / Search Endpoints token
Higher cost per request; use pagination cursors and avoid wide list polling.
SCIM Provisioning connection
SCIM provisioning is rate-limited per IdP connection; large bulk operations should be batched.
Webhook Delivery subscription
Webhooks are delivered with retry-on-5xx; receivers must respond within the platform timeout to avoid retry storms.
Policies
Backoff Strategy
Exponential backoff with jitter on 429 responses; honor Retry-After and avoid retrying without elapsed wait.
Pagination
Always paginate list endpoints rather than scanning entire collections to remain inside per-endpoint limits.
Webhook-Plus-Polling
Prefer webhooks for change notification and reduce poll frequency on list endpoints.