Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.

TriNet

This documentation for the TriNet integration describes the technical capabilities of this integration, including authorization, scopes/permissions, and utilized endpoints. For more information on how to integrate TriNet, visit our connection instructions.

Version​

This integration utilizes the Merge HR, Payroll, and Directory (HRIS) API v1.

Base URL​

The base URL used for all TriNet API endpoints:
https://api.merge.dev/api/hris/v1

Endpoints Utilized​

DataGrail uses the following endpoints to authorize and test the connection:


Authentication & Authorization​

The DataGrail TriNet integration connects using Merge API authentication which requires an API Key.

Sensitive Credentials
Publicly exposing your API credentials can allow unauthorized access to TriNet API endpoints by a third party. DataGrail stores your API credentials encrypted and protected.

Limits​

Limits in TriNet are calculated using the leaky bucket algorithm. All requests that are made after rate limits have been exceeded are throttled and an HTTP 429 Too Many Requests error is returned. Requests succeed again after enough requests have emptied out of the bucket.

  • DataGrail supports requests throttling to stay within 70-80% of specified service rate limits.
  • DataGrail processes API responses with HTTP 429 status to interrupt requests, waiting and retrying (using an exponential backoff strategy).

Capabilities​

Access​

DataGrail's TriNet integration provides Asynchronous Access capabilities for the following supported identifier category: Email.

Data Interactions​

For Access requests, DataGrail will take the following actions:

  1. Search employees by configured identifiers.

Endpoints Utilized​


Data Discovery​

DataGrail's TriNet integration provides data discovery capabilities based on the principle of finding any and all personal data that's stored in a data system.

Data Interactions​

For discovery requests, DataGrail will take the following actions:

  1. Fetch available (enabled) objects from the following Merge! models:
Supported Objects
  • employees,
  • dependents,
  • bank_info,
  • employments,
  • employee_payroll_runs,
  • benefits,
  • time_off,
  • time_off_balances,
  • timesheet_entries,
  • locations,
  1. Sample data for the next analysis and classification.

Endpoints Utilized​

MethodEndpointPurposeDocs
GET/bank-infoFetch BankInfo objects
GET/benefitsFetch benefits
GET/dependentsFetch dependents
GET/employee-payroll-runsFetch EmployeePayrollRun objects
GET/employeesFetch employees
GET/employmentsFetch employments
GET/locationsFetch locations
GET/time-offFetch TimeOff objects.
GET/time-off-balancesFetch TimeOffBalance objects.
GET/timesheet-entriesFetch TimesheetEntry objects.

 

Need help?
If you have any questions, please reach out to your dedicated Account Manager or contact us at support@datagrail.io.

Disclaimer: The information contained in this message does not constitute as legal advice. We would advise seeking professional counsel before acting on or interpreting any material.