Upgrades, Migration & Future Work

Upgrades made to existing endpoints, their newer versions and newly introduced endpoints are recorded here. It summarizes the impacts of the changes and informs about recommended timelines for migration.

18th of July, 2024

Introduction of Retrieve Stock Levels Endpoint

• v4 Retrieve Stock Levels endpoint is added to enable checking stock availability levels.

Retailers are now able to query the number of units available of SKUs per connection. This endpoint can be used to get entire availability information over all connections, products and SKUs or may be used in stricter queries with the related identifiers passed as body parameters.

One important behavior to mention here is that, to reduce the overhead, successive calls could be made with setting onlyChanges parameter true in the calls. In this case, only the changes in levels made since the last call is going to be included in the response.

More information could be found in the API Reference page here.

Introduction of v3 of Retrieve Prices Endpoint and Improvements on v2 of Retrieve Prices Endpoint

This set of changes are related to the endpoints listed below.

• v2 Retrieve Prices (Improved)
• v3 Retrieve Prices (Added)

It is strongly recommended for partners that are already integrated with v2 to upgrade to v3 as soon as possible. In the meantime, slight improvements have recently been added to v2 for better usability.

The Impact

• v3 Retrieve Prices
  • The response is now grouped firstly by SKUs, not regions as in v2.
  • productTitle is added. Products were only described by their GUIDs or SKUs in v2.
  • prices now includes promotionDetails. Promotion information had to be retrieved from separate endpoints and the responsibility was on to the retailers to find the correct promotion applied to the products, if any. In accordance with the feedback, v3 now handles all the promotion info, their precedence rules, etc. internally and returns only the relevant applied promotion information in full for the queried SKUs.
• v2 Retrieve Prices

There are minor additions made to the existing endpoint. It still groups the response by regions first so that its compatibility is intact but now additionally has regionCountries and salesCountries objects nested in the response that could be utilized to a get a complete picture of availability for the SKUs in the response. regionCountries involve activation enabled countries and salesCountries should reflect it as well.