WB API Updates Digest for October 2025

In October 2025, Wildberries implemented 12 significant API updates, including 5 critical changes. Main update directions: completion of advertising campaign unification, expansion of analytical capabilities, and optimization of supply and order management.

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

Ready-to-use Postman Collection: For convenient testing and API work, we prepared a collection of methods from this digest. Import it into your Postman and start working with the methods right away.

---

Critical Changes with Deadlines

The table below contains all changes requiring mandatory actions. Pay special attention to dates — some changes have already taken effect.

---

Marketing and Promotion

Completion of Promotion Campaign Unification

WB is completing the advertising campaign unification process started in September 2025. Campaigns with manual and unified bids are now fully merged into one type 9, and the obsolete type 8 is disabled as of October 23.

New Campaign Typology

All new campaigns are created with type 9. The bid type is now determined by a separate field bid_type with two possible values: manual (manual bid) and unified (unified bid).

Updated API Methods

Campaign Creation

The method Create Campaign now creates only type 9 campaigns with mandatory bid_type specification.

Campaign Information

The response of the method Manual Bid Campaign Information now includes the bid_type field:

{ "campaign_id": 12345, "type": 9, "bid_type": "manual", "status": "active" }

Bid Changes

The method is renamed to Change Bids in Campaigns and now requires specifying the placement parameter:

{ "campaign_id": 12345, "placement": "search", "bid": 150 }

The placement parameter accepts the following values: search (in search, for manual bid), recommendations (in recommendations, for manual bid), combined (in search and recommendations, for unified bid).

Product Card Management

The method is renamed to Change Product Card List in Campaigns.

Campaign List

The response of the method Campaign Lists is updated with descriptions of all campaign types and addition of bid_type information for type 9.

Step-by-Step Migration Instructions

If you haven't updated your integration yet, follow these steps.

Step 1. Update Campaign Creation

Make sure you're using the current creation method. Verify that created campaigns have type 9. Always specify bid_type when creating new campaigns.

Step 2. Update Campaign Information Processing

Add reading of the bid_type field from API responses. Update bid type determination logic in your system. Use bid_type instead of type to determine bid management strategy.

Step 3. Update Bid Changes

Add the placement parameter to all bid change requests. For manual bids, specify search or recommendations depending on placement location. For unified bids, use the combined value.

Step 4. Testing

Create test campaigns of both bid types (manual and unified). Check bid changes for different placement values. Ensure correct data display in your dashboards.

Practical Application

Business Benefits

A unified system simplifies management of all campaign types. Ability to quickly switch between strategies without recreating campaigns. Improved flexibility in managing ad placement locations.

Developer Benefits

Simplified codebase due to single campaign type. Bid type management through a separate field makes code more explicit and clear. Improved readability and maintainability of integrations.

---

Search Cluster Management

New methods for managing bids by search clusters have been added for manual bid campaigns. These methods allow setting individual bids for specific search queries, providing more precise control over advertising budget.

New Methods

Search Cluster Bid List

The method returns current bids for all search clusters in the selected campaign. Use it to get a complete picture of bid distribution across queries.

Set Bids for Search Clusters

The method allows setting or changing bids for specific search queries. You can set bids for multiple clusters in one request.

Delete Search Cluster Bids

Deleting individual bids returns clusters to using the campaign's base bid. This is useful for simplifying management of low-performing queries.

Search Cluster Statistics

The method is available for both manual and unified bid campaigns. Returns performance statistics for individual search queries: impressions, clicks, conversions, and costs.

Usage Scenarios

Performance Optimization

Get search cluster statistics for the recent period. Identify high-performing queries with good conversion. Increase bids on effective queries to boost impressions. Decrease or remove bids on ineffective queries.

Seasonal Optimization

Before the season starts, increase bids on seasonal search queries. Monitor performance through statistics during the season. After the season ends, return bids to baseline values.

Competitive Strategy

Identify key competitive search queries in your niche. Set increased bids on these clusters to improve positions. Track position changes and conversions for these queries.

Practical Application

Business Benefits

More precise optimization of advertising budget through query-level management. Ability to focus on high-profit queries. Detailed performance analytics for each query. Quick response to demand changes and competitive situation.

Developer Benefits

