Release Notes

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:

• Warehouses Inventory
• Acceptance Expenses
• Paid Storage

Added fields to the description of the getting buyers return applications method:

• origin_id_info — result of IMEI verification for a return via a Wildberries pickup point, which allows for more efficient return application processing for Apple items of the Smartphones subject ("SubjectId":515) with a discounted seller's price of 40,000 rubles and above
• delivery_dt — date and time the buyer received the order

Added the method for getting stickers for DBS assembly orders delivered to pickup points. Use this method to get stickers in PDF format for assembly orders with the confirm — on assembly — and deliver — on delivery — statuses.

To the response of the method for getting a list of new orders added the wbStickerId field — sticker ID.

Added the fields to the response of the method for getting information on completed orders:

• wbStickerId — sticker ID
• scanPrice — acceptance price for orders to a pickup point, in kopecks

Responses of the methods for getting information on completed orders and getting a list of new orders now include:

• pickup point address — in theaddress field
• delivery type dbsPickupPoint — Delivery By Supplier to Pickup Point — in the deliveryType field

Added CSV report of the InventoryHistoryReportRes model. In the report creation request, reportType of this model is STOCK_HISTORY_DAILY_CSV.

Now you can get inventory for any day during the last 3 months. The report shows data on balances as of 23:59.

This report is available without the Jam subscription.

Added new methods for working with lists of In-Store Pickup assembly orders.

You can now pass multiple assembly order IDs in one request:

• to transfer assembly orders to assembly
• to notify that assembly orders are ready for pickup
• to notify that the orders are received
• to notify that the orders are declined
• to get assembly order statuses
• to cancel the assembly orders
• to get assembly orders metadata
• to delete assembly orders metadata
• to add Data Matrix code to assembly orders
• to add UIN to assembly orders
• to add IMEI to assembly orders
• to add GTIN to assembly orders

New methods will replace deprecated methods in sections In-Store Pickup Assembly Orders and In-Store Pickup Metadata.

For more flexible management of access to seller data, we are introducing an update to WB API tokens — now new methods will be available depending on the token type:

• Personal
• Service — including authorization with OAuth
• Basic

Seller User Management method category is already available only with Personal token.

Added a orderStatus field — order status — to the methods:

• Feedbacks List
• Get the Feedback by ID
• List of Archived Feedbacks

Possible field values:

• buyout — bought out
• rejected — rejected
• returned — returned
• notSpecified — status not assigned

Added methods:

• Active and Inactive Search Cluster Lists
• Daily Search Clusters Statistics

To the response of the method for getting search clusters statistics added fields:

• shks — number of ordered products
• spend — product promotion costs in a specific search cluster of the campaign

Moved the method for changing the list of product cards in campaigns to the Campaigns Management subsection.

Added a currency field — report currency — to the methods:

• Sales Funnel
• Stocks Report
• Seller Analytics CSV — for DETAIL_HISTORY_REPORT and GROUPED_HISTORY_REPORT report types

By February 11, we will add the currency field to the reports:

• Search Queries for Your Items
• Seller Analytics CSV — for the remaining report types

Starting from February 11:

• Monetary values in all of the Analytics and Data reports will be returned in the currency of the seller's registration country.
• The value of the currency field will be determined by the country where the seller is registered.

The changes will be rolled out gradually for all sellers by February 16.

Added the method for getting B2B customer information for the DBS model. Now, using the WB API, you can get the B2B buyer data:

• Taxpayer Identification Number (TIN or INN in Russian)
• Code of Reason for Registration (CRR or KPP in Russian)
• Company name

Added the crossBorderType field with information on whether the assembly order is cross-border in the responses of the FBS methods:

• Get New Assembly Orders
• Get Assembly Orders

You can add an assembly order of any type — cross-border or non-cross-border — to an empty supply. After that, the supply acquires the type of the first added assembly order. Supply type will be specified in the crossBorderType field in the responses of the methods:

• Get a Supplies List
• Get Supply Details

Starting from March 2, it will be possible to add to the supply only the assembly orders of one type: cross-border or non-cross-border.

