OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes.
Structured read interface for the declared product and resources
List workers ↗
Structured read interface for the declared product and resources · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes.
Documented list/collection retrieval within the stated endpoint scope; whole-product recovery unverified
List workers ↗
Documented list/collection retrieval within the stated endpoint scope; whole-product recovery unverified · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes.
filter on status, work_email, created_at and updated_at
List workers ↗
filter on status, work_email, created_at and updated_at · Checked 2026-10-16
Access cost barrier -
-
Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes.
Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved
Get Started with the Developer API ↗
Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes.
Partner OAuth installation documented; applicable current V2 approval conditions not established
Installation OAuth guide ↗
Partner OAuth installation documented; applicable current V2 approval conditions not established · Checked 2026-10-16
Downstream permission -
-
Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes.
Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established
Get Started with the Developer API ↗
Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 2.5/10
Named operations in a limited domain
Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes.
POST /employee-documents/; worker, folder and uploaded file IDs
Upload and attach files ↗
POST /employee-documents/; worker, folder and uploaded file IDs · Checked 2026-10-16
Custom application path -
-
Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes.
Current chosen-application distribution and approval conditions remain unresolved
Get Started with the Developer API ↗
Current chosen-application distribution and approval conditions remain unresolved · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes.
Workers updated_at filter
List workers ↗
Workers updated_at filter · Checked 2026-10-16
Limit visibility -
-
Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes.
Usage and rate-limit guide reviewed; comparable route-specific throughput not established
API usage and rate limits ↗
Usage and rate-limit guide reviewed; comparable route-specific throughput not established · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes.
Worker updated_at identifies changes; termination is not hard deletion
List workers ↗
Worker updated_at identifies changes; termination is not hard deletion · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes.
Repeat the complete permitted worker collection and follow pagination to rebuild the selected current roster. This does not recover historical intermediate states, deleted worker payloads, employee-document bytes or a durable event checkpoint.
List workers ↗
GET /workers/; paginated worker list, limit/cursor and next_link · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes.
Customer-held structured API records within the declared resource scope
List workers ↗
Customer-held structured API records within the declared resource scope · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes.
Applicable post-cancellation retrieval clause not established by reviewed technical documentation
Get Started with the Developer API ↗
Applicable post-cancellation retrieval clause not established by reviewed technical documentation · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes.
Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified
List workers ↗
Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 7.5/10
Customer-authored native scripts or custom APIs
Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes.
Native functions; POST create and PATCH update with function scopes
Get Started with the Developer API ↗
Native functions; POST create and PATCH update with function scopes · Checked 2026-10-16
Rights to custom logic -
-
Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes.
Ownership and reusable export or independent execution of native workflow artifacts remain unresolved
Get Started with the Developer API ↗
Ownership and reusable export or independent execution of native workflow artifacts remain unresolved · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Token scopes intersect the creator’s permission profile. Workers may expose redacted-field metadata, so an apparently successful response can omit protected fields. App Shop partner OAuth is separate from a customer token; partner approval conditions remain unresolved here.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Workers use cursor pagination with a maximum of 100 and support updated_at filters. File uploads and employee-document attachment are separate workflows; an employee roster cannot stand in for document recovery.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Rippling scoped API access | API key | Customer | Not confirmed | Not confirmed | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
The reviewed API guides do not establish the lowest eligible subscription or fixed access fees. Page limits and token creation describe technical access rather than commercial entitlement.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
The file guide documents POST /employee-documents/ to attach uploaded documents to a worker. Broader employee modification is not inferred from list-worker access.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Workers can be filtered on updated_at. A returned employment termination state is not a deletion tombstone, and complete deletion capture or durable replay has not been established. Repeat the complete permitted worker collection and follow pagination to rebuild the selected current roster. This does not recover historical intermediate states, deleted worker payloads, employee-document bytes or a durable event checkpoint.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates identified; deletion capture not establishedRippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes. Worker updated_at identifies changes; termination is not hard deletion | List workers ↗Worker updated_at identifies changes; termination is not hard deletionChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedRippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes. Repeat the complete permitted worker collection and follow pagination to rebuild the selected current roster. This does not recover historical intermediate states, deleted worker payloads, employee-document bytes or a durable event checkpoint. | List workers ↗GET /workers/; paginated worker list, limit/cursor and next_linkChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Structured worker records can be held outside Rippling before cancellation. Files, compensation subobjects and native app configurations require their own permissions and retrieval; whole-product restoration remains unverified.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Developer APIs list, create and update native functions when their scopes permit. Independent execution and ownership of exported native function or workflow definitions remain unresolved (source access alone does not settle reusable rights).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeRippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes. Structured read interface for the declared product and resources | List workers ↗Structured read interface for the declared product and resourcesChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsRippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes. Documented list/collection retrieval within the stated endpoint scope; whole-product recovery unverified | List workers ↗Documented list/collection retrieval within the stated endpoint scope; whole-product recovery unverifiedChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersRippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes. filter on status, work_email, created_at and updated_at | List workers ↗filter on status, work_email, created_at and updated_atChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes. Partner OAuth installation documented; applicable current V2 approval conditions not established | Installation OAuth guide ↗Partner OAuth installation documented; applicable current V2 approval conditions not establishedChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes. Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved | Get Started with the Developer API ↗Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolvedChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes. Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established | Get Started with the Developer API ↗Reviewed access documentation; applicable downstream processing, AI and redistribution terms not establishedChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainRippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes. POST /employee-documents/; worker, folder and uploaded file IDs | Upload and attach files ↗POST /employee-documents/; worker, folder and uploaded file IDsChecked 2026-10-16 |
| How can customers connect an application they build or choose? | -Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes. Current chosen-application distribution and approval conditions remain unresolved | Get Started with the Developer API ↗Current chosen-application distribution and approval conditions remain unresolvedChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksRippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes. Workers updated_at filter | List workers ↗Workers updated_at filterChecked 2026-10-16 |
| How are integration limits disclosed? | -Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes. Usage and rate-limit guide reviewed; comparable route-specific throughput not established | API usage and rate limits ↗Usage and rate-limit guide reviewed; comparable route-specific throughput not establishedChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsRippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes. Customer-held structured API records within the declared resource scope | List workers ↗Customer-held structured API records within the declared resource scopeChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes. Applicable post-cancellation retrieval clause not established by reviewed technical documentation | Get Started with the Developer API ↗Applicable post-cancellation retrieval clause not established by reviewed technical documentationChecked 2026-10-16 |
| How can customers define their own business logic? | Customer-authored native scripts or custom APIsRippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes. Native functions; POST create and PATCH update with function scopes | Get Started with the Developer API ↗Native functions; POST create and PATCH update with function scopesChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Rippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes. Ownership and reusable export or independent execution of native workflow artifacts remain unresolved | Get Started with the Developer API ↗Ownership and reusable export or independent execution of native workflow artifacts remain unresolvedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedRippling V2 REST / company workers and employee-document attachment; customer API tokens and App Shop partner OAuth are distinct routes. Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified | List workers ↗Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverifiedChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Lowest eligible plan and fixed API access fees
- Applicable downstream-use and customer cancellation terms
- Complete file, history and configuration recovery
- Native workflow artifact ownership and independent execution
- Retained replay, checkpoints and gap-recovery procedure
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.