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 changesRequires a subcategory display label on POST /v1/productsProductsBreaking change
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.
- Send the subcategory display label from
GET /products/categoriesasproduct_subcategory, not a coarse value such asPHYSICAL_GENERAL. - Handle
400onPOST /v1/productsfor a category and subcategory pair that does not resolve.
2026-10-14
Breaking changesRejects null on product and product configuration updatesProductsBreaking change
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.
- Leave out a field you do not want to change instead of sending
null. - Send an empty string as
descriptionto clear a product description.
2026-09-17
Breaking changesReturns the existing product when a product is created twiceProductsBreaking change
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.
- Treat both
201and200as success. - Stop relying on
409to detect an existing product. - To change an existing product, update it with
PUT /v1/products/{product_id}.