Automated bid management based on performance metrics. Integration with analytics and BI systems for comprehensive analysis. Creation of automated rule-based bid management strategies. Ability to A/B test different bid strategies.

Implementation Recommendations

Start with analyzing statistics for the last 30 days to determine current situation. Identify top 20% queries by conversion as priority for bid increases. Gradually increase bids on effective clusters while tracking metric changes. Set up automatic alerts for sharp changes in key cluster performance.

---

Negative Phrase Management

Methods for centralized negative phrase management in manual bid campaigns have been added. Negative phrases help exclude ad displays for non-target queries, thereby reducing costs and improving traffic quality.

New Methods

Campaign Negative Phrase List

The method returns all active negative phrases set in the campaign, with their parameters and match types.

Set and Delete Negative Phrases

A unified method for adding new negative phrases and removing existing ones. Supports bulk updates in one request.

Work Format

When setting negative phrases, you need to specify the phrase text and match type. The method returns an array of all active negative phrases with their parameters.

{ "campaign_id": 12345, "phrases": [ { "phrase": "cheap", "match_type": "exact" }, { "phrase": "china", "match_type": "phrase" } ] }

Two match types are available: exact (exact query match) and phrase (phrase match, including additional words).

Practical Application

Business Benefits

Protection from non-target traffic reduces wasteful advertising spending. Reduced costs for clicks that don't lead to conversions. Improved overall traffic quality to product cards. Increased ROI of advertising campaigns through focus on target audience.

Developer Benefits

Centralized negative phrase management simplifies their maintenance. Ability to bulk update negative phrases in one request. Synchronization of negative phrases between multiple campaigns. Automatic addition of ineffective queries from statistics.

Usage Recommendations

Basic Negative Phrases

Create a list of common non-target words for your category: "china", "cheap", "replica", "fake". Exclude competitor names and brands. Block near-topic traffic not related to your products.

Dynamic Optimization

Analyze cluster statistics weekly for ineffective queries. Add queries with high CTR but zero conversion to negative phrases. Periodically review negative phrases and remove those that gained conversions.

Category Templates

Create ready-made negative phrase sets for different product categories. Apply these templates automatically when creating new campaigns. Regularly update templates based on accumulated data and new trends.

---

Supply and Logistics

Transition to IDs in FBW Supply Methods

WB is optimizing the supply API by replacing text fields with names with numeric identifiers. This change standardizes integrations, simplifies multilingual support, and increases API stability.

Method Changes

New field statusID — numeric supply status identifier — has been added to the responses of Supply List and Supply Details methods.

As of November 3, 2025, the following text fields are removed from API responses: statusName (supply status name), boxTypeName (supply type name), virtualTypeName (virtual supply type name).

Instead of removed fields, use corresponding IDs: statusID (supply status ID), boxTypeID (supply type ID), virtualTypeID (virtual supply type ID).

Value Reference Tables

Supply Statuses (statusID)

Supply Types (boxTypeID)

Virtual Supply Types (virtualTypeID)

Step-by-Step Migration Instructions

Step 1. Update Response Processing Code

Old response format contained text fields:

{ "supply_id": "WB-GI-12345678", "statusName": "Accepted at WB warehouse", "boxTypeName": "Boxes" }

New format uses numeric IDs:

{ "supply_id": "WB-GI-12345678", "statusID": 3, "boxTypeID": 3 }

Step 2. Create Mapping Reference Tables

Create reference tables in your system for mapping IDs to text names. Include reference tables for all three types: supply statuses, supply types, virtual supply types. Use the tables above to populate reference tables.

Step 3. Update User Interface

Replace direct display of text fields with mapping through created reference tables. Add localization of names for different languages if necessary. Ensure all status display locations use the new approach.

Step 4. Testing

Check mapping correctness for all possible ID values. Ensure correct status display in the user interface. Test all supply statuses in the production environment.

Practical Application

Business Benefits

Standardization of supply operations simplifies staff training. Foundation laid for multilingual interface support. More stable integration due to independence from wording changes.

Developer Benefits

Simplified data processing by working with numbers instead of strings. Independence from text wording changes in WB. Flexible localization on the client side. Reduced risk of parsing and string comparison errors.

Implementation Recommendations

