Change Log

Change Log

 

With this release we mainly extended our API by introducing new endpoints to access or update different aspects of the employee master or varibale data.

 

 

02.07.2025 (Released with Version 252.2.0)

  • Re-Work Master Data endpoint

    • The GET (all), GET (by ID), and PATCH endpoints have been revised and modernized.

    • The field ‘dateOfBirth’ is now located directly under ‘masterData’ – it is no longer under ‘masterData.additionalData’.

  • Re-Work/Update for endpoint: /dabpv/registration

    • To improve compatibility with Addison’s system, the endpoint method is now changed from PATCH to PUT.

    • This update keeps the same functionality while ensuring smoother operation.

 

18.06.2025 (Released with Version 252.1)

  • Component: DATEV LODAS – Master Data Import

    • Change Type: Field Requirement Update

    • The Person Group Key (Personengruppenschlüssel) is no longer a mandatory field when creating a new employee via the master data import interface.

 

04.06.2025 (Released with Version 251.7.0)

  • Implement endpoints to update existing contact data and add new contact data for an employee. It should support updating or adding one or multiple contact entries per employee.

  • Re-Work the update (PUT) endpoint for the variable data: It is now possible to update one or multiple variable data entries for one or more employees in a single API call. The update is now possible for only the changed fields. When a variable data entry is created using ‘hours, the response now includes the calculated 'industrialMinutes'.

  • Re-Work the master data endpoint: The endpoint now supports both reading (GET) and updating (PATCH) master data. The main object has been renamed from'employee'to 'masterdata'. The sub-object 'additionalNameInfo' is now called 'additionalData'. The field 'personalNumber' has been renamed to 'personnelNumber' and is no longer mandatory during updates. The field 'martialStatus' has been renamed to 'married'. Updates can be performed without providing all fields. If the IBAN is not from a German bank, the BIC field becomes mandatory. Any non-existent fields in the payload (e.g., bankname) are ignored.

 

07.05.2025 (Released with Version 251.5.0)

  • Implement considering the master data start date from LODAS file import

  • Re-Work the contracts data endpoint, now called 'contract' instead of 'contracts'. You can retrieve data for all employees or a single employee (GET), or update contract data for a single employee (PUT). The entry date cannot be changed, but individual fields can be updated. Additionally, new fields such as vacationDaysOverallEntitlement and weeklyWorkingHours are added.

  • Implement option to update address data for employee (PUT). The endpoint is now called 'address' instead of 'addresses'. Additionally, we have introduced the 'countryId'.

     

23.04.2025  (Released with Version 251.4.0 )

  • Re-Work the compensation resource for reading, updating and creating recurring compensations of an employee (GET, PUT, POST)

  • Re-work social insurance endpoint: Get social insurance data of all employees or for a single employee (GET) or update social insurance data of a single employee (PUT) 

  • Re-Work tax data: Get tax data of all employees or for a single employee (GET) or update tax data of a single employee (PUT)

 

09.04.2025 (Released with Version 251.3.0)

  • Import data from clocko:do (external time tracking) to the payroll accounting

  • Import Variable data from LODAS Lodas

  • Add, retrieve, or update capital-building contracts for a specific employee (GET, PUT, POST)

  • Update address data for a specific employee (PUT)

 

26.02.2025 (Released with Version 244.7.0)

  • GET a list of wage types (GET): API endpoint to receive a list of all available wage types (e.g. to map them for sending variable data)

 

12.03.2025 (Released with Version 251.1.0)

New Endpoints:

  • LODAS file import: This API endpoint allows the import of master data, variable data, fixed compensations, and absences using a DATEV LODAS file (POST).

  • Retrieval of establishments: A GET Endpoint for Establishments has been released, allowing users to programmatically retrieve details about the structure of establishments via the API. This endpoint allows users to either retrieve all establishments or to get a specific establishment using a parameter (GET).

  • Get common master data: This endpoint returns the common master data like our known prefixes, affixes, countries and nationalities. These data can be used, for example, when creating new employees (GET).

  • Get contract data of all employees or for a single employee (GET) and update contract data of a single employee (PUT) 

  • Get contact data of employees: Two new endpoints have been introduced to retrieve contact data: one for individual employees and one for all employees (GET).

  • Get address data of employees: Two new endpoints have now been introduced to retrieve address data: one for retrieving the address of a single employee and one for retrieving the addresses of all employees (GET).

  • Get tax details for either a single employee or all employees (GET) and update tax details for a single employe (PUT)  

  • Get social insurance details for either a single employee or all employees (GET) or update social insurance details for a single employe (PUT).

Changed Endpoints:

  • Adjustments to endpoints for eAU minimal data (Retrieval of data for all employees or for a single employee (GET): Our endpoints that deliver only the required information for the eAU process for time tracking applications have been adjusted to only return the data required for the eAU.

  • Deleted Endpoints: No API was deleted.