Breadcrumbs

Release Notes 22.04.2026

Administration API

API Contract Update: New Optional Properties Added

New optional properties were added to selected Administration API request and response schemas.

Affected endpoints

  • GET /v1-ext/Company

    • PUT /v1-ext/TablePlanner/{storeId}

Affected fields

Response (GET /v1-ext/Company)

Added new optional properties under company settings:

  • orderParkArchiveDays

    • validatePhoneNumbersEnabled

Request (PUT /v1-ext/TablePlanner/{storeId})

Added new optional request property:

  • useTableListAsDefaultView

Consumer action

No mandatory action is required for existing consumers, since all added properties are optional.

However:

  • Consumers of GET /v1-ext/Company may start receiving the new optional fields:

    • orderParkArchiveDays

    • validatePhoneNumbersEnabled

    • Consumers of PUT /v1-ext/TablePlanner/{storeId} can now optionally provide:

      • useTableListAsDefaultView

If you use strict schema validation, generated models, or explicit request/response mappings, consider updating them to include these new properties.

Customership API

API Contract Update: Phone Number Length Increased

The maximum length of phone number fields has been increased from 15 to 16 characters in selected Customer API request and response schemas.

Affected endpoints

  • POST /v1-ext/Customers/byIds

    • GET /v1-ext/Customers/filter

    • POST /v1-ext/Cardu/customers

    • POST /v1-ext/Customers

Affected fields

  • person.phoneNumbers[]

    • contactPersons[].phoneNumbers[]

Consumer action

Please update any client-side or server-side validation rules that assume a maximum phone number length of 15 characters.

Receipts API

API Contract Update: New Request Body Media Type Added

A new request body media type was added to an existing Receipts API endpoint.

Affected endpoints

  • POST /v1-ext/Receipt/delivery

Affected fields

No request or response fields were changed.

Change details

Added support for the following additional request body media type:

  • application/json-patch+json

Consumer action

No mandatory action is required for existing consumers.

However, consumers of POST /v1-ext/Receipt/delivery can now also send requests using:

  • application/json-patch+json

If you use generated clients, strict OpenAPI validation, or media type whitelisting, consider updating your configuration to recognize this newly supported request content type.