Create enums or constants for all possible ID values in your code. Use strongly-typed programming languages for protection from type errors. Add validation of unexpected ID values with logging and notification. Implement fallback logic for handling unknown ID values.

---

Direct PDF Retrieval of Cross-Border Stickers

WB is simplifying the process of obtaining stickers for cross-border shipments. Now you can directly receive PDF files with stickers instead of intermediate links, which speeds up the process and increases reliability.

Method Changes

A new method Get Cross-Border Assembly Task Stickers has been added, which directly returns a PDF file with stickers.

The method for getting links to cross-border assembly task stickers was disabled on October 23, 2025.

On October 21, the field parcelId — tracking number in the sticker for assembly task tracking — was added to the method response. This number must be saved and provided to customers for tracking international shipments.

New Method Format

The request contains an array of order IDs:

{ "order_ids": [123456, 123457, 123458] }

The response includes a PDF file in base64 format and order metadata:

{ "file": "base64_encoded_pdf", "orders": [ { "order_id": 123456, "parcelId": "WB-track-001" }, { "order_id": 123457, "parcelId": "WB-track-002" } ] }

Approach Comparison

Old Approach (before October 23)

The process consisted of several steps: requesting sticker links, following received links, downloading PDF files. Additional complexity due to limited link lifetime.

New Approach (from October 23)

One request immediately returns ready PDF file. No need to process intermediate links. No problems with link expiration. Tracking numbers received together with stickers in one request.

Step-by-Step Migration Instructions

Step 1. Replace Method

Remove usage of old link retrieval method. Implement call to new direct PDF retrieval method. Update response processing for working with base64-encoded content.

Step 2. Update Processing

Accept PDF file in base64 format directly from response. Decode base64 string and save file locally or send to print. Extract array of tracking numbers parcelId from response for each order.

Step 3. Save Tracking Numbers

Create link between order_id and parcelId in your database. Use parcelId for tracking international shipment status. Provide parcelId to customers for self-tracking of parcels.

Step 4. Testing

Check correctness of received PDF file. Ensure readability of QR codes and text on stickers. Test bulk sticker retrieval for multiple orders.

Practical Application

Business Benefits

Acceleration of cross-border shipment preparation by eliminating intermediate steps. Simplified sticker printing process for staff. Reliable receipt of tracking numbers in one request with stickers. Improved quality of international shipment tracking for customers.

Developer Benefits

Simplified sticker retrieval logic by eliminating multi-step process. No need to process intermediate links and timeouts. Automatic linking of orders with tracking numbers in one response. Single point for receiving all necessary information.

Implementation Recommendations

Save received PDF files locally for quick access when needed. Cache order_id ↔ parcelId correspondence in database. Set up automatic sending to print immediately after receiving stickers. Integrate parcelId into your tracking system and customer interface.

---

Working with Products

Non-Liquid Product Flag

A new field isBadTurnover — non-liquid product flag — has been added to pricing methods. This field helps identify products with low turnover in advance and take corrective measures before automatic sale.

Updated Methods

The isBadTurnover field has been added to responses of the following methods: Get Products with Prices, Get Products with Prices by SKUs, Get Product Sizes with Prices.

Field Format

Example response with isBadTurnover field:

{ "nmId": 123456, "price": 1500, "discount": 10, "isBadTurnover": true }

Important feature: the isBadTurnover field is displayed only for products with low stock index. If the field is absent in the response, this means the product is not non-liquid.

Value Interpretation

The value isBadTurnover: true indicates the following risks. Product has low stock index according to WB algorithms. High risk of automatic product inclusion in sale. Need to review purchase and sales strategy for this item. Possibility of temporary price change blocking by the platform.

Practical Application

Business Benefits

Early Warning: Problem product identification occurs before they go on sale. Time available for implementing corrective actions. Ability to prevent forced deep discounts.

Purchase Optimization: Reduction of purchase volumes for positions showing low turnover. Reallocation of purchase budget to more popular products. Analysis of low turnover reasons for assortment adjustment.

Marketing Actions: Strengthening promotion of non-liquid positions through advertising campaigns. Creating attractive product bundles including non-liquids. Conducting special promotions to accelerate problem position sales.

Developer Benefits

Automatic Actions: Automatic increase of advertising bids on non-liquid products by 20-30%. Including products in targeted promotions and special offers. Creating tasks for category managers to review strategy.

