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.

All changes Breaking only

Area: Connections

All areas Addresses Connections Exemptions Filings Imports Nexus Organizations Products Registrations Reports Transactions

Clear filters

Jump to date

2026-10-05

Breaking changes

Returns already_connected when an activated store is already connectedConnections

Breaking changeConnections

When POST /connections/apideck/{conn_id}/activate finds that the shopId belongs to a connection your organization already has, it reactivates that existing connection, removes the one being activated, and answers 400 as before. The error code is now already_connected instead of invalid_request, with the message This store is already connected. The existing connection was reactivated. The store is connected and nothing more is needed. already_connected is a new value of the code field in error responses.

Endpoints

POST/connections/apideck/{conn_id}/activate2026-07-21

What to do

Treat 400 with code already_connected as success, and list your connections again to find the one that remains.
Stop relying on invalid_request to detect an already connected store.
If your client accepts only known code values, add already_connected.