Changelog

We have launched Personio's Compensations API (https://developer.personio.de/v2.0/reference/get_v2-compensations-types) to general availability for all users who already have access to Personio's Public API. Users will be able to retrieve the types of compensation and the granular details of compensation for employees; In addition users will also be able create new types of compensation and create granular compensations for employees. In addition, users will able to filter GET requests by employee IDs and/or legal entity IDs for maximum flexibility

As part of our continuous approach to ensure the stability and reliability of the Personio Public API, we are introducing rate-limits to the GET Employees API endpoint (https://developer.personio.de/reference/get_company-employees) from May 6, 2024. A few salient points to note:

Personio Webhooks is in General Availability status and can be used by customers who have access to Personio's Public APIs. The API endpoints to create, manage and delete webhook subscriptions are present here; Personio Webhooks are modeled on Dataless Notifications in order to prevent PII data leaks and enhanced security. The scope of this release is updates to the Person entity in Personio and is explained in the API doc link above

We have introduced a Postman collection for the Personio Public API v1 in order to provide our API users with a pre-built set of methods to evaluate and integrate with our Public APIs in an easy manner. The Postman Collection is present on the Introduction page of our API Reference documentation and we welcome feedback on how to improve this offering.

A patch was applied on the POST Employees API endpoint wherein the value of 'weekly_working_hours' field is ingested accurately during the creation of a new employee; Previously the value of 'weekly_working_hours' was not being ingested during the employee creation process via the POST Employees enpoint.

As of April 8, 2024 the attribute ‘vacation_day_balance’ will be deprecated and removed from the GET Employees endpoint’s response, in favour of retrieving absence data from https://developer.personio.de/reference/get_company-employees-employee-id-absences-balance; This adjustment is aims to enhance usability and accuracy of the retrieved absence data as the original endpoint defaulted to returning only the balance of the highest-order absence type. The alternate endpoint (mentioned above) now offers balances for all absence types where the employee possesses a balance. We strongly advise customers and partners integrating this feature to make use of the dedicated endpoint mentioned above to prevent any integration disruptions.

The POST Absence Periods endpoint has been upgraded in a graceful manner, to accept hourly absence requests in accordance with the absence certificate requirement set on the Personio application. It is now optional to upload a certificate when creating an absence via the UI for hourly absence types, mirroring the behaviour of daily absence types. So creating an absence through the endpoint wouldn’t require uploading a certificate. However, the capability to upload a certificate itself through the endpoint remains unsupported at this time.

As of 8 January 2024, there will be a new field added to the response of the GET Employees endpoint i.e. 'preferred_name'. Please note that this is an additive change and will not break existing integrations.

The maximum number of employees whose attendances can be posted in a single POST request to this Attendances endpoint (https://developer.personio.de/reference/post_company-attendances) is set to 100, in order to maintain system stability.

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.