Analytics: Creating non-liquid product dashboard with change dynamics. Tracking turnover trends by categories and brands. Forecasting probability of products going on sale. Measuring effectiveness of corrective measures.

Recommended Actions

Urgent Measures (1-3 days)

When detecting isBadTurnover: true flag, immediately check relevance of set product price. Increase advertising budget by 20-30% to boost visibility. Add product to product recommendation block on popular positions. Check quality of description, photos, and product characteristics.

Short-term Measures (week)

Create special promotional campaign or temporary discount on product. Include position in attractive product bundles. Place product information in push notifications and mailings. Analyze competitor prices and offers for this position.

Medium-term Measures (month)

Review overall purchase strategy for this product group. Assess feasibility of keeping position in assortment. Study seasonality and product sales cyclicality over long period. Consider alternative sales channels for this category.

---

Orders and Delivery

Mandatory IMEI for Smartphones

As of November 5, 2025, it became mandatory to specify IMEI for all smartphones (subjectId: 515) in assembly tasks of DBW and DBS models. This requirement is aimed at combating counterfeiting and improving device tracking.

Affected Models and Methods

The requirement applies to two delivery models: DBW (Delivery by Wildberries) and DBS (Delivery by Seller).

Methods for transmitting IMEI: PUT /api/v3/dbw/orders/{orderId}/meta/imei for DBW model and PUT /api/v3/dbs/orders/{orderId}/meta/imei for DBS model.

Critical Consequences

As of November 5, 2025, without specified IMEI it's impossible to move smartphone assembly tasks to delivery status. Orders without IMEI will be automatically canceled by the system. Penalties will be charged for SLA violations (inability to ship). Complete blocking of smartphone shipments may occur until problem resolution.

Implementation Instructions

Technical Requirements

Implement IMEI transmission to API in your order management system. Set up automatic or manual IMEI reading from device packaging. Implement IMEI format validation (exactly 15 digits) before sending. Test the process on test smartphone orders.

Organizational Measures

Train warehouse staff on IMEI handling procedures. Prepare written instructions with examples and common errors. Organize IMEI filling quality control system. Set up monitoring system for smartphone orders without IMEI.

Readiness Check

Create test smartphone order in your system. Send IMEI through corresponding API method. Move order to delivery status. Ensure successful shipment without errors.

IMEI Format Requirements

IMEI must contain exactly 15 digits. Only digits from 0 to 9 are allowed. Spaces, hyphens, and other special characters are not allowed.

Examples of correct and incorrect format:

• Correct: 123456789012345
• Incorrect: 123 456 789 012 345 (contains spaces)
• Incorrect: 12345678901234 (only 14 digits)
• Incorrect: 123-456-789-012-345 (contains hyphens)

Practical Recommendations

Process Automation

Integrate barcode scanners for automatic IMEI reading. Set up automatic sending of scanned IMEI to API without manual input. Implement sending queue with retry attempts in case of temporary API failures.

Control System

Implement daily automatic report on all smartphone orders. Set up alerts for smartphone orders without IMEI older than 2 hours from creation. Create dashboard displaying percentage of orders with correctly specified IMEI.

Backup Procedures

Provide procedure for manual IMEI input in case of scanning equipment failure. Establish IMEI check control points before final shipment. Keep log of problem cases with analysis of causes and elimination measures.

---

Customer Information Clarification

An important clarification regarding empty values of phone fields has been added to the description of the method Customer Information. This helps correctly interpret API responses and properly build new order processing logic.

Updated Fields

The following fields may contain empty strings in API response: replacementPhone (substitute phone for customer contact), phone (main customer phone), additionalPhoneCodes (additional codes for contact), phoneCode (phone region code).

Empty string "" in these fields means that substitute phone numbers or additional codes have not yet been assigned to the customer. This is a temporary state that resolves automatically within a few minutes after order creation.

API Response Example

{ "order_id": 123456, "customer": { "replacementPhone": "", "phone": "", "additionalPhoneCodes": "", "phoneCode": "" }, "status": "new" }

Practical Application

Business Benefits

Correct understanding of order processing status by platform. Proper planning of time for first customer contact. Elimination of errors when attempting to contact customer before contacts are ready.

Implementation Recommendations

