Reference · built on requestConnectorHR, scheduling & workforce

Paylocity

Employee demographics, shifts, punch detail, and payroll inputs from Paylocity, with webhooks for hires, changes, and terminations.

Request accessPricing ↗

About

Paylocity is an HR and payroll suite for US employers. Its developer portal documents REST APIs for employee demographics, company codes and cost centers, scheduling, punch detail, punch import, pay entry, and pay details, plus a separate WebLink API for employee records, earnings, deductions, and taxes. Webhooks announce new hires, employee changes, terminations, processed payrolls, and time-off approvals.

Through Fibric, an operator reads shifts and punch detail, reacts to an Employee Change webhook, and proposes a punch import or a pay entry batch. A manager approves. The data is sent once, and a receipt shows what went and why.

This is a reference listing. It documents what Fibric would read from Paylocity and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Employee records through the WebLink API GET /v2/companies/{companyId}/employees and the Employee Demographics API v2
  • Company shifts, employee shifts, and open shifts through the Scheduling API at /apiHub/scheduling/v1/companies/{companyId}/shifts
  • Punch records for a company or one employee through the Punch Detail API v2 operation and data endpoints
  • Cost centers and labor levels through GET /apiHub/time/v1/companies/{companyId}/costCenters
  • Pay statements by employee and date range through the Pay Details API
  • New Hire, Employee Change, Termination, Payroll Processed, and Time Off Approval webhooks, each carrying companyId and employeeId

Proposed actions

  • Target capability: propose a punch import into Time & Labor for an open pay period through the Punch Import API
  • Target capability: propose a new payroll batch through POST /apihub/payroll/v2/companies/{companyId}/payEntryImport
  • Target capability: propose an employee record update through the WebLink Update Employee endpoint
  • Target capability: propose an earning or deduction upsert through the WebLink API

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Match punches to the schedule

    Shifts from the Scheduling API and punches from the Punch Detail API are compared each day. The operator proposes which punch pairs need a manager's correction before the period closes.

    With Punch Match

  • Sign off the period before payroll

    Once punch detail for the period is read, the operator proposes the pay entry batch and lists the exceptions a manager must clear first.

    With Timesheet Signoff

  • Start onboarding from a New Hire webhook

    A New Hire webhook arrives with companyId and employeeId. The operator reads the employee record and proposes the onboarding steps to run in other systems.

    With Onboarding Checklist

  • Spot overlapping time off

    Time Off Approval webhooks announce approvals as they happen. The operator checks them against company shifts and proposes coverage changes for a manager to approve.

    With Leave Conflict

Requirements

  • A Paylocity customer company admin submits the Web Services Access Request form; Paylocity then issues OAuth credentials and a sandbox
  • Credentials authorized for each API the integration calls, such as Punch Import or Scheduling
  • A publicly reachable HTTPS endpoint for webhooks, which Paylocity configures on request for active customers
  • For punch import, an active Time & Labor module with the API File Map set as default and matching cost centers
Authentication
OAuth 2.0 client credentials: post client_id, client_secret, and grant_type=client_credentials to the Paylocity token endpoint for a one-hour bearer token; TLS 1.2 is required and secrets rotate every 365 days.

Limits

  • The Punch Import API accepts at most 500 records per payload and cannot edit punches once submitted
  • Time & Labor accepts imported punches only for open pay periods
  • Employee Change webhooks poll once a minute and send only companyId and employeeId; read the API for the changed fields
  • Employee Demographics API v2 is in early adoption and the Pay Details API is restricted to approved integrations

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Paylocity ↗

Questions and answers

How do I get Paylocity API credentials?
A Paylocity customer company admin submits the Web Services Access Request form. After review, Paylocity provides OAuth client credentials and a sandbox account. Tokens come from the client credentials flow and expire after one hour. Every integration is customer-specific unless the owning organization has been approved for the Integrations Marketplace.
Which webhooks does Paylocity send?
New Hire, Employee Change, Termination, Payroll Processed, and Time Off Approval. Messages are JSON POSTs over HTTPS to a public URL you provide, and Paylocity sets them up on request. They come from 198.245.157.0/24 and 192.40.49.0/24. Undelivered notifications are queued and retried.
Can the Punch Import API edit punches?
No. It submits finalized time data into Time & Labor for open pay periods only. Edits to imported punches are made in the Time & Labor module. Payloads are limited to 500 records, and the client's File Map must match the fields you post.
Ask about Paylocity

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Paylocity through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy