WB API Digest — March 2026

In March 2026, Wildberries released 12 API updates. The month was focused on improving data quality: metadata checks during FBS delivery, mandatory IMEI for DBS, and new rules for product card merging. Some changes are already in effect, with the nearest deadlines on April 7 and 9. New capabilities include a method for getting WB warehouse inventory with expanded limits, recommended bids for ad campaigns, and DBW buyer information.

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.

At a Glance

Critical Changes with Deadlines

---

FBS Orders

In March, FBS received a series of updates aimed at improving data quality: phased metadata validation during delivery transfer, separation of B2B and B2C orders in supplies, and sticker status tracking for cross-border shipments.

Metadata Validation During Supply Delivery Transfer

Wildberries is introducing phased metadata validation for FBS assembly orders. When transferring a supply to delivery via PATCH /api/v3/supplies/{supplyId}/deliver, metadata correctness is now checked. If data is incorrect or missing, the method will return a 409 error with code MetaValidationFail and details for each assembly order.

Validation is being introduced in three phases:

• March 31 (already active) — IMEI
• April 7 (in 4 days) — UIN
• April 9 (in 6 days) — data matrix codes for B2B orders

The metadata retrieval method POST /api/marketplace/v3/orders/meta has also been updated. The response now includes a metaDetails array that returns validation statuses for each metadata type: filled, required, pending, as well as specific rejection reasons — imeiInvalidFormat, imeiAlreadySold, uinBadStatus, sgtinNotFound, and others. Use this array before transferring a supply to delivery to identify issues in advance and show the seller the exact reason for the block.

The deprecated meta object in this method's response will be removed on April 30. Switch to metaDetails ahead of time.

More details on validation in the help center.

What to Do

1. Before calling PATCH deliver, retrieve metaDetails via POST /api/marketplace/v3/orders/meta
2. Check the decision field of each array element — if the value is not filled or optional, the order will fail validation
3. Replace meta object processing with the metaDetails array before April 30

B2B Sale Indicator for Supplies

The isB2b field — a B2B sale indicator — has been added to the responses of the supply list and supply details methods. The field accepts three values: true (B2B), false (not B2B), and null (no assembly orders added to the supply yet).

A supply inherits the B2B indicator from the first added assembly order. Since March 19, only orders with the same indicator can be added to a single supply — either all B2B or all non-B2B. You can check an assembly order's B2B indicator via the new assembly orders and assembly order details methods.

If your code automatically distributes orders across supplies, add an isB2b check before adding — otherwise you'll get an error when trying to mix B2B and non-B2B orders in one supply.

Cross-Border Sticker Generation Status

Since April 1 (already active), the status field has been added to the response of the POST /api/v3/orders/stickers/cross-border method with values:

• awaitingTrackNumber — sticker not ready, waiting for carrier track number
• ready — sticker ready, PDF available in the file field

Cross-border order stickers may be generated with a delay — the track number arrives from the carrier asynchronously. Repeat the request until you receive the ready status before using data from the file field. Up to 100 assembly orders per request.

---

DBS Orders

Mandatory IMEI for Delivery Transfer

In parallel with FBS metadata validation (see above), DBS has also expanded IMEI requirements. Transferring an assembly order to delivery is now only possible with a mandatory IMEI. The POST /api/marketplace/v3/dbs/orders/status/deliver method will return a 409 error with "detail":"ImeiIsNotFilled" if no IMEI is assigned to the order.

To determine whether IMEI is required for a specific order, check the requiredMeta array in the response of the GET /api/v3/dbs/orders/new method. If the array contains "imei", assign the IMEI via the POST /api/marketplace/v3/dbs/orders/meta/imei method before transferring to delivery. Only one IMEI per order, and only for orders with confirm status.

Identifier validation during shipment now works across both FBS and DBS. If you work with both models, unify your IMEI check in a single flow before calling deliver.

---

Analytics

New Method for WB Warehouse Inventory

A new method POST /api/analytics/v1/stocks-report/wb-warehouses has been added for getting current WB warehouse inventory. Data is updated every 30 minutes — each response row contains data for one product size at one warehouse.

This method replaces the deprecated GET /api/v1/supplier/stocks, which will be disabled on June 23.

Key differences from the old method:

• Row limit — up to 250,000 per response
• Request frequency — once per 20 seconds per account (instead of once per minute)
• Offset pagination — for handling large data volumes
• Deduplication — all inventory for one size at one warehouse is strictly in one row
• Filtering — request data for specific nmIds and chrtIds (up to 1,000 items)
• New fields — warehouse IDs (warehouseId), warehouse names (warehouseName), and shipping regions (regionName)
• Sorting — ascending by WB article values

The method is available with a Personal or Service token for the Analytics category.

For Business

• Accurate inventory monitoring by warehouse and region without manual deduplication
• Filter by specific products — no need to download the entire catalog to check a few SKUs

For Developers

• Offset pagination allows correct processing of catalogs of any size
• One row per size/warehouse simplifies aggregation and reduces processing overhead

