Added pagination to the GET employees endpoint to make fetching larger sets of employee data easier. This is not a breaking change – all requests that don't contain the offset and limit parameter will still pull all of employees.
- We just added the attribute "status", which indicates the status of an Attendance Period (“approved”, “pending”).
- You're now also able to get the results using the parameters "includePending”, which returns Attendance Periods with both “pending” and “approved” status. Find more information in the API reference.
Synchronising attendance periods with Personio just became a whole lot easier!
Absence periods created via the
POST /company/time-offs endpoint used to skip the approval process by default, so there was no way to create absence requests using the public API.
The breaking changes described in the previous post have now been fixed:
We just introduced pagination to the GET Absence API which unfortunately introduced a breaking change (this was not on purpose). Currently, the absence response is limited to 200 entries by default in case no pagination parameters are put in, which might break your implementation given we didn't previously limit the response.
Synchronising absences with Personio just became a whole lot easier!
Two small improvements to the API reference:
Pushing large sets of attendance periods into Personio via the API used to be difficult because every "incorrect" element in the list caused an interruption in the whole POST process.
Added the absence category attribute to the "TimeOffType" object: