Summary and recommendation
TriNet does not publicly expose a documented REST or SCIM 2.0 user-management API as of this research date.
The Okta OIN listing for TriNet confirms SAML-based SSO support via Okta and OneLogin, but does not indicate SCIM provisioning capability.
No OAuth 2.0, API key, or webhook documentation was found in official TriNet or developer portal sources - do not assume standard REST API patterns apply.
Employee and user data is managed exclusively through TriNet's proprietary HR platform (TriNet HR+).
Any integration requiring automated employee lifecycle management would require direct engagement with TriNet's enterprise or partner team, with no guarantee of API availability.
API quick reference
| Has user API | No |
| SCIM available | No |
| SCIM plan required | Enterprise |
Authentication
Auth method: Not documented
User object / data model
User object field mapping is not yet verified for this app.
Core endpoints
Endpoint coverage is not yet verified for this app.
Rate limits, pagination, and events
Rate limits: Not documented
Rate-limit headers: No
Retry-After header: No
Rate-limit notes: Not documented
Pagination method: none
Default page size: 0
Max page size: 0
Pagination pointer: Not documented
Webhooks available: No
Webhook notes: No publicly documented webhook system for user-management events found in official TriNet documentation.
Alternative event strategy: TriNet does not publicly document a webhook or event-streaming API for user lifecycle events. Customers may need to rely on manual HR workflows or TriNet's internal platform notifications.
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: Enterprise
- Endpoint: Not documented
Limitations:
- No publicly documented SCIM 2.0 endpoint found in official TriNet or Okta OIN documentation.
- Okta OIN listing for TriNet does not indicate SCIM provisioning support.
- TriNet's context data indicates SCIM is not natively available; SSO (SAML) is supported via Okta and OneLogin but automated provisioning/deprovisioning via SCIM is not confirmed.
- Enterprise plan may be required if SCIM becomes available, but this is unconfirmed by current official sources.
Common scenarios
Given the absence of a public API, the only confirmed programmatic surface is SAML SSO.
This means identity graph completeness for TriNet-managed employees depends entirely on manual exports or HR platform reports
there is no event-driven or polling-based mechanism to detect new hires, role changes, or terminations in real time.
For teams building identity graph coverage across their SaaS stack, TriNet represents a data gap: employee records exist in the platform but cannot be queried, subscribed to, or synced without manual intervention or a custom enterprise agreement.
Scenarios requiring lifecycle automation (joiners, movers, leavers) have no documented API path today.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The core trap with TriNet's integration surface is conflating SSO availability with provisioning capability. SAML login works - but SAML does not carry group membership, role changes, or termination signals back to your identity provider automatically.
Without SCIM, your identity graph will drift from TriNet's source-of-truth employee records every time a hire, role change, or termination is processed.
Because TriNet is a co-employer, employee records also carry compliance retention requirements - terminated records are never deleted, only deactivated. Any sync logic built on record presence rather than status fields will misread inactive employees as active. There are no rate limit headers, no retry-after signals, and no webhook events to design around;
the API surface is effectively zero until TriNet publishes otherwise.
Automate TriNet workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
