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-23

Breaking changes
Requires a subcategory display label on POST /v1/productsBreaking change
Breaking changeProducts

POST /v1/products now accepts only the subcategory display labels that GET /products/categories lists, such as General Clothing, matched against product_category. Coarse values such as PHYSICAL_GENERAL were accepted before and now answer 400, as does any category and subcategory pair that does not resolve to a product tax code. product_subcategory is a plain string, and product responses return the same display label.

What to do
  • Send the subcategory display label from GET /products/categories as product_subcategory, not a coarse value such as PHYSICAL_GENERAL.
  • Handle 400 on POST /v1/products for a category and subcategory pair that does not resolve.

2026-10-14

Breaking changes
Rejects null on product and product configuration updatesBreaking change
Breaking changeProducts

PATCH /products/{product_id} now answers 422 when any field is sent as null; before, it answered 200 and changed nothing. A field you leave out keeps its value and a field you send is written as sent. To clear a description, send an empty string. PATCH /products/configs/{config_id} answers 422 for null on every field except productDescription, which null clears. Before, null on aiEnabled, isDefault or a category field changed nothing, and a null subcategory beside a category answered 400. This applies to every Api-Version.

What to do
  • Leave out a field you do not want to change instead of sending null.
  • Send an empty string as description to clear a product description.

2026-09-17

Breaking changes
Returns the existing product when a product is created twiceBreaking change
Breaking changeProducts

Creating a product with an external_id and source that already exist used to fail with 409 Conflict. It now succeeds with 200 and returns the stored product unchanged: the fields in the request are not applied. A product you deleted is restored instead, with status PENDING, and is not used in tax calculation until it is approved again. Creating a new product now answers 201 instead of 200.

What to do
  • Treat both 201 and 200 as success.
  • Stop relying on 409 to detect an existing product.
  • To change an existing product, update it with PUT /v1/products/{product_id}.
Kintsugi API Changelog: 2026