Skip to content

Unified API

Unified HRIS API

One standardized interface to read and write human resource information system data across every provider. 20 unified resources, 41 supported integrations, zero provider-specific code.

https://api.truto.one/unified/hris
Start integrating API docs
20

Unified resources

41

Supported integrations

Pass‑through

Real-time, no data storage

Data Model

HRIS resources

Every resource is normalized across providers. Use the same schema whether your customer is on AlexisHR or BambooHR.

Bank Info

Bank info represent the Bank Account information for an Employee

7 fields Docs →
Bank Info fields
id string
employee string
account_number string
bank_name string
account_type string
created_at string
updated_at string

Benefits

Benefits represent the benefits for an Employee

13 fields Docs →
Benefits fields
id string
name string
employee object
provider_name string
company_benefit object
employee_contribution string
company_contribution string
currency string
start_date string
end_date string
status string
created_at string
updated_at string

Companies

Companies represent the companies in HRIS

6 fields Docs →
Companies fields
id string
legal_name string
display_name string
enis array
created_at string
updated_at string

Company Benefits

Represents the benefits offered by a company

7 fields Docs →
Company Benefits fields
id string
name string
description string
status string
company object
created_at string
updated_at string

Employee Compensations

Represent the compensation configuration for an Employee

14 fields Docs →
Employee Compensations fields
id string
type string
description string
employee object
amount number
currency string
period string
payment_frequency string
status string
start_date string
end_date string
end_reason string
created_at string
updated_at string

Employee Payroll Runs

Employee Payroll Runs represent the Employee Payroll Runs for an Employee

13 fields Docs →
Employee Payroll Runs fields
id string
employee string
payroll_run string
gross_pay number
net_pay number
start_date string
end_date string
check_date string
earnings array
deductions array
taxes array
created_at string
updated_at string

Employees

Represents an employee in HRIS

32 fields Docs →
Employees fields
id string
employee_number string
company object
first_name string
middle_name string
last_name string
name string
username string
job_title string
groups array
emails array
phones array
employments array
home_location array
work_location object
manager object
pay_group object
ssn string
gender string
ethnicity string
marital_status string
date_of_birth string
start_date string
employment_status string
termination_date string
termination_type string
termination_reason string
avatar string
tags array
created_at string
updated_at string
etag string

Employments

Employments represent a job position at a company.

15 fields Docs →
Employments fields
id string
employee object
job_title string
pay_rate number
pay_period string
pay_frequency string
pay_currency string
pay_group string
flsa_status string
effective_date string
end_date string
employment_type string
end_reason string
created_at string
updated_at string

Fields

Represent the fields for various entities in the company

6 fields Docs →
Fields fields
id string
name string
label string
entity_type string
created_at string
updated_at string

Group Types

Group types represent the types of group.

5 fields Docs →
Group Types fields
id string
name string
description string
created_at string
updated_at string

Groups

Groups represent the groups for an Employee

7 fields Docs →
Groups fields
id string
parent_group string
name string
description string
type string
created_at string
updated_at string

Job Roles

Represent the job roles in a company

5 fields Docs →
Job Roles fields
id string
name string
description string
created_at string
updated_at string

Locations

Locations represent the locations in HRIS

12 fields Docs →
Locations fields
id string
name string
phone_number object
street_1 string
street_2 string
city string
state string
postal_code string
country string
location_type string
created_at string
updated_at string

Pay Groups

Paygroups represent a subset of employees that are put together for payroll processing purposes.

5 fields Docs →
Pay Groups fields
id string
name string
pay_group_name string
created_at string
updated_at string

Payroll Runs

Payrollruns represent a group of pay statements for a specific pay schedule.

8 fields Docs →
Payroll Runs fields
id string
run_state string
run_type string
start_date string
end_date string
check_date string
created_at string
updated_at string

Tags

The tags represent a tag for a employee.

4 fields Docs →
Tags fields
id string
name string
created_at string
updated_at string

Timeoff Balances

Represent the time off balances for an Employee

6 fields Docs →
Timeoff Balances fields
id string
employee object
timeoff_policy string
balance number
created_at string
updated_at string

Timeoff Policies

Represent the time off policies in a company

4 fields Docs →
Timeoff Policies fields
id string
name string
description string
unit string

Timeoff Requests

Represent the time off requests for an Employee

16 fields Docs →
Timeoff Requests fields
id string
description string
reason object
employee object
approver string
status string
employee_note string
units string
amount number
timeoff_type string
request_policy_type string
start_time string
end_time string
session string
created_at string
updated_at string

Timeoff Types

Represent the time off types in a company

6 fields Docs →
Timeoff Types fields
id string
name string
description string
unit string
created_at string
updated_at string

How It Works

From zero to integrated

Go live with the Unified HRIS API in under an hour. No boilerplate, no maintenance burden.

01

Connect your customer’s account

Use Truto’s pre-built auth flows to connect any human resource information system provider. OAuth, API keys, and custom auth — all handled.

02

Query the unified API

Read and write data through a single, normalized REST API. Same endpoints, same schema, regardless of the underlying provider.

03

Customize with JSONata

Need a field the unified model doesn’t cover? Extend the schema with declarative JSONata mappings — no code deploys, no waiting on us.

From the Blog

HRIS integration guides

Deep dives, architecture guides, and practical tutorials for building human resource information system integrations.

Unified HRIS API

Start building with the Unified HRIS API

41 integrations. 20 unified resources. Zero provider-specific code. Ship human resource information system integrations in hours, not months.

Talk to us