Release Notes

Adjusted the wholesale object description in the requests and responses for the methods:

• List Items — POST /content/v2/cards/upload
• List Items with Merge — POST /content/v2/cards/upload/add
• Listings — POST /content/v2/get/cards/list
• Listings in Trash — POST /content/v2/get/cards/trash

In the previous version of the wholesale object description, it was incorrectly specified that when "enabled":true, the item is intended for wholesale sales.
In the corrected version of the wholesale object description, it is specified that when "enabled":true, the item is intended for any B2B sale, not just wholesale.

Now you can use the WB API to specify documents in the listing:

• Certificate of Conformity
• The Correspondence Declaration
• Certificate of Registration of SGR
• Registration Certificate
• Certificate of Registration of the Republic of Belarus
• Registration of a Pesticide
• Registration of an Agrochemical
• Medicine Registration Certificate

To specify the documents in the listing, use the documents object in the requests for methods :

• List Items — POST /content/v2/cards/upload
• List Items with Merge — POST /content/v2/cards/upload/add
• Update Listings — POST /content/v2/cards/update

To get information about the documents specified in the listing, use the documents object in the responses for the Listings method — POST /content/v2/get/cards/list.

You can now only pass documents in the characteristics array:

• if you have never specified the documents object in your requests
• if you have not specified documents in your personal account in the updated Documents section in listings.

We recommend passing documents only using the documents object, because if you pass documents in the characteristics array, these documents may be processed incorrectly for any listings.

Documents that have already been in listings will be automatically duplicated in the documents object in the responses for the POST /content/v2/get/cards/list method.

We remind you that listings are overwritten during updates. Therefore, in the requests for the POST /content/v2/cards/update method, include those documents that you are not going to update.

Starting from August 15 we are making temporary changes to how WB API works. Some information about WB warehouses will not be available, see more in the news on Sellers Portal.

• The methods of Information for Forming Supplies and Supply Rates are disabled
• Stock Rates returns data:
  • Box Rates — only for warehouses outside the Russian Federation, and also with warehouseName:
    • Свой склад РФ
    • Свой склад СГТ РФ
  • Pallet Rates — only for warehouses outside the Russian Federation
• Return Rates returns data only for warehouses outside the Russian Federation, and also with warehouseName:
  • Свой склад РФ
  • Свой склад СГТ РФ
  • Склад WB РФ
  • Склад WB СГТ РФ
• In the warehouses array of WB Warehouses Inventory Report totals with "warehouseName":"Warehouse WB Rus" and "warehouseName":"Warehouse WB SGT Rus" are returned instead of data for warehouses in the Russian Federation, except those specified in the news separately and Koledino
• In the Paid Storage report and in the Analytics and Data reports with details on WB warehouses, WB warehouse data is returned only in totals by item sizes
• The following constant values are set in report lines:

• The following constant values are set in report lines for WB warehouses:

• The following constant values are set in report lines for shipping warehouses in the Russian Federation:

• In Details for the Sales Reports by Report ID and by Period values of the officeName field for warehouses in the Russian Federation, starting from daily reports for August 13, are reduced to the four specified in the news

We will inform you about further changes later.

The GET /api/advert/v0/bids/recommendations method now returns recommended bids not only for campaigns with the CPM payment type — per impressions, but also for CPC — per clicks.

Starting from August 18, you will only be able to add a customs declaration number to assembly orders with the confirm status.

Also, starting from August 18, sellers from Armenia will be required to specify a customs declaration number for items produced outside the EAEU if an order from Armenia is being delivered to the Russian Federation.

To check whether it is required to add a customs declaration to an assembly order, use the GET /api/v3/orders/new method. The required label identifiers are listed in the requiredMeta field.

To add a customs declaration number to an assembly order, pass it in the request of the PUT /api/marketplace/v3/orders/{orderId}/meta/customs-declaration method in the customsDeclaration parameter.

Without the required customs declaration number, it is impossible to get assembly order stickers using the POST /api/v3/orders/stickers method — if the required customs declaration number is not specified for at least one assembly order, you will receive error 409 CustomsDeclarationIsRequired.

Also, if the required customs declaration number is not added to the assembly order, the supply with this assembly order cannot be transferred to delivery. In the response of the PATCH /api/v3/supplies/{supplyId}/deliver method, you will receive error 409 MetaValidationFail, and the decision field for customsDeclaration will return the required value.

To check whether the required customs declaration number is added to the assembly order before transferring the supply to delivery, use the POST /api/marketplace/v3/orders/meta method. You can transfer a supply to delivery if the decision field for customsDeclaration returns filled or optional statuses.