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
Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate.
Company worker lists and per-worker retrieval return authorized Flex records. VMT selection changes included PII and detail; it is not a complete account extract.
Paychex worker collection guide ↗
Company workers; JSON; offset/limit; next links; VMT fields · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate.
Traverse company workers with offset/limit and response next links, without incompatible filters. Preserve VMT selection and authorized company IDs.
Paychex worker collection guide ↗
Company workers; JSON; offset/limit; next links; VMT fields · Checked 2026-10-16
Paychex public OpenAPI operation specification ↗
GET /companies/{companyId}/workers; creation-date filters versus offset/limit; PATCH /workers/{workerId} · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate.
Worker collection filters include creation-date ranges and worker attributes. Paging and filtering cannot be combined; a creation-date range is not an update watermark.
Paychex worker collection guide ↗
Company workers; JSON; offset/limit; next links; VMT fields · Checked 2026-10-16
Access cost barrier -
-
Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate.
Lowest-paid-plan entitlement and complete fixed API or partner access fees are unresolved.
Paychex OAuth application authentication ↗
Client ID/secret; /auth/oauth/v2/token; client_credentials; bearer scope · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 5.0/10
Separate provider consent or partner agreement required
Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate.
Paychex evaluates partner requests, reviews the integration and approves production permissions; each client separately approves access in Flex. Customer-built apps do not establish an unrestricted external-partner route.
Paychex partner approval process ↗
Partner evaluation; sandbox demonstration; final approval; production app permissions · Checked 2026-10-16
Paychex customer integration approval ↗
Request Client Access; company display ID; Paychex Flex approval and third-party terms · Checked 2026-10-16
Paychex customer-built application route ↗
Super Admin/Security Admin; own integrated solution; production app · Checked 2026-10-16
Downstream permission -
-
Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate.
The operation guides do not establish applicable downstream processing, AI-use or redistribution rights.
Paychex OAuth application authentication ↗
Client ID/secret; /auth/oauth/v2/token; client_credentials; bearer scope · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate.
POST company workers creates an IN_PROGRESS employee/contractor requiring completion in Flex; PATCH /workers/{workerId} changes permitted worker fields. These operations do not execute payroll.
Paychex create in-progress worker ↗
POST company workers; IN_PROGRESS; finish worker in Flex; invalid IDs on locked resources · Checked 2026-10-16
Paychex public OpenAPI operation specification ↗
GET /companies/{companyId}/workers; creation-date filters versus offset/limit; PATCH /workers/{workerId} · Checked 2026-10-16
Custom application path 5.0/10
Approved third-party applications using fixed interfaces
Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate.
Provider approval precedes customer authorization for this partner route.
Paychex partner approval process ↗
Partner evaluation; sandbox demonstration; final approval; production app permissions · Checked 2026-10-16
Paychex customer integration approval ↗
Request Client Access; company display ID; Paychex Flex approval and third-party terms · Checked 2026-10-16
Paychex customer-built application route ↗
Super Admin/Security Admin; own integrated solution; production app · 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
Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate.
Use worker-domain webhook hints plus full worker reconciliation. The listed from/to filter selects creation dates and cannot replace update capture.
Paychex worker webhook notifications ↗
WRKR_DEM/WRKR_CMP/WRKR_EMPL/WRKR_ADD notifications; fetch current state; 5-minute retries; possible queue disable · Checked 2026-10-16
Paychex public OpenAPI operation specification ↗
GET /companies/{companyId}/workers; creation-date filters versus offset/limit; PATCH /workers/{workerId} · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate.
Current published partner-key allowance is 10,000 requests/minute with a 2,000/second burst shared across its apps. Use live headers and Retry-After on 429; refill is continuous.
Paychex rate limits and throttle recovery ↗
Current per-partner 10,000/minute; burst 2,000/second; shared partner key; continuous refill; Retry-After · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate.
Worker-domain notifications identify changed workers; an exhaustive hard-deletion identity contract is not established by the enumerated triggers.
Paychex worker webhook notifications ↗
WRKR_DEM/WRKR_CMP/WRKR_EMPL/WRKR_ADD notifications; fetch current state; 5-minute retries; possible queue disable · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate.
Failed notifications retry every 5 minutes until success, but Paychex can disable an unsuccessful queue. No retained replay API is proved; re-list workers to rebuild current permitted records.
Paychex worker webhook notifications ↗
WRKR_DEM/WRKR_CMP/WRKR_EMPL/WRKR_ADD notifications; fetch current state; 5-minute retries; possible queue disable · Checked 2026-10-16
Paychex worker collection guide ↗
Company workers; JSON; offset/limit; next links; VMT fields · 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
Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate.
Permitted structured API records can form a customer-held copy.
Paychex worker collection guide ↗
Company workers; JSON; offset/limit; next links; VMT fields · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate.
Live retrieval does not establish contractual access after cancellation.
Paychex worker collection guide ↗
Company workers; JSON; offset/limit; next links; VMT fields · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate.
The declared current record collection is portable; full history, files, configuration and whole-product reconstruction are unverified.
Paychex worker collection guide ↗
Company workers; JSON; offset/limit; next links; VMT fields · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate.
The documented route supports external integration code; native workflow authoring and portability are unverified (API clients are separate artifacts).
Paychex OAuth application authentication ↗
Client ID/secret; /auth/oauth/v2/token; client_credentials; bearer scope · Checked 2026-10-16
Rights to custom logic -
-
Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate.
Rights to reusable native workflow definitions and independent execution are unresolved.
Paychex OAuth application authentication ↗
Client ID/secret; /auth/oauth/v2/token; client_credentials; bearer scope · 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
Paychex evaluates partner requests, reviews the integration and approves production permissions; each client separately approves access in Flex. Customer-built apps do not establish an unrestricted external-partner route.
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
Company worker lists and per-worker retrieval return authorized Flex records. VMT selection changes included PII and detail; it is not a complete account extract. Traverse company workers with offset/limit and response next links, without incompatible filters. Preserve VMT selection and authorized company IDs. Worker collection filters include creation-date ranges and worker attributes. Paging and filtering cannot be combined; a creation-date range is not an update watermark.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Approved Paychex partner production application | OAuth client credentials | Integration provider | Yes | partner agreement | 2026-10-16 |
| Customer-built Paychex company application | OAuth client credentials | Customer | No | customer authorization | 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
Lowest-paid-plan entitlement and complete fixed API or partner access fees are unresolved.
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
POST company workers creates an IN_PROGRESS employee/contractor requiring completion in Flex; PATCH /workers/{workerId} changes permitted worker fields. These operations do not execute payroll.
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
Use worker-domain webhook hints plus full worker reconciliation. The listed from/to filter selects creation dates and cannot replace update capture. Worker-domain notifications identify changed workers; an exhaustive hard-deletion identity contract is not established by the enumerated triggers. Failed notifications retry every 5 minutes until success, but Paychex can disable an unsuccessful queue. No retained replay API is proved; re-list workers to rebuild current permitted records. Current published partner-key allowance is 10,000 requests/minute with a 2,000/second burst shared across its apps. Use live headers and Retry-After on 429; refill is continuous.
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 establishedPaychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate. Worker-domain notifications identify changed workers; an exhaustive hard-deletion identity contract is not established by the enumerated triggers. | Paychex worker webhook notifications ↗WRKR_DEM/WRKR_CMP/WRKR_EMPL/WRKR_ADD notifications; fetch current state; 5-minute retries; possible queue disableChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointPaychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate. Failed notifications retry every 5 minutes until success, but Paychex can disable an unsuccessful queue. No retained replay API is proved; re-list workers to rebuild current permitted records. | Paychex worker webhook notifications ↗WRKR_DEM/WRKR_CMP/WRKR_EMPL/WRKR_ADD notifications; fetch current state; 5-minute retries; possible queue disableChecked 2026-10-16 Paychex worker collection guide ↗Company workers; JSON; offset/limit; next links; VMT fieldsChecked 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
The declared current record collection is portable; full history, files, configuration and whole-product reconstruction are unverified. Live retrieval does not establish contractual access after cancellation.
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
The documented route supports external integration code; native workflow authoring and portability are unverified (API clients are separate artifacts). Rights to reusable native workflow definitions and independent execution are unresolved.
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 scopePaychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate. Company worker lists and per-worker retrieval return authorized Flex records. VMT selection changes included PII and detail; it is not a complete account extract. | Paychex worker collection guide ↗Company workers; JSON; offset/limit; next links; VMT fieldsChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsPaychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate. Traverse company workers with offset/limit and response next links, without incompatible filters. Preserve VMT selection and authorized company IDs. | Paychex worker collection guide ↗Company workers; JSON; offset/limit; next links; VMT fieldsChecked 2026-10-16 Paychex public OpenAPI operation specification ↗GET /companies/{companyId}/workers; creation-date filters versus offset/limit; PATCH /workers/{workerId}Checked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersPaychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate. Worker collection filters include creation-date ranges and worker attributes. Paging and filtering cannot be combined; a creation-date range is not an update watermark. | Paychex worker collection guide ↗Company workers; JSON; offset/limit; next links; VMT fieldsChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Separate provider consent or partner agreement requiredPaychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate. Paychex evaluates partner requests, reviews the integration and approves production permissions; each client separately approves access in Flex. Customer-built apps do not establish an unrestricted external-partner route. | Paychex partner approval process ↗Partner evaluation; sandbox demonstration; final approval; production app permissionsChecked 2026-10-16 Paychex customer integration approval ↗Request Client Access; company display ID; Paychex Flex approval and third-party termsChecked 2026-10-16 Paychex customer-built application route ↗Super Admin/Security Admin; own integrated solution; production appChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate. Lowest-paid-plan entitlement and complete fixed API or partner access fees are unresolved. | Paychex OAuth application authentication ↗Client ID/secret; /auth/oauth/v2/token; client_credentials; bearer scopeChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate. The operation guides do not establish applicable downstream processing, AI-use or redistribution rights. | Paychex OAuth application authentication ↗Client ID/secret; /auth/oauth/v2/token; client_credentials; bearer scopeChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainPaychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate. POST company workers creates an IN_PROGRESS employee/contractor requiring completion in Flex; PATCH /workers/{workerId} changes permitted worker fields. These operations do not execute payroll. | Paychex create in-progress worker ↗POST company workers; IN_PROGRESS; finish worker in Flex; invalid IDs on locked resourcesChecked 2026-10-16 Paychex public OpenAPI operation specification ↗GET /companies/{companyId}/workers; creation-date filters versus offset/limit; PATCH /workers/{workerId}Checked 2026-10-16 |
| How can customers connect an application they build or choose? | Approved third-party applications using fixed interfacesPaychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate. Provider approval precedes customer authorization for this partner route. | Paychex partner approval process ↗Partner evaluation; sandbox demonstration; final approval; production app permissionsChecked 2026-10-16 Paychex customer integration approval ↗Request Client Access; company display ID; Paychex Flex approval and third-party termsChecked 2026-10-16 Paychex customer-built application route ↗Super Admin/Security Admin; own integrated solution; production appChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksPaychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate. Use worker-domain webhook hints plus full worker reconciliation. The listed from/to filter selects creation dates and cannot replace update capture. | Paychex worker webhook notifications ↗WRKR_DEM/WRKR_CMP/WRKR_EMPL/WRKR_ADD notifications; fetch current state; 5-minute retries; possible queue disableChecked 2026-10-16 Paychex public OpenAPI operation specification ↗GET /companies/{companyId}/workers; creation-date filters versus offset/limit; PATCH /workers/{workerId}Checked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsPaychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate. Current published partner-key allowance is 10,000 requests/minute with a 2,000/second burst shared across its apps. Use live headers and Retry-After on 429; refill is continuous. | Paychex rate limits and throttle recovery ↗Current per-partner 10,000/minute; burst 2,000/second; shared partner key; continuous refill; Retry-AfterChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsPaychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate. Permitted structured API records can form a customer-held copy. | Paychex worker collection guide ↗Company workers; JSON; offset/limit; next links; VMT fieldsChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate. Live retrieval does not establish contractual access after cancellation. | Paychex worker collection guide ↗Company workers; JSON; offset/limit; next links; VMT fieldsChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedPaychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate. The documented route supports external integration code; native workflow authoring and portability are unverified (API clients are separate artifacts). | Paychex OAuth application authentication ↗Client ID/secret; /auth/oauth/v2/token; client_credentials; bearer scopeChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Paychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate. Rights to reusable native workflow definitions and independent execution are unresolved. | Paychex OAuth application authentication ↗Client ID/secret; /auth/oauth/v2/token; client_credentials; bearer scopeChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedPaychex Flex / authorized-company worker collection, worker updates and creation of in-progress workers through an approved partner application. Customer-built company apps, completed hiring, payroll execution and complete HR history are separate. The declared current record collection is portable; full history, files, configuration and whole-product reconstruction are unverified. | Paychex worker collection guide ↗Company workers; JSON; offset/limit; next links; VMT fieldsChecked 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
- Complete lowest-plan entitlement and fixed API fees
- Applicable downstream processing, AI-use and redistribution rights
- Contractual post-cancellation retrieval terms
- Native workflow artifact ownership, reusable export and independent execution
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.