Personio API
Attendances and Projects v1 API removal
Stops workingSubscribe to Personio APIShare
On January 31, 2027, the attendance and projects v1 endpoints will stop working. Calls to /v1/company/attendances* will fail after this date. Integrations using these v1 endpoints must move to their v2 versions to maintain service.
Calls it hits
/v1/company/attendances*
What to use instead of these calls
Migrate to the v2 Attendance Periods API at /v2/attendance-periods, which uses UUID ids, explicit break periods, and skip_approval=true to skip approval. For projects, use the v2 Projects API at /v2/projects with status=ACTIVE/ARCHIVED instead of active.
In Personio API's words
The attendance and projects v1 endpoints will be deprecated in favor of their v2 versions with the final deprecation date set for Jan 31, 2027. All integrations using these v1 endpoints must migrate to the v2 APIs to ensure continued service
Facts
- API
- Personio API
api.personio.de - Kind
- Removal
- Takes effect
- January 31, 2027
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Personio API's own pages
Questions
When does this change take effect?
Calls to /v1/company/attendances* on Personio API stop working on January 31, 2027.
What happens to calls after January 31, 2027?
They fail from that day.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before January 31, 2027.