Integrate with what already runs at home
Employees, payroll and time tracking exposed over an API, with a key per integration — so the ERP, the BI tool or an internal system reads straight from the source.
Why use it
The problems Avos solves in everyday HR.
Manual exports are not integration
A spreadsheet exported every week breaks on the first holiday and nobody notices.
The other system queries the API and always reads current data, with nobody in the middle.
One password for everything
An integration running on a person's account dies when that person leaves.
Every integration gets its own key, revocable without touching the others.
Time tracking that lives elsewhere
Companies with their own clocking hardware would have to type punches twice.
Punches come in through the API and land in the same records that produce timesheets and legal exports.
How it works
Create the key
One per integration, scoped to what it may read and write.
Consume the endpoints
Employees, pay periods and payrolls, and time punches.
Revoke whenever
The key goes away on its own, without taking the others down.
Frequently asked questions
What does the API expose today?
Employees (list, read, create and update), pay periods and payrolls, and time punches — plus lookup lists such as departments and positions.
How does authentication work?
Through API keys, created per integration and revocable at any time, without depending on a person's account.