Online Attendance GIRITON offers REST API for integration with other systems.

You can conveniently download data from GIRITON to other systems. Such as hours worked, human resources or a list of vacations. You can also upload data from other systems to GIRITON. Such as time spent on individual projects or new users in human resources.

How to generate REST Api token

To communicate with Giriton’s REST api, it is necessary to generate a so-called “REST API token” which serves as a password during communication. You can generate a new REST API token in Giriton web application in  Paired devices agenda by clicking the + REST API token button. Name it appropriately after the addition of a new token. For example, “Integration with the warehouse system”. You can display it in the format yourcompany.xxxx-xxxx-xxxx-xxxx by clicking the eye icon in the “REST API Token”.

Attention! Treat this token as carefully as the password. Using the REST Api token, it is possible to read data or write data to your company’s account. Personal data may be leaked if your token falls into the wrong hands.

We recommend checking or adjusting permissions for each api token in 3 Permissions card. You can set for each token what can be done in the system when using it. For example, you can generate a single token that you only want to use to check the list of people in the workplace. You only grant permission to view attendance to such a token. The second token will be used to add people to Giriton so you will grant View Human Resources and Edit Human Resources permissions to it. If you use a token to try to make a REST Api call to which the given token doesn’t have permission, the call will fail.

How to communicate via REST Api

More information about REST api, including documentation, can be found at

REST Api limits

There are limits on the number of calls made on the REST API. You can do:
  • Max 600 calls per 1 minute
  • Max 700 calls in 10 minutes
  • Max 800 calls per 60 minutes
This means that when your application makes more than 600 calls within a single minute, the REST API will start returning HTTP error 429 Too Many Requests. Your application then has to wait another minute before it can make another 100 calls, exhausting the ten-minute limit. It then has to wait another 10 minutes and can make another 100 calls, thus exhausting the hourly limit and having to wait another hour before being able to make another API call.