Always check for phone numbers before attempting to call customer. Don't process empty strings as system error or API problem. Poll method periodically until valid numbers are received. Set reasonable timeout for number assignment waiting (usually 5-15 minutes). Log cases of prolonged number absence for problem analysis.

---

Documents and Reporting

Daily Sales Report Details

The method Sales Report by Realization received an important update — it now supports retrieval of daily report details. This enables more operational financial accounting and management.

New Request Parameter

To get daily details, use the parameter period=daily in the request:

{ "dateFrom": "2025-10-01", "dateTo": "2025-10-31", "period": "daily" }

Available period parameter values: daily (daily details, new capability), weekly (weekly details).

Response Format

The response contains an array of reports broken down by days:

{ "reports": [ { "date": "2025-10-01", "sales": [ { "nm_id": 123456, "quantity": 5, "revenue": 7500, "commission": 1125 } ], "total_revenue": 7500, "total_commission": 1125 }, { "date": "2025-10-02", "sales": [] } ] }

Practical Application

Business Benefits

Daily Analysis: Tracking sales dynamics by days in near real-time mode. Quick identification of anomalies and non-standard situations in sales. Rapid response to demand changes and market situation.

Financial Planning: Daily accounting of incoming revenue for accurate cash flow. Detailed control of cash movement. Improved forecasting of payments and receipts.

Operational Management: Adjustment of purchase volumes based on current sales data. Quick price and discount management when demand changes. Timely assessment of marketing campaign effectiveness.

Developer Benefits

Reporting Automation: Daily automatic data loading into accounting system. Management report generation without manual labor. Seamless integration with BI systems and dashboards.

Analytics: Building detailed sales dynamics charts with daily breakdown. Comparing current indicators with similar periods from previous years. Identifying seasonality and long-term trends based on daily data.

Usage Recommendations

Request data once a day at 6:00 AM to get complete data for previous day. Additionally perform weekly requests for reconciliation with weekly reports. At end of each month, conduct full reconciliation for financial period closing. Store historical data for building long-term trends and forecasts.

---

New Package Size Understatement Reports

A new method Package Size Understatement has been added to get detailed reports on deductions. These reports help control packaging quality and minimize penalties.

Available Reports

Deductions for Package Size Understatement

The report contains information about all penalties charged for mismatch between declared and actual product dimensions. Includes deduction amounts, measurement dates, and discrepancy details.

Warehouse Measurements

Detailed data on actual dimension measurements conducted at WB warehouses. Allows comparing declared sizes with measured ones and identifying systematic errors.

Report Format

Example data from report:

{ "penalties": [ { "nm_id": 123456, "declared_dimensions": { "length": 30, "width": 20, "height": 10 }, "actual_dimensions": { "length": 35, "width": 25, "height": 12 }, "penalty_amount": 150, "measurement_date": "2025-10-15" } ] }

Reasons for Deductions

Size understatement is recorded in the following cases. Actual dimensions of packaged product exceed those declared in card. Difference between declared and actual dimensions exceeds allowable tolerance. Incorrect or non-standard product packaging increases its dimensions.

Consequences of size understatement include penalty deductions from seller payments. Incorrect calculation of logistics costs affects profitability. Problems arise with placing products at WB warehouse.

Practical Application

Business Benefits

Quality Control: Identifying products with systematic errors in dimension specification. Audit of product packaging processes at your warehouse. Targeted staff training based on specific errors.

Financial Control: Accounting for all deductions in product cost for proper pricing. Analysis of additional expense causes by product categories. Optimization of packaging processes to reduce penalties.

Preventive Measures: Timely correction of dimensions in product cards based on measurements. Changing packaging materials for problem products. Implementation of mandatory dimension control before first shipment.

Developer Benefits

Automation: Daily automatic report loading for operational control. Setting up automatic notifications to managers about new penalties. Integration with quality control system for creating correction tasks.

Analytics: Creating penalty dashboard with breakdown by product categories and suppliers. Tracking deduction quantity trends to assess measure effectiveness. Forming top products with biggest dimension problems.

Penalty Reduction Recommendations

Product Card Accuracy

Always measure products in fully packaged form before entering in card. Account for all protective materials (bubble wrap, foam, cardboard corners). Add 1-2 cm margin per side to account for packaging tolerance.

