Payroll systems · Paycor
Paycor
Paycor's own documentation covers employees, pay statements, deduction write, bank account write, tax forms, hours and webhooks through the API. Access: Client admin or partner.
Integration method grade ? · field-level docs NOT publicly readable · last verified 2026-09-26 · Paycor Developers Portal (renders no content unauthenticated)
What the API lets you do
| Question | Answer | Conf | What the documentation says |
|---|---|---|---|
| How do you get API access? | Client admin or partner | D | 'Only a Paycor Perform HR/Payroll/Company admin can create a Developer Portal account'; prospective partners go through the partner portal. Sandbox and production environments are provided. Source |
| Can you read employees and pay rates? | Yes — REST read and write | D | Get employees by tenant or legal entity, get employee and pay rates by employee ID, add or update pay rates, and create employees. Source |
| Can you read pay statements? | Yes — paystubs | D | Get paystubs by employee ID (with check number and planner ID), paystub document links, and payroll processing data by legal entity. Source |
| Can you write a deduction? | Yes — add / update | D | Add Employee Deduction and PUT Employee Deduction by employee ID, with a CalculateUntil date; hours and earnings can also be posted to the paygrid. Source |
| Can you write a direct deposit account? | Yes — add / update | D | Add Employee Direct Deposits and PUT Employee Direct Deposit, including HSA variants; unmasked account numbers need a separate data-access setting. Source |
| Can you read W-2s? | Yes — tax document links | D | Get Employee Tax Document Link by employee ID returns a downloadable tax document; a 'Tax W2C Document Created' event exists. W-2 retrieval is not named explicitly. Source |
| Can you read hours worked? | Yes — hours and punches | D | Time card hours by employee or legal entity, timecard punches, employee hours, and posting hours or punches into Perform Time. Source |
| Does it push change events? | Yes — event subscriptions | D | Per-app event subscriptions including Employee.Created, Employee.Modified, Person.Modified and Payroll.Distributed. Source |
| How does an integration authenticate? | OAuth 2.0 + subscription key | D | OAuth 2.0 with client admin authorisation yields access and refresh tokens per legal entity; every request also needs an Ocp-Apim-Subscription-Key header. Source |
Deduction write, in detail
For benefits, HSA/FSA and 401(k) integrations. 8 of 10 fields are unverified — no public source states the answer. Compare every system on the deduction write detail page.
| Field | Value | Conf | Note — and what a correct answer needed |
|---|---|---|---|
| Deduction read | Claimed — API | P | A deductions resource at v1/employees/{id}/deductions/{id} is described by third-party integration vendors, not read by us in Paycor’s own reference. Marked practitioner-reported rather than vendor-documented because the source is a competitor’s directory page. |
| Deduction write | API — add / update | D | Re-checked 2026-09-26 from the portal’s own bundled documentation text. Add Employee Deduction and PUT Employee Deduction by employee ID, with a CalculateUntil date. Field-level shape not otherwise assessed. |
| Pre-tax vs post-tax at write | Unverified | U | No field-level detail assessed. |
| Amount vs percent | Unverified | U | No field-level detail assessed. |
| Effective dating | Unverified | U | No field-level detail assessed. |
| Retro adjustment | Unverified | U | No field-level detail assessed. |
| Employer contribution | Unverified | U | No field-level detail assessed. |
| Code taxonomy shape | Unverified | U | No field-level detail assessed. |
| Auth model | Unverified | U | Not assessed. |
| Data freshness | Unverified | U | Not assessed. |
D vendor-documented · U unverified · — not offered. See every payroll system side by side in the Payroll API Capability Matrix.