On February 2, we will remove the deprecated statusID field — product status — from the responses of the methods:

• Chat List
• Chat Events

Starting from February 5, images in the photoLinks field will be returned in webp format instead of jpg for the methods:

• Feedbacks List
• Get the Feedback by ID
• List of Archived Feedbacks

Added the fields with information about promo code discounts to details for the realization reports:

• uuid_promocode — promo code ID
• sale_price_promocode_discount_prc — promo code discount, %

The new fields will be displayed in daily reports starting with the report for January 19, and in weekly reports starting with the report for January 19–25.

On February 2, we will remove the deprecated clientID field — buyer ID — from the responses of the methods:

• Chat List
• Chat Events

Now you can specify the custom declaration number in the metadata of FBS and DBS assembly orders.

To check if you can specify the custom declaration number for the assembly order, use the methods for getting a list of new FBS and DBS assembly orders:

• if the value of the requiredMeta response field is customsDeclaration, you can specify the custom declaration number
• if the value of the requiredMeta response field is not customsDeclaration, you can specify the custom declaration number

To specify the custom declaration number, use the new methods:

Add Custom Declaration to the Order — FBS

Add Custom Declaration to the Orders — DBS

To check the specified custom declaration number, use the methods for getting FBS and DBS assembly order metadata. The specified custom declaration number will be displayed in the customsDeclaration field.

To delete the custom declaration number, use the methods for deleting FBS and DBS assembly order metadata.

Added new methods for working with lists of DBS assembly orders.

You can now pass multiple assembly order IDs in one request:

• to get assembly order statuses 
• to cancel the assembly orders 
• to transfer assemly orders to assembly 
• to transfer assembly orders to deliver 
• to notify that the orders are received by buyer 
• to notify that the buyer has declined the orders 
• to get assembly orders metadata 
• to delete assembly orders metadata 
• to add Data Matrix code to assembly orders  
• to add UIN to assembly orders 
• to add IMEI to assembly orders 
• to add GTIN to assembly orders 

New methods will replace deprecated methods in sections DBS Assembly Orders and DBS Metadata.

Added the fields with information about seller loyalty program discounts to details for the realization reports:

• loyalty_id — seller loyalty program discount ID
• loyalty_discount — seller loyalty program discount, %

The new fields will be displayed in daily reports starting with the report for January 12, and in weekly reports starting with the report for January 12–18.

Added the fields with information about seller own promos with additional discounts to the details for the realization reports:

• seller_promo_id — seller own promo ID with additional discount
• seller_promo_discount — additional discount from seller promo, %

The new fields will be displayed in daily reports starting with the report for December 29, and in weekly reports starting with the report for December 29–31.

Added responses with moderation statuses for the Get File from the Message method:

• 202 The file is under moderation
• 451 Moderation failed

Added the new methods for getting reports with underreporting of package dimensions:

• Logistics and Storage Costs Multiplier
• Warehouse Measurements

The deprecated method for getting this data will be disabled on January 27.

As we shift to work with campaigns with custom and standard bids — 9 type, from February 2 we will disable the deprecated methods for standard bid campaigns — 8 type:

• List of Product Cards for Campaign with Standard Bid
• Changing the List of Product Cards in a Campaign with Standard Bid
• Statistics of a Campaign with Standard Bid by Phrase Clusters

The deprecation date for the Setting/Removing Minus-phrases for Campaigns with Standard Bid method changed from January 15 to February 2.

In the response of the Chat List method, we added the lastMessage object with information about the last message in the chat:

• text — message text
• addTimestamp — message time

Added the delivery_method field with information about the sales method and cargo type to the details for the realization reports. Now you can match report items with rates based on the delivery method.

The delivery_method field is only displayed for FBS , FBW, and DBW models.

The new field will de displayed in daily reports starting with the report for December 22, and in weekly reports starting with the report for December 22–28.

Updated the Realization Sales Report method responses. Now, if there is no data, the method returns the 204 No Data response, rather than an empty array [] in the 200 Success response.