Release Notes

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 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.

Starting March 11, we will disable the deprecated method for getting the Supplies report.

Use the Supplies Information methods to get the supply data.

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

• 202 The file is under moderation
• 451 Moderation failed

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.

Added the method for getting the Substitution and Incorrect Attachments report.

The deprecated methods for getting this data will be disabled on January 20:

• Substitutions
• Characteristics Change

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.

To the Get New Assembly Orders method response added a new sellerDate field with recommended delivery date for over dimensional products to the sorting center or warehouse.

The sellerDate field is only displayed for assembly orders with over dimensional products ODC, cargoType: 2.

Delivery over dimensional products to the warehouse on the recommended date facilitates acceptance and timely shipment to buyers. If oversized products are delivered to the warehouse earlier, the seller pays for storage until the recommended date. If items are delivered after the recommended date, a higher storage rate applies.

Now you can use WB API to create and manage campaigns with cpc payment type — cost per click.

Added new versions of the methods:

• Campaign Information
• Minimum Bids for Product Cards
• Changing Campaigns Bids

Added the payment_type parameter — campaign payment type — to the following methods:

• Create Campaign
• Subjects for Campaigns

In the new versions of the methods, bids are displayed and passed in kopecks, not rubles. Previous versions of the methods will continue to support bids in rubles and will be available until February 2:

• Campaign Information
• Minimum Bids for Product Cards
• Changing Campaigns Bids

On February 2 we will also disable the deprecated versions of the methods

• Custom Bid Campaigns Information
• Changing Bids
• Promotional Configuration Values
• Setting/Removing Minus Phrases from Search