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-11-19

Breaking changes
Answers 400 when a Saleor connection needs a change before tax calculation can startBreaking change
Breaking changeConnections

POST /connections/{conn_id}/enable-tax-collection answers 400 with a message that says what to change when Saleor refuses the setup, for example because the Saleor app is missing a permission. These refusals answered 503 before, which invited a retry that could not succeed. A request made while another tax change for the same Saleor store is still running keeps answering 503 with a fixed message and a Retry-After header, and a retry then can succeed.

What to do
  • Treat 400 from POST /connections/{conn_id}/enable-tax-collection as final: show the message and retry only after the setting it names is changed.
  • Keep retrying 503, waiting for the Retry-After interval.

2026-11-11

Breaking changes
Turns off Saleor tax collection when you delete or disable a Saleor connectionBreaking change
Breaking changeConnections

DELETE /connections/{conn_id} on a Saleor connection now turns its tax collection off before archiving it. If the store still has Kintsugi's tax setup afterwards, the connection is not archived and the request answers 503; retrying may succeed. POST /connections/{conn_id}/disable-tax-collection on a Saleor connection that is already disabled retries any tax setup an earlier disable left behind, and answers 503, leaving tax collection enabled, while another tax change for the same store is running. A Saleor outage during that cleanup does not fail the request, so call disable again to retry it. POST /connections/vertex-o-series/{conn_id}/mark-installed answers 400 for a Saleor connection, because Saleor tax collection is turned on from the connection's own tax setting.

What to do
  • On 503 from DELETE /connections/{conn_id} or POST /connections/{conn_id}/disable-tax-collection, wait a moment and send the same request again.
  • Do not call POST /connections/vertex-o-series/{conn_id}/mark-installed for a Saleor connection.

2026-11-05

Breaking changes
Answers 409 when you delete or disconnect a connection that has filed historyBreaking change
Breaking changeConnections

DELETE /connections/{conn_id} and POST /connections/quickbooks/disconnect now refuse to archive a connection that owns filed tax history, and answer 409 with the error code connection_has_filed_history, a new value of the error code enum. Before, both archived the connection. The connection is left unchanged, and sending the request again returns the same 409. POST /connections/quickbooks/disconnect already answers 409 when realmId matches more than one connection, so read code to tell the two apart.

What to do
  • Handle 409 with code connection_has_filed_history from both endpoints, and do not retry it.
  • Branch on code when you handle 409 from POST /connections/quickbooks/disconnect, since it also answers 409 for an ambiguous realmId.
  • Show the user that the connection cannot be removed and point them to Kintsugi support.

2026-10-29

Breaking changes
Matches an existing ERP connection when activating an Apideck connectionBreaking change
Breaking changeConnections

POST /connections/apideck/{conn_id}/activate now finds an existing live connection for the same ERP account, not only by shopId: the NetSuite subsidiary, the DualEntry company, or the QuickBooks, Xero or Dynamics 365 entity. When this connection holds no data, the existing one is reactivated and this one is deleted, and the call answers 400 with code already_connected. When only the existing connection is empty, it is removed and this one is activated. When both hold data, the call answers 409 and both connections stay. A 409 was not possible on this endpoint for these sources before.

What to do
  • Handle 409 from this endpoint by keeping the existing connection and disconnecting the one you do not need with DELETE /connections/{connId}.
  • Send netsuiteAccountId, netsuiteSubsidiaryId or dualentryCompanyId on this call, not in an earlier settings update, so they land on the connection that stays.

2026-10-15

Breaking changes

2026-10-14

Breaking changes
Refreshes a Bunny connection with POST on 2026-10-06 and rejects a null nameBreaking change
Breaking changeConnections

On Api-Version: 2026-10-06, POST /connections/bunny/{conn_id}/refresh replaces PATCH, which now answers 405. The request body is unchanged. 2026-07-21 keeps PATCH. On every Api-Version, name is written as sent, including an empty string, and is left unchanged when omitted. Sending name as null now answers 422.

What to do
  • On Api-Version: 2026-10-06, call POST instead of PATCH to refresh the connection.
  • Leave out name to keep the current name, and do not send it as null.
Clears connection settings with null and rejects an empty idBreaking change
Breaking changeConnections

PATCH /connections/{conn_id}/settings now clears a nullable field when you send it as null; before, null was ignored and no field could be cleared. That covers airwallexHistoricalSyncStartDate, woocommerceHistoricalSyncStartDate, netsuiteHistoricalSyncStartDate, microsoftD365HistoricalSyncStartDate, amazonHistoricalSyncStartDate, apideckConnectionState, dualentryCompanyId, netsuiteAccountId and netsuiteSubsidiaryId. null on needsUpdate, isOneworldAccount or netsuiteSyncMode answers 422; before, it answered 200 and changed nothing. An empty string for dualentryCompanyId, netsuiteAccountId or netsuiteSubsidiaryId now answers 422; before, it cleared the value, so send null instead. This applies to every Api-Version.

What to do
  • Send null, not an empty string, to clear dualentryCompanyId, netsuiteAccountId or netsuiteSubsidiaryId.
  • Leave out needsUpdate, isOneworldAccount and netsuiteSyncMode when they should not change.

2026-10-05

Breaking changes
Returns already_connected when an activated store is already connectedBreaking change
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.

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.
Kintsugi API Changelog: 2026