Skip to main content
Use the @bijection/connectors/paylocity entrypoint to declare Paylocity resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Employees

roster: Employee status roster

The following example matches configuration standard.

Configuration: standard

Case: paylocity/employees/roster/standard. Connection and resource configuration are declared by this exact case. Credential kind: paylocity. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: employees
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. employees.roster walks GET /api/v2/companies/{companyId}/employees?pagesize=100&pagenumber=n whole each pass and publishes each employee’s employeeId, statusCode and statusTypeCode (the list’s whole answer). OAuth client credentials (scope=WebLinkAPI) issue a Bearer token. WebLink webhooks carry no delivery identity and no signature, so no listener is declared. Built from the provider’s published API documentation; nothing here has run against Paylocity or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.