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.
| Date | Change | Breaking | Status |
|---|---|---|---|
| 2026-11-18 | Response headers and paging limits in the reference | No | Upcoming |
| 2026-11-17 | Examples for every endpoint | No | Upcoming |
| 2026-11-17 | Deprecated endpoints link their change list entry | No | Upcoming |
| 2026-11-17 | Baseline of v1 | No | Upcoming |
| 2026-11-15 | Payment sums | No | Upcoming |
| 2026-11-15 | Payment facts | No | Upcoming |
| 2026-11-15 | Shipments with lines and parcels, delivery endpoint closed | Yes | Upcoming |
| 2026-11-15 | Cancellations, returns and deliveries reported as facts | Yes | Upcoming |
| 2026-11-14 | Amounts in minor units | Yes | Upcoming |
| 2026-11-14 | Line status endpoint closed | Yes | Upcoming |
| 2026-11-14 | Line status derived from the quantities | Yes | Upcoming |
| 2026-11-14 | Line quantities follow the quantity rules | Yes | Upcoming |
| 2026-11-14 | Customer name and email are optional | Yes | Upcoming |
| 2026-11-14 | VAT basis required on every new order | Yes | Upcoming |
| 2026-11-14 | VAT rate required on every new order line | Yes | Upcoming |