API Release News from August 20, 2026

Here’s what’s new in API that’s been in production since August 20, 2026!

Breaking Changes:

Zero price will no longer clear a price in the Pricelists API

Affected endpoint: PATCH /api/pricelists/{id}
Rollout: gradual, per e-shop, starting 14.9.2026 — controlled by a feature flag on our side

What changes

Today, sending a literal 0 in data.price.price, data.price.commonPrice, data.price.buyPrice, or data.prices.purchasePrice.price clears the price — the same as sending null.

After the change, 0 will be stored as a genuine price of zero:

– for data.price.price, data.price.commonPrice this means an orderable, free item
– for data.price.buyPrice, data.prices.purchasePrice.price it is a purchase cost of 0 and does not affect orderability.

The only way to remove a price will be an explicit null. Fields you don’t send remain untouched, as before.

What you need to do

If your addon sends 0 to clear a price, switch it to null before 14.9.2026. Sending null already works today, so you can migrate immediately — no need to wait for the rollout.

Also note that a 0.00 value may already appear in GET responses today when a merchant sets a genuine zero price in administration or via CSV/XML import — make sure your integration treats 0.00 and null as distinct values.

Related change for CSV/XML import and export

The same distinction now applies to product import and export: an empty cell means “no price” and a literal 0 means a genuine zero price. If your integration generates import files, verify it doesn’t write 0 for products that should have no price — especially files derived from older exports, where a missing price was rendered as 0 .

Documentation

The updated behavior is described in the Pricelists endpoint documentation — see the PATCH /api/pricelists/{id} description.

‘Buy X, Get Y’ discounts activation at the cash register

Affected endpoint: PATCH /api/xy-discounts/settings
Rollout: one-time global, starting 31.8.2026

What changes

Today, enabling setting enableInCashdesk was checked only against internal project language, now it will be checked against cash desk/cash register modules.

What you need to do

Verify that project has indeed cash desk or cash register enabled before setting enableInCashdesk to true.

 

 


If you have any API-related questions, feedback or requests, please do not hesitate to contact us on api@shoptet.cz. We would love to hear from you!

Post navigation