The POST Create Compensation endpoint has been erroneously returning additional attributes in the 'type' object. These attributes will be removed from the response on 18 November, 2024 and are as follows:
Personio is proud to announce the GA launch of webhooks for Creation/Updation/Deletion (C/U/D) events for Absences and Attendances, to all our customers and partners. The specific event descriptions for these events are hosted here ; Please do note that the IDs returned in these webhooks are ONLY compatible with the v2 endpoints for Absences and Attendances , which are currently in Open Alpha.
Personio is proud to announce the launch of our Attendance v2 and Absence v2 APIs into Open Alpha. They are ready for use by all of Personio's customers and partners; Since these APIs are in Alpha, we expect further evolutionary changes before they are promoted to General Availability.
Currently, when existing API credentials are updated by adding/removing endpoint scopes, the existing tokens are not invalidated. Starting September 2, once scopes are added or removed, the existing authenticated API credentials will be invalidated, requiring clients to re-authenticate.
The v2 Persons GET, POST and PATCH Persons endpoint now allows for the retrieval, creation and updation, respectively, of values for the attribute 'full_time_weekly_working_hours' and therefore enables programmatic control over the maximum working hours for one or more employees in an organization.
Personio has added two new webhooks to its roster i.e. 'employment.started' and 'employment.terminated' (https://developer.personio.de/v2.0/reference/webhooks); These webhooks are triggered for a specific set of employees on the date of occurence of the employment start and/or the employment termination events. For more details, please refer to the link above
In keeping with Personio's continuous improvement model to our Public APIs, we have added two attributes to our GET Compensations API viz., 'weekly_working_hours' and 'full_time_weekly_working_hours'. The addition of those two attributes enable customers and partners to derive effective salaries for employees, based on the actual hours worked and hence improves the flexibility and usability of the Compensations API
As more of our customers and partners adopt Personio's APIs, one of the consistent feedback points that we have heard is around the unavailability of the available options of a 'List' and/or a 'Tags' variable via the Public API. We have addressed this issue with this enhancement release on the GET List Allowed Attributes endpoint i.e.(https://developer.personio.de/reference/get_company-employees-attributes) whereby the available options for a 'List' and/or a 'Tags' variable are now present in a new 'options' object in the payload.
Personio is proud to announce the General Availability of our Person & Employment v2 APIs (https://developer.personio.de/v2.0/reference/get_v2-persons and https://developer.personio.de/v2.0/reference/get_v2-persons-person-id-employments) for use by all our customers and partners
Personio has released a GET Org Units endpoint that enables users to retrieve details about their organizational structure programmatically via the Public API (https://developer.personio.de/v2.0/reference/getorgunit-1). This endpoint also allows for optional retrieval of a particular Org Unit's parent chain via a query parameter
