Rippling: Platform APIs are returning 403s
Affected components: Identity & App Management - Platform APIPlatform API
Timeline of updates
- resolved
Between approximately 10:15am and 12:04pm PST, requests to our V2 API returned errors. This affected integrations and workflows using the V2 API, including custom-object API calls and Rippling Functions that call these endpoints. V1 API availability was unaffected.
The issue has been fully resolved.
Changes Rewindex caught on this incident
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-07 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
f7d3a2396d58aa65…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on status.rippling.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Rippling, started 2026-11-07 21:25 UTC, resolved after 0 min, 1 update(s); edited after publishing.
- Title
- Platform APIs are returning 403s
- Vendor
- Rippling
- Date
- URL
- https://rewindex.com/company/rippling/incidents/038xt222tn3g
Rippling profileRecent Rippling incidentsAll outages on November 7, 2026Rippling in November 2026MarkdownJSON