Here’s what’s new in API that’s been in production since November 2, 2026!
salesChannelGuid, and filtering orders by the store GUID also returns orders from all of its cash desks. From November 16, 2026, GET /api/orders, GET /api/orders/{code} and order snapshots will return the cash desk’s own GUID, and the salesChannelGuid filter will match only the channel you pass.salesChannelGuid against known stores, expect new, previously unseen GUIDs. Cash desks and their parent store will be available in GET /api/sales-channels via the new parentSalesChannelGuid attribute (see the plans below).PATCH /api/pricelists/{id}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:
data.price.price, data.price.commonPrice this means an orderable, free itemdata.price.buyPrice, data.prices.purchasePrice.price it is a purchase cost of 0 and does not affect orderability.null. Fields you don’t send remain untouched, as before.0 to clear a price, switch it to null before 16.11.2026. Sending null already works today, so you can migrate immediately — no need to wait for the rollout.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.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 .PATCH /api/pricelists/{id} description.POST /api/customers/batch creates customers in bulk as an asynchronous job. See the documentation.pricelist:update event fires when a price list’s name, currency or sales channel assignment changes. It does not fire on changes of individual prices within a price list. See the documentation.eshop:language event fires when a language is added to the e-shop or the language configuration changes. Until now, only a change of the default language was reported, via eshop:settingsInformation. See the documentation.internalOrderNumber, the buyer’s own purchase order number. It is returned by GET /api/orders and GET /api/orders/{code}, and can be set via POST /api/orders and PATCH /api/orders/{code}. Invoices, proforma invoices and delivery notes return it read-only, populated from the order at the time the document is created; changing it on the order later does not update existing documents. Orders also expose a new read-only marketplaceOrderId attribute.New features and improvements in progress, e.g.:
PATCH /api/customers/batcharticle:create, article:update and article:delete, with optional payloadPlease note: The plan above is subject to change due to unexpected events or changes in priorities — we do not commit to deliver these outputs and outcomes. Thank you for your understanding.
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!