Payroll systems · Rippling
Rippling
Rippling's own documentation covers employees, pay statements, deduction write, hours and webhooks through the API. Access: Customer tokens; App Shop partners.
Integration method grade ? · field-level docs NOT publicly readable · last verified 2026-09-26 · Rippling Developer (not publicly readable)
What the API lets you do
| Question | Answer | Conf | What the documentation says |
|---|---|---|---|
| How do you get API access? | Customer tokens; App Shop partners | D | Customers create API tokens in Tools > Developer; third-party apps are built through the Rippling App Shop with OAuth. Source |
| Can you read employees and pay rates? | Yes — workers + compensation | D | v2 GET /workers expands employment and compensation, including annual_salary_equivalent and hourly_wage. Source |
| Can you read pay statements? | Global Payroll customers only | D | worker-payroll-records return gross, net, earnings, taxes and deductions, but only for Rippling Global Payroll customers with the Payroll API entitlement. Source |
| Can you write a deduction? | Legacy 401(k) only | D | The v2 FAQ says deduction endpoints are 'Not at this time'; the legacy V1 Partner API has POST Employee 401k Deduction. Source |
| Can you write a direct deposit account? | Unverified | U | No bank account or payment-method endpoint in the v2 reference. |
| Can you read W-2s? | Unverified | U | No tax-document endpoint in the v2 reference. |
| Can you read hours worked? | Yes — time entries and cards | D | time-entries and time-cards endpoints; time entries can also be created and updated. Source |
| Does it push change events? | App Shop partners only | D | Webhooks (employee.created/updated/terminated, 401_deductions.updated) go only to App Shop partner apps, with about five minutes' lag. Source |
| How does an integration authenticate? | API token or OAuth 2.0 | D | Customer integrations use a bearer API token that inherits the creator's permissions; App Shop partners use OAuth authorisation-code flow. Source |
Deduction write, in detail
For benefits, HSA/FSA and 401(k) integrations. 9 of 10 fields are unverified — no public source states the answer. Compare every system on the deduction write detail page.
| Field | Value | Conf | Note — and what a correct answer needed |
|---|---|---|---|
| Deduction read | Unverified | U | developer.rippling.com serves no content to an unauthenticated fetcher; the docs site states documentation is read with a Rippling account. |
| Deduction write | Legacy 401(k) only | D | Re-checked 2026-09-26. The v2 REST API FAQ says deduction endpoints are "Not at this time". The legacy V1 Partner API documents POST Employee 401k Deduction (traditional and Roth contribution amounts) — the only deduction write Rippling publishes. |
| Pre-tax vs post-tax at write | Unverified | U | No public specification. |
| Amount vs percent | Unverified | U | No public specification. |
| Effective dating | Unverified | U | No public specification. |
| Retro adjustment | Unverified | U | No public specification. |
| Employer contribution | Unverified | U | No public specification. |
| Code taxonomy shape | Unverified | U | No public specification. |
| Auth model | Unverified | U | No public specification. |
| Data freshness | Unverified | U | No public specification. |
D vendor-documented · U unverified · — not offered. See every payroll system side by side in the Payroll API Capability Matrix.