End-user applications: The user is required to log in to TriNet to obtain access to the required resources. When a user runs an API call, it is using the individual's own credentials. Learn more about end-user applications.

Business-to-business (B2B) applications: These are typically system integrations. All processes occur in the background and system login is not always possible. Different security measures need to be taken. Learn more about B2B applications.

TriNet API calls access sensitive employee and company data. Before the application can call them, the following must be accomplished with OAuth 2.0 and the corresponding libraries:

Your application must be authenticated.

The user with access to that data must grant your application access.

The user must be authenticated to grant that access.

Refresh and access tokens: When a user grants your application access, the authorization server provides the application with refresh and access tokens. Your application uses access tokens to authorize API calls. Access tokens expire but refresh tokens do not. Your application can use a refresh token to acquire a new access token.

Keep your application's refresh and access tokens secure as they can be used to access sensitive data.

Client ID and client secret: These uniquely identify your company's application and are used to acquire tokens. List of scopes is also assigned to determine access level. Please visit Oauth Scopes page for more info.

500-599 Server Error Status Codes

The statusText and statusMessage provide additional information about the status of the request. This can be useful when a request returns a 4xx error, when those fields provide additional information about the error that can be used in debugging the issue.

Most records contain an effective date that indicates when that information or action becomes effective. A record may also have an effective end date. The record that is currently effective is available for transactions. Other records are stored as history or will take effect on a future date.

An employee can have multiple changes for the same effective date, for example, if there are two job changes that take effect on the same date.