Payroll systems · TriNet
TriNet
TriNet's own documentation covers employees through the API. Access: Approval + customer authorisation.
Integration method grade ? · field-level docs NOT publicly readable · last verified 2026-09-26 · TriNet PEO Developer Portal
What the API lets you do
| Question | Answer | Conf | What the documentation says |
|---|---|---|---|
| How do you get API access? | Approval + customer authorisation | D | Request form, TriNet-approved developer account, API Discovery call, then customer authorisation before production keys; 'Full API specifications will be available once an account is created.' Source |
| Can you read employees and pay rates? | Yes — list employees | D | GET /v1/company/{companyId}/employees with employmentInfo (job title, hire and termination dates) and payInfo (rate and frequency) scopes. Source |
| Can you read pay statements? | Unverified — spec behind login | U | 'Payroll' and 'Money' categories are listed, but endpoint specifications require sign-in. |
| Can you write a deduction? | Unverified | U | A generic write scope exists, but which endpoints accept deductions is not public; whether the PEO or the client controls deductions is not stated. |
| Can you write a direct deposit account? | Unverified | U | A direct-deposit payment method code is listed, but no public bank-write endpoint. |
| Can you read W-2s? | Unverified | U | No public W-2 or tax-document endpoint information. |
| Can you read hours worked? | Unverified — time off only listed | U | A time-off category is listed; no public worked-hours endpoint. |
| Does it push change events? | Unverified | U | No webhook or event documentation on the public portal. |
| How does an integration authenticate? | OAuth 2.0 client credentials | D | client_credentials with Basic auth returns a bearer token; no refresh; read and write plus section scopes. 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 | Unverified | U | 'Elections' are mentioned under Money, but the endpoint specification is login-gated. |
| Deduction write | Unverified | U | No public field-level reference located; PEO versus client control of deductions is not stated. |
| Pre-tax vs post-tax at write | Unverified | U | No public field-level reference located. |
| Amount vs percent | Unverified | U | No public field-level reference located. |
| Effective dating | Effective-dated (general) | D | 'Most records contain an effective date… may also have an effective end date' — a general statement, not specific to deductions. |
| Retro adjustment | Unverified | U | No public statement on retro adjustment. |
| Employer contribution | Unverified | U | No public field-level reference located. |
| Code taxonomy shape | Unverified | U | TriNet-standard earnings and payment codes are published, but no deduction code list. |
| Auth model | OAuth 2.0 client credentials | D | Client ID and secret provisioned by TriNet; access limited by scope, endpoint list, company and quota. |
| Data freshness | Unverified | U | No public statement on latency or change events. |
D vendor-documented · U unverified · — not offered. See every payroll system side by side in the Payroll API Capability Matrix.