Skip to main content

Change list

Every change to the tenant API, newest first. Each entry has its own page in three parts:

  • What changed: the change itself, with the fields, status codes and problem types it touches.
  • Affected operations: the endpoints and webhooks the change reaches.
  • What you do: what your integration must do, or that nothing is needed.

Breaking says whether a call or a read that works today can stop working. The versioning policy says what counts as breaking, how a breaking change is announced and how long a deprecated endpoint stays.

Upcoming means that the change is in the reference, which is built from the main branch, but not yet in production. When it reaches production the entry shows Released with that date.

DateChangeBreakingStatus
2026-11-18Response headers and paging limits in the referenceNoUpcoming
2026-11-17Examples for every endpointNoUpcoming
2026-11-17Deprecated endpoints link their change list entryNoUpcoming
2026-11-17Baseline of v1NoUpcoming
2026-11-15Payment sumsNoUpcoming
2026-11-15Payment factsNoUpcoming
2026-11-15Shipments with lines and parcels, delivery endpoint closedYesUpcoming
2026-11-15Cancellations, returns and deliveries reported as factsYesUpcoming
2026-11-14Amounts in minor unitsYesUpcoming
2026-11-14Line status endpoint closedYesUpcoming
2026-11-14Line status derived from the quantitiesYesUpcoming
2026-11-14Line quantities follow the quantity rulesYesUpcoming
2026-11-14Customer name and email are optionalYesUpcoming
2026-11-14VAT basis required on every new orderYesUpcoming
2026-11-14VAT rate required on every new order lineYesUpcoming