April
2026
Changed
Now you can use the WB API to confirm that required labeling code is applied to the product. To do this, pass the true value for the kizMarked parameter in the requests for the methods:
By default, the false value will be passed in the requests of these methods. This means that you do not confirm that the product has required labeling code. In this case, the item that requires labelling code will not pass moderation and will be blocked.
To check, whether labeling code is required for the product, use the POST /content/v2/get/cards/list method, the needKiz response field:
true — labeling code is requiredfalse — labeling code not requiredTo check whether you have confirmed that required labeling code is applied to the product, use the response field kizMarked in the POST /content/v2/get/cards/list and POST /content/v2/get/cards/trash methods.
Changed
Added fields to the response of the method for getting stickers for cross-border assembly orders POST /api/v3/orders/stickers/cross-border. The fields contain data for printing stickers:
partA — the first part of the sticker ID for printing the signaturepartB — the second part of the sticker ID for printing the signaturebarcode — the encoded value of the stickerNew
Added the fields with information about promo items and wholesale discount for businesses to details for the realization reports — GET /api/v5/supplier/reportDetailByPeriod:
article_substitution — promo item article IDsale_price_affiliated_discount_prc — promo item article discount (%)sale_price_wholesale_discount_prc — wholesale discount for businesses (%)Changed
Now you can use the WB API to check the date and time when the product card was added to the drafts. To do this, we added the updatedAt field for each data batch to the response of the POST /content/v2/cards/error/list method. The field contains the date and time when the package was created or edited.
New
Added the GET /api/common/v1/subscriptions method, which allows you to get detailed information about Jam subscription:
The method is available by Service token of any category.
Changed
Now, statistics in the POST /adv/v0/normquery/stats and POST /adv/v1/normquery/stats methods is available for campaigns with the cpc payment type — pay-per-click.
For these campaigns, you can get all data except:
viewsctrcpmNew
Added the GET /api/common/v1/rating method, which allows you to get the seller user rating and feedbacks count.
The method is available by Service token of the Feedbacks and Questions category.
March
2026
Changed
Added validation for FBS assembly order metadata. Now, if the metadata is specified incorrectly, you will receive a 409 error when moving the supply to the delivery using the PATCH /supplies/{supply}/deliver method. The error will indicate which assembly order metadata failed validation, along with their statuses.
Starting March 31, we will begin validating IMEI. Starting April 7 — UIN, and starting April 9 — data matrix codes for B2B orders.
You can learn more about metadata validation in the help center.
Also updated the response of the method for getting metadata POST /api/marketplace/v3/orders/meta:
metaDetails array. It returns the validation statuses of the assembly order metadata. We recommend getting the metaDetails array before moving the supply to the delivery.meta object.Changed
Expanded the list of personal account sections for which user access can be configured:
oldAnalyticsReports — Reportsmarketplace — Seller WarehouseSpecify the new sections in the method requests:
You can get the updated sections list in the response of the GET /api/v1/users method.
New
On April 1, we will add the status field to the response of the method for getting stickers for assembly orders POST /api/v3/orders/stickers/cross-border. The new field will allow you to track the sticker generation status:
awaitingTrackNumber — the sticker is not ready. Waiting for a carrier's track number.ready — the sticker is readyStickers may be generated with a delay. Repeat the request until you receive the ready status.
New
Added method for getting current WB warehouses inventory — POST /api/analytics/v1/stocks-report/wb-warehouses.
In this method we:
The method is available by Personal or Service token for the Analytics category.
The current method GET /api/v1/supplier/stocks will be disabled on June 23.
New
Added the tin field — Taxpayer identification number of the partner (INN in Russian) — to the response of the seller information method GET /api/v1/seller-info method.
Changed
The Seller User Management methods are available for all sellers countries now. Use these methods to:
You can manage user access only with a token from the active owner of the seller account.
To authorize, use a Personal token with the Users category.
New
Orders DBS changes
Now you can transfer an assembly order to delivery only if the required IMEI is specified.
If the required IMEI is not specified for an assembly order, the method POST /api/marketplace/v3/dbs/orders/status/deliver will return an error with status code 409 and "detail":"ImeiIsNotFilled".
Check the assembly order metadata in the requiredMeta array in the response of the method GET /api/v3/dbs/orders/new.
New
Added the isBoxOnPallet field — Pallet with Single Items supply type — to the responses of the methods:
Added the boxTypeID — supply type ID — to the Supplies List method response.
New
Added a method for getting recommended bids. Use this method to get competitive and leadership bids for items and search clusters by campaign ID and WB article.
New
Added a method for getting buyer information for DBW model. Use it to get buyers data by their order ID.
Changed
Starting from March 11, new rules for item merging will apply for the Beauty and Household Chemicals categories.
The changes will affect the methods:
If а card in a request does not comply with the new rules, the methods will return the 400 status code response and the corresponding values of the errorText field. The vendorCode of items that do not comply with the rules will be listed in the additionalErrors object.
New
Added the indicator of B2B sale for FBS supplies — the isB2b field — to responses of the methods:
You can add any assembly order to an empty supply. After that, the supply acquires the B2B indicator of the added assembly order. The B2B indicator of the supply will be specified in the isB2b field in the responses of the methods for getting a supplies list and getting supply details.
To check the indicator of a B2B sale of an assembly order, use the methods for getting new assembly orders and getting assembly orders.
Starting from March 19, it will be possible to add to the supply only the assembly orders with the same B2B indicator value: either B2B or non-B2B.
February
2026
Changed
Starting from March 11, if there is no data, the methods for getting reports on generation task will return the response 204 No data instead of an empty array [] in the response 200 Success.
List of reports on generation task: