> ## Documentation Index
> Fetch the complete documentation index at: https://api.veda.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> New updates and improvements

[//]: # "<Expandable title=\"Upcoming Changes\">"

[//]: # "    <Update label=\"To be finalised\" tags={[\"New Releases\", \"Improvements\"]}>"

[//]: # "    </Update>"

[//]: # "</Expandable>"

<Update label="19. June 2026" tags={["New Releases", "Improvements"]}>
  ## New Features and Improvements

  * Added [birthName](/api-reference/endpoint/persons#response-items-birth-name) field to person endpoints
  * Added [Group](/api-reference/endpoint/groups) `COMPANY` describing the company configured for employees in the Platform
</Update>

<Update label="13. June 2026" tags={["New Releases", "Improvements"]}>
  <Icon icon="location-exclamation" /> Adding values to enums is not considered a breaking change. The employment `paymentTime` enum has been extended to allow for arbitrary string values. See the Bug Fixes section for more details.

  ## New Features and Improvements

  * Absences are finally here! The new Absences endpoints allow you to retrieve information about absences of one or all persons: [Absences](/api-reference/endpoint/absences) and [Person Absences](/api-reference/endpoint/person-absences)
  * Added a [Time Bookings endpoint](/api-reference/endpoint/time-bookings) to retrieve time bookings for all persons, complementing the existing [single-person endpoint](/api-reference/endpoint/person-time-bookings).
  * The new [Time Booking Keys endpoint](/api-reference/endpoint/time-booking-keys) allows you to look up the booking keys that are used in the time bookings and absences.
  * Variable payments can now be submitted for payroll processing. Use the new [Variable Payments](/api-reference/endpoint/variable-payments-post) endpoint to post bonuses or other one-time payroll supplements for a payroll contract. They will be forwarded to the payroll administrator for approval.
  * Once approved, submitted variable payments are visible via the [Variable Payments GET endpoint](/api-reference/endpoint/variable-payments), which lists all variable payments for a given payroll contract and billing period.

  ## Bug Fixes

  * [Payment times](/api-reference/endpoint/persons#response-items-employments-items-payment-time-one-of-0) were incorrectly limited to the four values provided in the standard version. If you have configured a custom payment time in your system, its id will now be returned instead of the enum values.
</Update>

<Update label="03. June 2026" tags={["New Releases"]}>
  ## New Features and Improvements

  * Want to know the name of the group a person is in? The new [Groups endpoint](/api-reference/endpoint/groups) lets you look up groups by type and returns their names.
</Update>

<Update label="08. May 2026" tags={["New Releases", "Improvements", "Deprecation"]}>
  <Icon icon="location-exclamation" /> To support writing information the access token scope has changed from `api:read` to `api:use`.

  ## New Features and Improvements

  * Many new fields for the [person endpoints](/api-reference/endpoint/persons): `usualPlaceOfWork`, `status`, `groupExitDate`, `exitReasonId`, `exitNoticeDate`, `legalEntity`, `groups` (`PAYROLL_COMPANY`, `TIME_COMPANY`, `ORGANISATIONAL_UNIT`, `COST_CENTER`, `PAYROLL_GROUP`, `BUSINESS_AREA`), `keyNumber`, `employments` (`personGroupCode`, `fullTime`, `permanent`, `start`, `end`, `fixedTermEndDate`, `workingHours`, `paymentTime`)
  * The first write endpoint enables you to set and update a person's private addresses and bank details. [PATCH Person By ID](/api-reference/endpoint/persons-id-put)
  * If you want to take a look at what you've written, you can also find the bank details in the person endpoints. [Persons - bankDetails](/api-reference/endpoint/persons#response-items-bank-details)
  * Resolved the confusing mix of [Time Balances](/api-reference/endpoint/person-time-balances) and [Time Accounts](/api-reference/endpoint/person-time-accounts).
  * The api returns HTTP status codes 405 (Method Not Allowed) and 406 (Not Acceptable) when a request is made using an unsupported HTTP method or with an unsupported `Accept` header, respectively.
  * The api now supports `HEAD` requests for all endpoints that support `GET` requests. By definition, these requests will be processed in the same way as GET requests, but no body will be returned.

  ## Bug Fixes

  * The [persons endpoint](/api-reference/endpoint/persons#response-items-custom-fields) no longer returns an error if the VEDA API doesn't have permission to read any custom fields.

  ## Deprecation

  * Deprecated [Person#payrollContractIds](/api-reference/endpoint/persons#response-items-payroll-contract-ids) in favour of the new Person#employments field. Payroll contract IDs are still available in the employments, but the new structure allows for more detailed employment information.
</Update>

<Update label="24. March 2026" tags={["Improvements"]}>
  ## New Features and Improvements

  * Improved error handling. Less generic server errors and more 4xx type error responses. Improved and aligned response bodies and codes for invalid request parameters.
  * Added support for `customFields` when requesting multiple persons.
  * Changes to non-primal payroll employments are now correctly reflected in person queries using the `modifiedSince` parameter. Empty objects are no longer returned.
</Update>

<Update label="14. November 2025" tags={["New Releases", "Improvements"]}>
  ## New Features and Improvements

  * Added support for `additionalAddressInfo` when requesting multiple persons.
  * The `unit` field in time booking days has been removed, as the day sums are always returned in hours and minutes.
  * If a data source is needed more than once to answer a query, it's only accessed once and the result is cached. This improves the performance of larger, more complex requests.

  ## Bug Fixes

  * The [Time Bookings endpoint](/api-reference/endpoint/person-time-bookings) now correctly uses the `time-bookings` path instead of the incorrect `timebookings`.
</Update>

<Update label="30. September 2025" tags={["New Releases"]}>
  Hello World!
</Update>