Deprecation of legacy API endpoints on May 1, 2026

We retire a set of legacy API endpoints because more efficient and up-to-date versions exist. This change supports ongoing improvements to the reliability and scalability of our API platform. 

Please update all self-built integrations by May 1, 2026. If you only use our partner integrations, such as for creating invoices, you don’t need to do anything.

What does this mean for interface owners and companies?

If you use our API for data exchange with other systems, custom reports, or automations, take action now: 

• Review your integrations. Identify any remaining usage of deprecated endpoints.
• Plan the migration. Start the switch to the new endpoints early to avoid disruptions. 

Affected endpoints and their successors

These endpoints are removed. Please switch to the listed routes. 

• api/absences ⇒ api/v4/absences
• api/customers ⇒ api/v3/customers
• api/v2/customers/countProjects ⇒ api/v3/customers/countProjects
• api/entries ⇒ api/v2/entries
• api/holidaysquota ⇒ api/v2/holidaysQuota
• api/lumpsumservices ⇒ api/v4/lumpSumServices
• api/services ⇒ api/v4/services
• api/users ⇒ api/v3/users
• api/users/me ⇒ api/v4/users/me
• api/v2/absences ⇒ api/v4/absences
• api/v3/absences ⇒ api/v4/absences
• api/v2/aggregates/users/me ⇒ api/v4/users/me
• api/v2/customers ⇒ api/v3/customers
• api/v2/entriesTexts ⇒ api/v3/entriesTexts
• api/holidayscarry ⇒ api/v3/holidaysCarry
• api/v2/lumpsumservices ⇒ api/v4/lumpSumServices
• api/v3/lumpsumservices ⇒ api/v4/lumpSumServices
• api/nonbusinessdays ⇒ api/v2/nonbusinessDays
• api/nonbusinessgroups ⇒ api/v2/nonbusinessGroups
• api/overtimecarry ⇒ api/v3/overtimeCarry
• api/v2/projects ⇒ api/v4/projects
• api/v2/services ⇒ api/v4/services
• api/v3/services ⇒ api/v4/services
• api/v2/teams ⇒ api/v3/teams
• api/v2/users ⇒ api/v3/users
• api/v2/users/me ⇒ api/v4/users/me
• api/v2/workTimes/changeRequests/{id}/approve ⇒ api/v3/workTimes/changeRequests/{id}/approve 

Access the API documentation for details.