WB API Digest — April 2025
In the latest edition of our monthly digest, we highlight the new features and updates released in April 2025
Publication date: 06.05.2025
WB API Digest for April 2025
Before moving on to a detailed overview of the API changes, we’d like to share some important news about our portal
Launched the Personal Account and API Status
A personal space for portal users
The developer portal now features two new functions: Personal Account and API Status
What does this mean for users?
- In the Personal Account, you can easily manage your profile, keep track of important events, and always stay up to date with portal changes.
- With API Status, you’ll be able to see the current state of all APIs in real time, learn about scheduled maintenance, and respond quickly to any incidents.
New Case Studies
Desport Case Study (formerly Decathlon)
We spoke with Desport to find out how an enterprise-level seller increased sales and reduced costs through integration with WB API.
Key Results of the Case Study:
- 6× revenue growth in the first year.
- 40% reduction in operational costs.
- Scaled from zero to flagship-store level.
- Expanded reach — 80% of orders came from regions with no prior sales.
UVmarket Case Study
Discover a ready-made solution built on WB API for integrating your store with 1C.
Seller Achievements:
- Desport: from 0 to 1,500 orders per day.
- Maytoni: revenue growth from 0.5 to 12 million RUB per month.
- LMdecor: deliveries increased from 2 to 15 containers per week.
- Liberty Project: expanded from one region to all of Russia.
- Carrot: one employee’s productivity rose to the level of an entire department.
More case studies are on the way
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.
Guides for Working with WB API
Product Management Guide
Our documentation just got even easier to use. In April, we released the first guide on managing products via WB API:
- Walked through business cases so you can use the API more effectively.
- Specified the optimal order for sending requests and provided method recommendations.
- Added clear flowcharts to simplify understanding of the integration.
Look for guides right in the docs — in sections marked with the «📖» icon.
Now that we’ve covered the big news and new tools, let’s dive into a detailed overview of the latest WB API changes for April 2025
WB API Updates
New Field in the «Get Product Cards List» Method
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.
🏷️ Product Cards via Google Sheets: Step-by-Step Guide
Expanded Documentation on Request Limits
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.
New Rules for Managing Seller Warehouse Stock
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.
How to prepare now:
- Verify that your products match the warehouse type.
- Transfer standard goods (
cargoType: 1) to suitable warehouses.
📦 Warehouse Data via Google Sheets: Step-by-Step Guide
Switching to the Current «Sales Funnel» Endpoints
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.
🔄 Sales Funnel via Google Sheets: Step-by-Step Guide
New Fields in the Weekly Sales Report Details
More data for analyzing discount and co-financing programs
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.
🔍 Report Details via Google Sheets: Step-by-Step Guide
Removed the orderType Field from «Orders» and «Sales» Methods
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.
🚚 Orders, Sales, and Returns via Google Sheets: Step-by-Step Guide
Conclusion
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.
Here’s what we’ve seen:
- New fields and updates in key methods, plus the removal of outdated endpoints, so WB API stays current and processes your requests faster.
- New case studies showing how to grow from zero to high performance with WB API.
- Personal Account and API Status with helpful new features.
- Expanded documentation — now you don’t just read about methods; you see clear guides, diagrams, and recommendations.
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.