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
Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits.
Structured read interface for the declared product and resources
Get All Employees ↗
Structured read interface for the declared product and resources · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits.
Documented list/collection retrieval within the stated endpoint scope; whole-product recovery unverified
Get All Employees ↗
Documented list/collection retrieval within the stated endpoint scope; whole-product recovery unverified · Checked 2026-10-16
Query expressiveness 7.5/10
Fixed object or report retrieval
Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits.
Get All Employees; page number and page size
Get All Employees ↗
Get All Employees; page number and page size · Checked 2026-10-16
Access cost barrier -
-
Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits.
Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved
Getting Started ↗
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 5.0/10
Separate provider consent or partner agreement required
Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits.
Access review, customer sponsorship and issued credentials
Getting Started ↗
Access review, customer sponsorship and issued credentials · Checked 2026-10-16
Downstream permission -
-
Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits.
Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established
Getting Started ↗
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 7.5/10
Create and update in one business domain
Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits.
Employee create and update through separately documented operations; field and payroll-sensitive constraints remain applicable.
Update Employee ↗
Update Employee operation; company and employee identifiers · Checked 2026-10-16
Create employee ↗
Create employee; POST employee collection with company-specific validation and field permissions · Checked 2026-10-16
Custom application path 5.0/10
Approved third-party applications using fixed interfaces
Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits.
Approved applications use the documented fixed API interfaces
Getting Started ↗
Approved applications use the documented fixed API interfaces · 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
Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits.
Employee change webhooks and synchronization polling
Synchronization and Webhooks ↗
Employee change webhooks and synchronization polling · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits.
Weblink 25 calls/second; 429 and backoff guidance
Weblink API Rate Limits ↗
Weblink 25 calls/second; 429 and backoff guidance · Checked 2026-10-16
CDC and deletion capture -
-
Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits.
Employment termination is not deletion; full deletion identity coverage unverified
Synchronization and Webhooks ↗
Employment termination is not deletion; full deletion identity coverage unverified · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits.
Error-dependent webhook retries; triage queue is not a consumer checkpoint
Synchronization and Webhooks ↗
Error-dependent webhook retries; triage queue is not a consumer checkpoint · 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
Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits.
Customer-held structured API records within the declared resource scope
Get All Employees ↗
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.
Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits.
Applicable post-cancellation retrieval clause not established by reviewed technical documentation
Getting Started ↗
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
Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits.
Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified
Get All Employees ↗
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 2.5/10
External integration code; native business logic portability not established
Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits.
Customer integration code can run outside the provider; native workflow authoring not established
Getting Started ↗
Customer integration code can run outside the provider; native workflow authoring not established · Checked 2026-10-16
Rights to custom logic -
-
Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits.
Ownership and reusable export or independent execution of native workflow artifacts remain unresolved
Getting Started ↗
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
Demo access requires an existing customer or a sponsoring early-adopter customer. Paylocity reviews access and issues OAuth credentials; technology partnership adds its own agreement and commercial requirements.
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
Get All Employees returns company-scoped payroll/HR records using zero-based page numbers and a default page size of 25. Employee, earning and deduction routes are separate; their presence does not establish full payroll document export.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Paylocity scoped API access | OAuth client credentials | Integration provider | Yes | Partner approval | 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
Route-specific fees and the minimum customer package remain unresolved. Partnership requirements mention commercial terms without establishing the price of the customer integration.
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
Employee creation and updates are documented through distinct POST and update endpoints. Current field permissions and validation still apply; payroll execution and employment termination require separate operation-specific authority.
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
Paylocity documents polling and employee change webhooks, with error-dependent retries and a triage queue. Termination events describe employment state, not proof of record deletion or retained replay.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | -Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits. Employment termination is not deletion; full deletion identity coverage unverified | Synchronization and Webhooks ↗Employment termination is not deletion; full deletion identity coverage unverifiedChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointPaylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits. Error-dependent webhook retries; triage queue is not a consumer checkpoint | Synchronization and Webhooks ↗Error-dependent webhook retries; triage queue is not a consumer checkpointChecked 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
Paginated employee records support an external copy before cancellation. Attachments, complete payroll history and native rules require separate evidence; no customer cancellation retrieval window was established.
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
Approved applications can implement external integration logic. Native workflow artifact rights and independent execution remain unresolved (a bidirectional mapping does not convey ownership).
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 scopePaylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits. Structured read interface for the declared product and resources | Get All Employees ↗Structured read interface for the declared product and resourcesChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsPaylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits. Documented list/collection retrieval within the stated endpoint scope; whole-product recovery unverified | Get All Employees ↗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? | Fixed object or report retrievalPaylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits. Get All Employees; page number and page size | Get All Employees ↗Get All Employees; page number and page sizeChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Separate provider consent or partner agreement requiredPaylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits. Access review, customer sponsorship and issued credentials | Getting Started ↗Access review, customer sponsorship and issued credentialsChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits. Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved | Getting Started ↗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? | -Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits. Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established | Getting Started ↗Reviewed access documentation; applicable downstream processing, AI and redistribution terms not establishedChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainPaylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits. Employee create and update through separately documented operations; field and payroll-sensitive constraints remain applicable. | Update Employee ↗Update Employee operation; company and employee identifiersChecked 2026-10-16 Create employee ↗Create employee; POST employee collection with company-specific validation and field permissionsChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Approved third-party applications using fixed interfacesPaylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits. Approved applications use the documented fixed API interfaces | Getting Started ↗Approved applications use the documented fixed API interfacesChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksPaylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits. Employee change webhooks and synchronization polling | Synchronization and Webhooks ↗Employee change webhooks and synchronization pollingChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsPaylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits. Weblink 25 calls/second; 429 and backoff guidance | Weblink API Rate Limits ↗Weblink 25 calls/second; 429 and backoff guidanceChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsPaylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits. Customer-held structured API records within the declared resource scope | Get All Employees ↗Customer-held structured API records within the declared resource scopeChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits. Applicable post-cancellation retrieval clause not established by reviewed technical documentation | Getting Started ↗Applicable post-cancellation retrieval clause not established by reviewed technical documentationChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedPaylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits. Customer integration code can run outside the provider; native workflow authoring not established | Getting Started ↗Customer integration code can run outside the provider; native workflow authoring not establishedChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Paylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits. Ownership and reusable export or independent execution of native workflow artifacts remain unresolved | Getting Started ↗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 unverifiedPaylocity Payroll/HR Weblink v2 employee API through approved customer or partner integration credentials; other API families have distinct limits. Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified | Get All Employees ↗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
- Complete declared update and deletion identity coverage
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.