WB API Digest — February 2026

In the latest edition of our monthly digest, we highlight the new features and updates released in February 2026

2

Publication date: 03.03.2026

content

WB API Digest — February 2026

In February 2026, Wildberries released 9 API updates. The month focused on expanding seller capabilities: new batch methods for In-Store Pickup, stickers for DBS, a CSV inventory history report, and multi-currency support in analytics.

Disclaimer: Practical recommendations in this digest may vary depending on the specifics of your implementation.

Ready-made Postman collection: For convenient testing and working with the API, we've prepared a collection of methods from this digest. Import it into your Postman, set your API key in the api_key variable, and start working with the methods right away.

Technical support is responsible for how the API itself works.

Discuss the Postman interface and collections in the Community.

At a Glance

WhatSummary
⚠️ Response 204 in reportsEmpty reports will return 204 instead of empty [] — March 11
🆕 In-Store Pickup batch methodsBulk status changes for assembly orders
🆕 DBS stickersPDF stickers for DBS orders with pickup point delivery
🆕 CSV inventory history reportType STOCK_HISTORY_DAILY_CSV — no Jam subscription required
🆕 Search cluster methodsCluster lists and daily statistics
🔄 Multi-currency in analyticscurrency field in all Analytics reports
🔄 Order status in feedbacksorderStatus field in feedback methods
🔄 WB API token typesAccess control: personal, service, basic
🔄 Promotion method relocationProduct card editing method → Campaign Management

Critical Changes with Deadlines

DeadlineWhat's ChangingWhat to Do
March 11Report generation methods will return 204 instead of 200 with [] when there's no dataAdd 204 No Content handling in your client

Reports

New 204 Response for Empty Reports

Starting March 11, three report generation methods will change behavior: if there's no data for the request, they'll return 204 No Content instead of 200 with an empty array [].

Affected reports:

If your code treats an empty array as "no data" — everything works fine. But if your client expects 200 and breaks on 204, you need to add handling for this status before March 11. A common mistake: trying to parse JSON from a 204 response body, which has no body.

DBS Orders

Stickers for DBS Assembly Orders with Pickup Point Delivery

A new method for getting stickers has been added — POST /api/marketplace/v3/dbs/orders/stickers — for DBS orders with pickup point delivery. The method returns PDF stickers for orders in confirm (on assembly) and deliver (in delivery) statuses.

New fields have also been added to DBS assembly order methods:

  • The new assembly orders method (GET /api/v3/dbs/orders/new) now includes wbStickerId — the sticker identifier.
  • The completed assembly orders method (GET /api/v3/dbs/orders) now includes wbStickerId and scanPrice — the pickup point acceptance price in kopecks.

For business:

  • Automatic sticker printing for DBS orders delivered to pickup points — no need to generate them manually
  • Acceptance cost tracking via the scanPrice field

For developers:

  • Sticker integration follows the same workflow as FBS — send an array of order IDs, get a PDF back
  • scanPrice comes in kopecks — divide by 100 for display

In-Store Pickup

Batch Methods for Bulk Assembly Order Management

Four new methods have been added for batch processing of In-Store Pickup assembly orders. Previously, each order's status had to be changed individually; now you can send multiple IDs in a single request:

These methods cover the entire lifecycle of an In-Store Pickup assembly order: from confirming assembly to buyer receipt or rejection. If you run a store with high pickup order volume, batch processing will significantly reduce the number of API requests.

Marketing and Promotion

New Methods and Extended Search Cluster Statistics

Two new methods for working with search clusters in advertising campaigns have been added:

Additionally, the existing search cluster statistics method (POST /adv/v0/normquery/stats) now includes shks (number of ordered items) and spend (promotion costs for a specific cluster). You can now evaluate each cluster's effectiveness not only by clicks but also by orders and spend — and with the new v1 method, do it on a daily basis.

Product Card Editing Method Relocation

The product card list editing method (PATCH /adv/v0/auction/nms) has been moved to the Campaign Management subsection. The endpoint remains the same — only its location in the documentation has changed.

Analytics

Multi-Currency Support in Reports

Wildberries is systematically transitioning analytics to multi-currency support. In February, the currency field — report currency — was added to the following methods:

Starting February 11, the currency field has been added to all remaining reports in the Analytics and Data section, and monetary values are now returned in the seller's country of registration currency. If your code assumed all amounts were in rubles — check the currency field and add conversion logic as needed.

New CSV Inventory History Report

A new report type STOCK_HISTORY_DAILY_CSV has been added to Seller Analytics CSV. To create the report, send a request to the report creation endpoint with reportType: "STOCK_HISTORY_DAILY_CSV", then download the finished file.

The report shows inventory data as of 23:59 each day. It's available without a Jam subscription — one of the few CSV reports that doesn't require one.

Customer Communication

Order Status in Feedbacks

The orderStatus field — the status of the order associated with the feedback — has been added to feedback methods:

Possible values: buyout (purchased), rejected (declined), returned (returned), notSpecified (no status assigned). You can now filter feedbacks by order completion type — for example, separately analyze feedbacks from buyers who returned the item to understand return reasons.

General

Access Control by Token Types

Wildberries is introducing access differentiation for API methods by token type:

  • Personal — full access, including user management
  • Service — including OAuth authorization
  • Basic — limited set of methods

The Seller User Management category is already restricted to the personal token only. In the future, this differentiation will extend to new methods. If you use service or basic tokens — verify that you won't lose access to the methods you need.

Migration Checklist

Before March 11

  • Add 204 response handling in report download methods (Warehouse Inventory, Acceptance Operations, Paid Storage)
  • Add currency field handling in analytics reports — monetary values are already returned in the seller's currency
  • Add orderStatus handling in feedback methods
  • Add wbStickerId and scanPrice handling in DBS assembly order methods
  • Verify the type of token you're using — user management methods are restricted to personal tokens only

Official documentation and resources