Personio is proud to announce the launch of the Webhooks Events API (https://developer.personio.de/v2.0/reference/get_v2-webhooks-id-events), which enables our customers to obtain a list of all events associated with a specific Webhook config. to upto 30 days in the past. Users are also able to specify a query timeframe by using the 'occured_at' fields as well as an event name using the 'event_name' field.
Personio will be updating a set of absence categories to better align with market needs and enhance flexibility of absence types for all customers. The summary of the changes are present below:
Based on the feedback received from customers and partners regarding the date of pagination enforcement on the v1 Employees API and a desire for our API users to have as smooth a transition as possible, the date of pagination enforcement will be moved from December 7, 2024 to January 31, 2025. We thank all of our users for their continuous feedback and support and we will continue to ensure that your feedback is listened to and actioned upon.
For the following v1 endpoints - GET v1/company/attendances, POST v1/company/attendances, GET v1/company/time-offs, POST v1/company/time-offs and GET v1/company/time-offs/{id} and GET v1/company/time-off-types there will be an additional field in the payload named 'id_v2'.
Personio is proud to announce the launch of webhooks for document created, updated, signed and deleted events. Specific event descriptions are found here. Please do note that these webhooks are only triggered for employee-owned documents.
After receiving feedback from our partners on the pagination enforcement post, we have decided to exclude all partner accounts from the pagination enforcement scheduled for December 7.
As of September 16, 2024 the following attributes were deprecated from the response of the GET Absence Types endpoint (https://developer.personio.de/reference/get_company-time-off-types)
As of October 9, 2024 Personio will update the error response of the v1 GET Absence Periods endpoint (https://api.personio.de/v1/company/absence-periods) to return a 404 error response when an invalid Absence Type ID is provided in the query parameter of a request. Currently, when an invalid Absence Type ID is provided in the query parameter, a 500 error response is provided.
Context:
Personio has added a new Absence Webhook to its catalog of webhook offerings i.e. Absence Status Updated (documentation here: https://developer.personio.de/v2.0/reference/webhooks#absence-periodupdatedstatus) which is triggered when the status of an Absence period is changed, for eg. from "Pending" to "Approved".
