Here’s what’s news in API Release that’s been in production since January 28, 2025!
Breaking Changes:
Change in Content-type header response
Soon we will change the response in the Content-type header (from the original application/vnd.shoptet.v1.0+json; charset=utf-8 to application/json; charset=utf-8)
Currently we don’t know the exact date yet, but as soon as it is, we will specify and let you know.
New features:
API Rate limiter
As we have already communicated in a separate post, we have launched a new key feature of our API in the form of a rate limiter
With this activity, we will try to maximize the efficiency of working with API and performance integrations that communicate with our API
For more detailed information, please see the mentioned article above from Jan 21, 2025 which is dedicated to this
Quantity discounts and a associated webhooks
Along with the quantity discount API functionality that we released late last year, we are adding support for associated webhooks, specifically the following:
quantityDiscount:create
quantityDiscount:update
quantityDiscount:delete
quantityDiscount:massDelete
quantityDiscount:massUpdate
Please note: to ensure maximum value, we recommend registering both single and mass webhooks
As we already outlined in the first release in January, we have completed the complete CRUD of Consumption taxes, which will allow complete management via API, which you can find in the Products section
Translation supports now decriptive parameters
If the module Foreign languages (Cizí jazyky) activated on customer e-shop, multi-language support in API, handled by query parameter language, can be newly used on the descriptive parameters also
If parameter is not set, default shop language is used
Improvements:
New product related products query filter
Based on feedback from some of you, we have added the possibility to filter on endpoint List of Product related products specifically what products you are interested in using the new query filter visible
If set to true, only visible products are returned (those, which does not have visibility: hidden)
Example: visible=true
Last changes endpoints enriched by query filter
We have developed the requested functionality to be able to adjust the result of Last changes endpoint consumption to a more granular output – so we added a new query filter changeType to all Last changes endpoints, which you can use to control the expected output
Query only controls whether endpoint returns edit or delete type changed records
Example: changeType=edit
Bugfixes:
404 - mistakes not found – let’s celebrate 🙂 !
What we plan in upcoming days:
We are currently working on new tooling to give you the tools to integrate with our API faster and more efficiently. We’ll be working on this over the next 14 days and will, I believe, update you with more details soon.
Please note: the above outlook 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.