What Changes During Migration

If your integration uses the old method, start migrating now — there are still 2.5 months until the June 23 shutdown, but changing the host, method, and token category will require changes at the API client level.

---

Working with Products

New Product Card Merging Rules

Since March 11 (already active), new rules for product card merging apply to the Beauty and Household Chemicals categories. The updated rules clarify which products can be merged into one card, improving catalog quality and ensuring correct display for buyers.

The changes affect three methods:

• Create Product Cards
• Create Product Cards with Merge — up to 29 cards per request
• Update Product Cards — up to 3,000 cards per request

If a card in a request doesn't comply with the new rules, the method will return 400 with an error description in errorText. The vendorCode of non-compliant cards will be listed in the additionalErrors object — allowing you to fix specific items without reviewing the entire request.

If you work with the "Beauty" or "Household Chemicals" categories and create or merge cards via API, add handling for the 400 status code with additionalErrors checking. The rules are already in effect, so existing integrations may start receiving errors without any changes on your side.

---

DBW Orders

Buyer Information

A new method POST /api/marketplace/v3/dbw/orders/client has been added for the DBW model. The method returns buyer data by order ID: name, full name for documents (fullName), primary phone with extension code (phone + phoneCode), backup phone (replacementPhone), and additional contact numbers.

For Business

• Automatic document generation with buyer data without manual requisition requests
• Quick communication with the customer on order questions — all contact data available

For Developers

• CRM and document management integration: fullName suits printed forms, phone + phoneCode for auto-dialing
• Multiple phone support — account for additionalPhones when implementing call logic

---

Marketing and Promotion

Recommended Bids for Campaigns

A new method GET /api/advert/v0/bids/recommendations has been added for getting recommended bids by campaign ID and WB article. The method works only for campaigns with cost-per-impression (CPM) billing.

The response contains two levels of recommendations:

For product cards — three benchmarks in kopecks:

• competitiveBid — average bid of other sellers in the category
• leadersBid — average bid of category leaders
• top2 — bid for reaching the top

For search clusters (normQueries) — recommended bids broken down by reach level:

• Maximum (76–100%) — reachMax
• Medium (61–75%) — reachMedium
• Minimum (50–60%) — reachMin

Each level contains the recommended bid (bidKopecks) and minimum bid (bidKopecksMin).

In practice, this method enables automated bid management: for example, periodically comparing your current campaign bid with competitiveBid and adjusting to a competitive level, or alerting when a bid drops below bidKopecksMin for the target reach. The limit is 5 requests per minute, which is enough for monitoring dozens of campaigns at intervals of a few minutes.

---

FBW Supplies

New Fields for Supply Types

The isBoxOnPallet field — Pallet with Single Items supply type — has been added to the responses of the Acceptance Options, Supplies List, and Supply Details methods. The field is only returned when boxTypeID: 2 (boxes): true means boxes are placed on a pallet individually.

The boxTypeID field — a numeric supply type identifier — has also been added to the Supplies List method:

If your system automatically creates or routes supplies, these fields allow more precise type identification and correct handling of different acceptance formats.

---

General

Seller User Management

Two updates in the User Management section.

First, user management methods are now available for sellers from all countries. Previously, this functionality was limited to specific regions. Through the API you can:

• Create an invitation for a new user with access to the seller profile
• Get the user list — active and invited
• Update access permissions
• Revoke access to the profile

Authorization requires a Personal token with the Users category from the active profile owner.

Second, the list of personal account sections for configuring employee access has been expanded:

• oldAnalyticsReports — Reports
• marketplace — Seller Warehouse

Specify the new sections when creating invitations and updating access permissions. The updated list of available sections can be retrieved via GET /api/v1/users.

TIN in Seller Information

The tin field — Taxpayer Identification Number (INN) — has been added to the response of the GET /api/v1/seller-info method. The method is available with any token category.

The field is useful for automatic requisite verification and integrations with accounting systems where TIN is used as the primary counterparty identifier — for example, in automatic invoice generation or data reconciliation across platforms.

---

Migration Checklist

Already Active

• Handle 409 error for IMEI validation in FBS supplies — check decision in metaDetails before calling deliver
• Handle 409 error (ImeiIsNotFilled) when transferring DBS orders to delivery without IMEI
• Handle 400 error when merging "Beauty" and "Household Chemicals" cards — check additionalErrors
• Account for the status field in FBS cross-border stickers — repeat request until ready

By April 7 (in 4 days)

• Add UIN validation handling when transferring FBS supply to delivery — check decision in metaDetails

By April 9 (in 6 days)

• Add data matrix code validation handling for B2B orders in FBS

By April 30

• Migrate from meta object to metaDetails array in POST /api/marketplace/v3/orders/meta response

By June 23

• Migrate from GET /api/v1/supplier/stocks to POST /api/analytics/v1/stocks-report/wb-warehouses

---

Useful Links

Official Documentation and Resources

• Official WB API Documentation
• Release Notes with All Updates
• API Testing Sandbox
• • WB API Knowledge Base