Process Standardization

Use standard packaging solutions for similar products. Document packaging processes with photo instructions. Regularly train and retrain staff on proper packaging. Implement dimension control system before shipping new positions.

Monitoring System

Conduct weekly check of new penalties in report. Analyze causes of each size understatement case. Immediately take corrective measures on problem positions. Track effectiveness of implemented measures for reducing penalty quantity.

---

Analytics and Data

Sales Funnel v3

WB is releasing a new version of Sales Funnel methods with an expanded set of metrics, improved pagination, and support for analyzing WB Club loyalty program member behavior. This is a significant update requiring migration by December 9, 2025.

New v3 Version Methods

Product Card Statistics for Period

The method returns aggregated data on product cards for selected period with cursor pagination support for working with large data volumes.

Product Card Statistics by Days

The method provides daily breakdown of all metrics for analyzing indicator dynamics over time.

Product Card Group Statistics by Days

The method allows grouping cards by categories and analyzing them with daily statistics, which is convenient for category management.

All v2 version methods will be disabled on December 9, 2025.

Main v3 Version Innovations

Extended Metrics List

New product card performance metrics and more detailed conversion indicators at each sales funnel stage have been added.

WB Club Loyalty Program Metrics

Ability to separately track loyalty program member behavior has appeared. Available metrics: views from WB Club members, cart additions by program members, orders from WB Club members, program member conversion, program member average check.

Improved Pagination

New cursor pagination mechanism implemented in product card statistics for period method. This ensures more stable work with large data volumes and ability to request large date ranges without limitations.

Response Cleanup

Fields with error information removed from successful 200 responses, simplifying data processing.

New addToWishList Field

Tracking of product additions to favorites added. Field present in SalesFunnelProductRes, SalesFunnelGroupRes models and seller analytics report CSV retrieval method.

New Metrics Structure

Basic Card Metrics

{ "nm_id": 123456, "period": { "start": "2025-10-01", "end": "2025-10-31" }, "metrics": { "views": 15000, "addToCart": 450, "orders": 120, "addToWishList": 230 } }

WB Club Member Metrics

{ "wb_club": { "views": 3000, "addToCart": 120, "orders": 35, "conversion_rate": 1.17 } }

Step-by-Step Migration Instructions

By December 9, 2025, you need to complete the following steps.

Step 1. Update Endpoints

Replace v2 with v3 in all sales funnel requests. Old format: /api/v2/sales-funnel/products. New format: /api/v3/sales-funnel/products.

Step 2. Update Pagination Mechanism

Old pagination in v2 used pages:

{ "page": 1, "limit": 100 }

New cursor pagination in v3:

{ "cursor": "eyJwYWdlIjoxfQ==", "limit": 100 }

Step 3. Add New Metrics Processing

Add processing of addToWishList metric to your system for analyzing product interest. If your business uses WB Club program, implement program member metrics processing. Update data storage for saving extended conversion metrics.

Step 4. Update Error Handling Logic

In v3 version, errors are not returned in successful response bodies. Process HTTP statuses to determine request success. Read error information from response body only for 4xx and 5xx statuses.

Step 5. Testing

Request same data through v2 and v3 to compare results. Check cursor pagination correctness on large datasets. Ensure proper processing of all new fields in your system.

Practical Application

Business Benefits

Loyalty Program Analysis: Comparing purchasing behavior of WB Club members and regular buyers. Quantitative assessment of loyalty program effectiveness for your business. Ability to create targeted promotions and offers for program members.

Sales Funnel Optimization: Tracking product additions to favorites as additional interest indicator. Identifying conversion bottlenecks at each funnel stage. Conducting A/B testing of different product card variants.

Strategic Planning: Analyzing long-term trends across different product categories. Identifying seasonality and sales cyclicality by product groups. Improved demand forecasting based on extended metrics.

Developer Benefits

Extended Analytics: Creating detailed dashboards with WB Club member behavior metrics. Cohort analysis of buyers by different segments. Building complete sales funnels accounting for favorite additions.

Performance Optimization: Using cursor pagination for efficient work with large data volumes. Ability to parallel load data for different products. Incremental data updates instead of full reload.

Implementation Recommendations

