Ask a Question

Time-Off notifications via webhook?

Hello! The webhook feature is definitely a game-changing addition. Are there any plans to include Time-Off event notifications via webhook? I would appreciate to know if you are considering this on your roadmap. Thank you so much!

Add salary start date

It would be awesome if you could add salary start dates to the response when fetching employees. Ideally it would be nice to get all historical salaries as well, but just the current salary's start date would help a lot. Cheers / Fredrik

Time off types with unit "hour" are no longer returned from /v1/company/time-off-types

Hi! I was so certain that /v1/company/time-off-types used to return all absence types, both with unit "day" and "hour". But since yesterday or so I only get the "day" unit time off types. According to the docs it should return both. I created these hour-types myself so I was thinking maybe it was a permissions issue, but I can't find any obvious permissions setting for this on the settings page Cheers / Fredrik

Custom Reports: Provided authorization is not valid

Hello, I'm trying to get information from Custom_Report via your API Reference page. Usually, in every other Personal Data tab, there's a field for entering Bearer token, and after entering the token, the requests are executed correctly. However, I encountered a problem in Custom reports: there's no entry field there (only X-Partner and X-App), and when I tried to run the script, I got error 401 – ‘Provided authorisation is not valid’. I added the my token to the script myself, but still get the same error. Could you please tell me how to fix this? Is it possible to get Custom Reports in the current state of the API?

Same authentication token for v1 & v2 APIs

I want to use the latest Personio APIs but, some modules are still closed Alpha. So, I'm planning to use the APIs from both of the versions to meet the requirement. Would it possible to use the same access token to access the APIs from v1 and v2 as the requesting credentials for both of them?

absence-periods 'Filter by absence periods that start at or before given date.' is wrong.

Good evening, We are creating an interface with Personio to retrieve absence requests. This information will be forwarded to another application. Every hour we do retrieve the absence requests and only process the requests that are not yet send to the other application. We are using the absence-periods API for this and want to retrieve absence request between a particular start and end date. <https://api.personio.de/v1/company/absence-periods?start_date=2024-05-05&end_date=2025-06-04&limit=200&offset=0> We were surprised to see objects with a start date 2024-04-22 in the results. So, we did read the documentation again and we can't query the start and end date because of something strange. The start_date is: 'Filter by absence periods that start at or before given date.'. This makes the field impossible to query. The fields should be: Start_date is: 'Filter by absence periods that start at or after given date.' End date: "Filter by absence periods that start at or before given date." Is this a bug or do we see this the wrong way?

DocuWare Integration

Hi Community, Is there any way to integrate Docuware with Personio via API? Docuware is sadly nowhere to be found on the marketplace and the only integration possibility I see is using Make as 3rd party

Rate Limit Monitor

Hi, is it possible to monitor the rate limit for certain endpoints? We are getting an irregular request error from calling: <https://api.personio.de/v1/company/employees> and we would like to know if a rate limit is the cause.

List Employees with updated_since not working correct!?

example: ?updated_since=2024-05-27T00:00:01 will yield 8 employees If I get all employees and set the filter in my List<Employee> to LastModifiedAt = 2024-05-27, I get 27 employees! by the way, the first employee was changed at 09:46:17 How really works updated_since? Is my path usually correct? Is it a Bug?

Profile Pictures API not available

{ "success": false, "error": { "message": "personio.core.api.exceptions.api.not.found.http.exception", "code": 0 } }