As of August 25, 2023 the Hourly Absences endpoint i.e. /company/absence-periods, has had an update to the pagination logic of responses, to match the existing API documentation i.e. the 'offset' variable has been updated to refer to a page-level offset rather a per-record-level offset, as was previously the case.

Starting November 16, 2023, in order to improve the performance of the GET Employees endpoint and ensure system stability, we are introducing pagination as a mandatory feature when the updated_since filter is used to retrieve the data.

Pagination can be used in the GetReport Endpoint via page and limit query parameters. The limit indicates how many employees per page should be returned. Example: /company/custom-reports/reports/{report_id}?page=2&limit=100

Provision of report status via API

Changed the nature of bearer token from one-time use to stable tokens

Changed 'end_time' in POST and PATCH endpoints to be optional

We are adding a new field legacy_categoryfor the response of the GET endpoint.

Until now, the documentation stated that the only way to submit client_id and client_secret is through the query parameters.

A new endpoint that allows customers to delete hourly absence periods has been added

Three new fields are added to the hourly absence GET/POST response as follows: