In order to provide our customers and partners with a reliable and performant API, we have instituted a rate limit of 2000 requests per min, based on the IP address of the requester. We have also updated our API TOS here: https://developer.personio.de/docs/tos-api-security-1 in the interests of complete transparency

As of 24 June, 2024 Personio Webhooks will have an extended retry policy for all current and future webhooks. The number of retries has been increased from 2 to 6 and the time window of retries is extended from 120 seconds to 6 days. More info here, in the 'Retries' section: https://developer.personio.de/v2.0/reference/webhooks

We are adding a UI filtering component to our API credentials page, that allows users of the Compensation API to specify the Legal Entities for whom Compensation data should be returned only when a GET call is made to the Compensations API endpoint. Please note that the UI filter will override Legal Entity values specified in the query parameter of the GET call and that the filter only applies to the GET API endpoint's response payloads.

Personio Webhooks for Employment events 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 Employment entity in Personio and is explained in the API doc link above

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.