Publication date: 06.05.2025
The developer portal now features two new functions: Personal Account and API Status
We spoke with Desport to find out how an enterprise-level seller increased sales and reduced costs through integration with WB API.
Discover a ready-made solution built on WB API for integrating your store with 1C.
We’re actively expanding our Case Studies section. Soon you’ll see new automation scenarios, additional examples of exports via Google Sheets, and even more real-life stories from sellers.
Our documentation just got even easier to use. In April, we released the first guide on managing products via WB API:
Look for guides right in the docs — in sections marked with the «📖» icon.
The POST /content/v2/get/cards/list
method now returns a new field, needKiz
, which can be either true
or false
. This lets you know whether the «Chestny Znak» marking code is required for a product, making it easier to monitor which items need mandatory labeling under Russian law.
In response to your feedback, we’ve detailed the WB API rate limits and added direct links to this information in every method description. Now the docs clearly explain how limits work, how to avoid blocks, and what to do if you exceed them.
We’re continuously improving the documentation based on your experience and suggestions. If you have ideas, requests, or questions — please share them. Every suggestion helps make WB API more user-friendly and clear.
As of April 30, you can no longer delete or update stock levels if the warehouse is currently being updated or deleted. Requests will return a 409
error with the message «The store is processing.» Wait a few seconds and retry.
Additionally, from May 26, 2025, updating stock for small-sized items (cargoType: 1
) in FBS model is limited if the virtual warehouse is meant for large-sized goods. Such items can only be deleted.
These changes aim to optimize processing and logistics. We recommend moving standard goods to the appropriate virtual warehouses in advance to avoid disruptions.
cargoType: 1
) to suitable warehouses.WB API continues to retire outdated methods. On April 29, we disabled the «Statistics of Product Card Groups by Period» method — /api/v2/nm-report/grouped
. Please use the current «Sales Funnel» endpoints instead.
As of April 28, the «Sales by Realization Report» method now includes two new fields:
wibes_wb_discount_percent
— Wibes discount percentage.installment_cofinancing_amount
— co-financing discount amount.Now you can immediately get data on our promotional offers and assess the impact of both Wibes discounts and co-financing on your sales metrics.
As of April 29, the orderType
field was removed from the responses of both /api/v1/supplier/orders
and /api/v1/supplier/sales
. Order type data (including returns) is no longer available in these methods. We recommend using srid
and specific response fields (e.g., isRealization
, isCancel
, paymentSaleAmount
, forPay
, etc.) instead.
April 2025 was a milestone month for WB API development: the platform took several steps toward being even more convenient and business- and developer-oriented.
All of this confirms the main trend: WB API evolves together with its users. We listen, adapt, add what’s important, and remove what’s unnecessary. Thank you for testing, integrating, and automating — you make our API even better.