KintsugiKintsugi
API reference / Changelog / 2026

API changelog: 2026

Every change to the Kintsugi API in 2026, newest first. For the latest changes and every release, see the API changelog.

2026-10-16

Breaking changes
Ends nexus and registration timestamps with ZBreaking change
Breaking changeNexus

Timestamps in nexus and registration responses now carry an explicit UTC marker, as in 2026-01-02T03:04:05Z. Before, they had no UTC offset, as in 2026-01-02T03:04:05. The values are unchanged and were always UTC. On a nexus the fields are created_at, updated_at, earliest_transaction_date, most_recent_transaction_date, earliest_collected_date, last_processed_at, last_tax_liability_processed_at, disregarded_at and registration.deregistration_completed. On a registration they are registration_requested, registration_completed, deregistration_requested, deregistration_completed, marked_collecting_date, created_at and deregistration_acknowledged_at. A parser that expects the exact old format fails on the new one.

What to do
  • Parse these fields as RFC 3339 date-times, which accept the Z suffix, instead of matching the old format.
  • Treat the values as UTC, and convert them to a local time only for display.

2026-10-14

Breaking changes
Reopens a physical presence with endDate null and rejects null on other fieldsBreaking change
Breaking changeNexus

PATCH /physical-nexus/{physical_nexus_id} now treats endDate: null as reopening a closed presence; before, null on any field meant leave it unchanged, and a closed presence could not be reopened. null on category, startDate, street1, street2, city or postalCode now answers 422. An empty string still clears an address field, and a field you leave out keeps its value. Reopening recalculates exposure like any other date change. This applies to every Api-Version.

What to do
  • Send endDate: null to reopen a presence, and leave endDate out to keep it.
  • Stop sending null on the other fields. Leave them out, or send an empty string to clear an address field.

2026-09-21

Breaking changes
Returns the existing record when a physical nexus is created twiceBreaking change
Breaking changeNexus

Creating a physical nexus for an organization, country, state and category that already has one used to fail with 409 Conflict. It now succeeds and returns the stored record unchanged: the dates and address in the request are not applied. On v1 and the Partner API the response is 200, the same as for a new record. On the 2026-07-21 release it is 200 for an existing record and 201 for a new one.

What to do
  • Stop relying on 409 to detect an existing record.
  • To change an existing record's dates or address, update it: PUT /v1/nexus/physical_nexus/{physical_nexus_id} on v1, or PATCH /physical-nexus/{physical_nexus_id} on the 2026-07-21 release.
Kintsugi API Changelog: 2026