Start migration early, a month before December 9 deadline, to identify possible problems. Run requests to v2 and v3 in parallel during transition period for data comparison. Set up monitoring and alerts on new metrics for tracking changes. Train analysts and managers to work with new WB Club metrics.

---

Customer Communication

Question Methods Simplification

On October 27, 2025, the unused field size was disabled in responses of the methods Get Question List and Get Question by ID.

Practical Application

If your system used the size field, remove its processing from code. The field is no longer returned in API responses. This change doesn't affect core functionality of working with customer questions.

---

Response Template Methods Disabled

WB is optimizing the customer communication API by disabling obsolete response template management methods. This requires transition to alternative solutions by November 19, 2025.

Disabled Methods

As of November 19, 2025, the following methods will be unavailable: get response templates for questions and reviews, create new response template, edit existing template, delete template from system.

Alternative Solutions

Local Template Storage

Store all response templates in your own management system. Storage options: relational or document-oriented database, CRM system with template functionality, specialized file storage.

Direct Response Sending

Use direct response sending methods without intermediate saving in WB. Available methods: Reply to Question and Reply to Review.

Integration with External Systems

Consider using external solutions for template management. Options: specialized helpdesk systems, CRM with built-in template functionality, customer feedback services.

Step-by-Step Migration Instructions

By November 19, 2025, complete the following actions.

Step 1. Export Existing Templates

Get all current templates through WB API while it's available. Save complete content of each template. Save all metadata: categories, tags, usage statistics.

Step 2. Implement Local Storage

Create table or collection structure for storing templates in your DB. Implement full set of CRUD operations for template management. Add search and filtering functionality for templates by various criteria.

Step 3. Update Response Process

Implement selection of appropriate template from local storage. Add ability to adapt template text before sending. Set up direct response sending through WB API methods.

Step 4. Testing

Check availability of all saved templates in new system. Ensure correct response sending to customers. Test search and template insertion functions.

Recommended Storage Structure

Example template record structure:

{ "template_id": "local_001", "category": "shipping", "title": "Delivery time", "text": "Hello! Usually delivery takes 3-5 days...", "variables": ["shipping_days", "city"], "usage_count": 145, "last_used": "2025-10-30T10:00:00Z" }

Practical Application

Business Benefits

Full control over response template content and structure. Ability to create extended analytics of template usage. Flexible customization of template system for your business specifics. Independence from WB API changes.

Developer Benefits

Maximum flexibility in template management and organization. Ability to version templates and rollback to previous versions. Simple integration with existing systems and processes. Extended functionality: conditional logic, variables, auto-insertion.

Implementation Recommendations

Add multi-level template categorization for convenient navigation. Implement full-text search by content and keywords. Maintain detailed usage statistics for each template for optimization. Set up granular access rights by user roles. Implement system for suggesting new templates from employees.

---

Migration Checklist

Critical Changes

From October 23, 2025

Transition to creating type 9 campaigns with mandatory bid_type specification. Migration to direct PDF cross-border sticker retrieval without intermediate links.

From November 3, 2025

Replace text field processing with numeric IDs in FBW supply methods. Create internal reference tables for mapping IDs to readable names.

From November 5, 2025

Implement mandatory IMEI transmission for all smartphone orders. Set up monitoring and control system for smartphone orders without IMEI.

By November 19, 2025

Export all response templates from WB API before their disabling. Implement local template storage in own system.

By December 9, 2025

Migrate to sales funnel v3 with all new methods. Update pagination logic to cursor model. Add processing of WB Club loyalty program metrics.

Implementation Measures

Use new search cluster bid management methods for precise budget optimization. Set up centralized negative phrase management through updated methods. Implement isBadTurnover field monitoring system for early non-liquid identification. Connect daily sales report details for operational accounting. Set up regular monitoring of package size understatement reports. Process and save tracking numbers parcelId in cross-border stickers. Work with new addToWishList field in sales funnel analytics.

---

Useful Links

Official Documentation and Resources

• Official WB API Documentation
• Release Notes with all updates
• Sandbox for API testing
• WB API Developer Community

Ready-to-use Postman Collection

For your convenience, we prepared a ready-made collection of all methods from this digest. Import the collection into Postman, specify your API key in the api_key variable, and immediately start testing updated methods.

---

Successful integration! Follow monthly WB API update digests and implement all changes timely!