WB API Digest — November 2025

In the latest edition of our monthly digest, we highlight the new features and updates released in November 2025

Publication date: 03.12.2025

WB API Updates Digest — November 2025

In November 2025, Wildberries released 12 API updates, 7 of which are critical changes with specific deadlines. The main focus of the month is a massive optimization of FBS orders and supplies: new method versions allow processing up to 100 elements instead of one, significantly speeding up integrations.

Disclaimer: Practical recommendations in this digest are based on integration experience and may vary depending on your specific implementation.

Ready-to-use Postman Collection: For convenient testing and API work, 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 right away.

Critical Changes with Deadlines

Deadline	What's Changing	Required Actions
December 8	Disabling complaint methods for feedbacks	Switch to personal account
December 11	Removal of `valuation` field in unanswered feedbacks	Remove field processing from code
December 17	Disabling the old method for getting supply orders	Migrate to new method for getting order IDs
December 18	Disabling the old version of adding orders to supply	Migrate to batch version (up to 100 IDs)
December 24	Disabling the old version of FBS metadata method	Migrate to batch version (up to 100 IDs)

FBS Orders and Supplies

November became the month of massive FBS method optimization. Wildberries is consistently transitioning the API to batch processing, which is critical for sellers with high order volumes.

New Version of the FBS Metadata Method

A new version of the Get Assembly Orders Metadata method has been added. The key change — you can now pass up to 100 assembly order IDs in a single request instead of one.

Migration Deadline: December 24, 2025 — the current version will be disabled.

Benefits

For Business:

Faster order processing during peak periods — one request instead of 100
Reduced risk of exceeding API limits during mass processing
More stable integrations during high-load periods

For Developers:

Simplified batch order processing logic
Reduced infrastructure load due to fewer HTTP requests
Opportunity to optimize parallel processing

Migration

Replace calls to the old endpoint GET /api/v3/orders/{orderId}/meta with the new POST /api/marketplace/v3/orders/meta with an array of IDs in the request body. We recommend grouping orders in batches of 50-100 for optimal performance.

New Version of the Add Orders to Supply Method

The Add Assembly Orders to the Supply method received a similar update. You can now add up to 100 assembly orders to a supply in a single request.

Migration Deadline: December 18, 2025.

Practical Application

This change is especially important for sellers creating large supplies. Previously, adding 500 orders to a supply required 500 separate API calls. Now it can be done in 5 requests.

Implementation Recommendations:

Implement order buffering before adding to supply
Add partial error handling — in batch requests, some orders may be added successfully while others fail
Log results of each batch request for debugging

New Method for Getting Supply Assembly Order IDs

A new method Get IDs of the Supply Assembly Orders has been added, which returns only order identifiers without full data.

The old method Get the Supply Orders will be disabled on December 17, 2025.

Why This Matters

The new approach optimizes work with large supplies:

Get the list of IDs via the new lightweight method
Request details only for needed orders via a separate method

This reduces the volume of transmitted data and speeds up operations, especially when you only need information about some orders in the supply.

New optionalMeta Field in Assembly Orders

The optionalMeta field has been added to the response of the Get New Assembly Orders method — a list of optional metadata.

Difference Between requiredMeta and optionalMeta

requiredMeta — metadata without which the assembly order cannot be transferred to delivery
optionalMeta — metadata that can be omitted for delivery transfer, but may be required when a customer returns a product

Important: If your product requires mandatory marking, you must specify all metadata whether it was received in requiredMeta or optionalMeta field (see 4.6 of the Offer).

Recommendation: Add all metadata from both fields to assembly orders — this will reduce the risk of issues with returns.

Increased Limit for Data Matrix Codes

The maximum number of elements in the sgtins array has been increased when adding Data Matrix codes to an FBS assembly order. You can now pass up to 100 codes in a single request.

This simplifies work with products requiring multiple marking codes (e.g., sets or bundles).

Marketing and Promotions

Limit in Campaign Statistics Method

Starting November 27, the Campaign Statistics method request can contain a maximum of 50 campaign IDs in the ids array.

What to Do

If your integration requests statistics for more than 50 campaigns simultaneously, split requests into batches. Add pagination with grouping by 50 campaigns and aggregate results on your side.

Removal of Deprecated Campaign Types

Data for campaigns with deprecated types has been removed from the responses of Campaigns Lists and Campaigns Information methods:

4 — in catalog
5 — in product card
6 — in search
7 — in recommendations on the main page

It has been unavailable to create campaigns of these types since March 2024. If your system still processes these types, you can safely remove the corresponding logic.

Reorganization of Search Clusters Methods

Methods for working with search clusters have been moved to a separate subsection in the documentation. Functionality remains unchanged — this is purely an organizational improvement for easier navigation.

Customer Communication

Temporary Disabling of Complaint Methods for Feedbacks

On December 8, complaint management methods will be disabled:

What to Do

Wildberries is temporarily removing this functionality from the API to improve data accuracy. Complaint management remains available through the seller's personal account.

Recommendations:

If you have automated complaint submission via API, switch this process to manual mode through your personal account
WB promises to announce when complaint management via API is available again
Follow Release Notes for updates on functionality restoration

Removal of valuation Field in Unanswered Feedbacks

On December 11, the valuation field (average rating of all feedbacks) will be removed from the Unanswered Feedbacks method response.

If your system uses this field, remove its processing from your code or obtain the average rating through another method.

Disabling Response Templates Methods

Reminder about the October deadline: starting November 19, response template methods have been disabled:

Get response templates
Create a template
Edit template
Delete the template

If you haven't migrated yet — implement template storage in your own system and use direct response submission methods.

Documents and Analytics

New Field in Details for the Realization Reports

The payment_schedule field has been added to details for the realization reports — one-time instant money withdrawal rate.

The field is used to display the commission for the Withdraw Now service, which allows receiving payment earlier than the standard term.

Practical Application

If you use the early withdrawal service, you can now automatically account for this service's commission in financial reporting. Add processing of the new field to your management report generation logic.