Publication date: 05.02.2026
In January 2026, Wildberries released 7 API updates. Key topics: a new method for retrieving B2B buyer data in DBS, cross-border support in FBS assembly orders and supplies, and continued expansion of the sales report with new discount fields.
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.
| What | Summary |
|---|---|
| 🆕 B2B buyer information | New DBS method — TIN, KPP, and organization name |
| 🔄 New FBS assembly orders | crossBorderType field for cross-border |
| 🔄 FBS assembly order information | crossBorderType field for cross-border |
| 🔄 FBS supply list / Supply information | crossBorderType field for cross-border |
| 🔄 Sales report | Loyalty discount and promo code fields |
| 🔄 Feedbacks | Image format webp instead of jpg — February 5 |
| ⚠️ Chat list / Chat events | clientID removal — February 2 |
| ⚠️ Chat list / Chat events | statusID removal — February 10 |
If you missed the December digest, note that several deadlines are still ahead:
| Deadline | What's Changing |
|---|---|
| February 2 | Deprecation of single-bid campaign methods (type 8) — migrate to type 9 |
| February 9 | Barcodes removed from inventory methods — migrate to chrtId |
| March 11 | Deprecation of the "Supplies" method — migrate to "Supply Information" methods |
| Deadline | What's Changing | Required Action |
|---|---|---|
| February 2 | clientID field removal from chat methods | Remove field handling from response parsing |
| February 5 | Image format in feedbacks: webp instead of jpg | Update photoLinks processing |
| February 10 | statusID field removal from chat methods | Remove field handling from response parsing |
A new method for retrieving B2B buyer information has been added for the DBS model. You can now get B2B buyer data via the API: TIN, KPP, and organization name.
The method accepts an array of assembly order IDs and returns buyer details for each one. To determine whether an order is a B2B sale, check the options.isB2b field in the response of the Get new DBS assembly orders method. If isB2b: true — call the new method to get the buyer's details.
For business:
For developers:
crossBorderType Field in Assembly Orders and SuppliesThe crossBorderType field has been added to the responses of four FBS methods, indicating whether an assembly order or supply is cross-border.
The field appears in assembly order methods:
And in supply methods:
How supplies work: you can add any assembly order — cross-border or not — to an empty supply. The supply inherits the type of the first added order, after which only orders of the same type can be added. This behavior is analogous to how a supply inherits its cargo type (cargoType) from the first order.
If you work with cross-border via FBS, use crossBorderType to route orders into separate supplies and correctly handle logistics flows.
The Sales by realization report method continues to expand — two sets of fields were added in January. As a reminder, in December the same method received the delivery_method, seller_promo_id, and seller_promo_discount fields.
The loyalty_id and loyalty_discount fields have been added to the response — they show the ID and percentage of the seller's loyalty discount. More about the loyalty discount mechanics: announcement.
Similarly, uuid_promocode and sale_price_promocode_discount_prc have been added — the promo code ID and its discount percentage. More about promo codes: announcement.
Both updates are available in daily and weekly reports starting from the dates listed above. If you build management reporting based on the API, add processing for the new fields for accurate discount accounting.
Wildberries continues cleaning up deprecated fields in the Chat list and Chat events methods. The clientID field (buyer ID) will be removed on February 2, and the statusID field (product status) on February 10.
Both fields have long been obsolete and were marked as deprecated in the documentation. If your code processes these fields — remove them before the respective deadlines to avoid parsing errors.
Starting February 5, images in the photoLinks field will be returned in webp format instead of jpg for the following methods:
The URL format in the fullSize and miniSize fields will change — file extensions in links will be .webp instead of .jpg. If you save or process feedback photos, make sure your code handles the webp format correctly. Most modern image processing libraries support webp, but if you validate file extensions or MIME types — update those checks.
clientID field handling in chat methodsphotoLinks (webp instead of jpg)chrtId in all inventory methodsstatusID field handling in chat methodscrossBorderType to route cross-border FBS ordersloyalty_id, loyalty_discount, uuid_promocode, and sale_price_promocode_discount_prc to financial reportingOfficial documentation and resources