Publication date: 09.07.2025
In June, the WB API team released a detailed FBS & Click & Collect guide.
The new guide includes:
This new guide makes integration and understanding of FBS simpler, even for those without deep API experience.
Another major addition was the launch of the sandbox for FBS order testing. Developers can now test all methods in a safe environment before integrating them into production workflows.
What you can test in the new sandbox:
Access is provided via a special «Test Environment» token, so you can safely experiment without affecting live data.
Similar to FBS, Wildberries launched a separate sandbox for Click & Collect orders. Before integration, all methods can be verified in a secure environment, reducing risks of errors.
Available for testing:
Dedicated test methods were also added:
These guides and sandboxes enable faster, safer integration of FBS and Click & Collect models into your business workflows.
In June, WB API added an important improvement for DBS orders. A new field — replacementPhone
— is now available in the customer info method. It contains the buyer’s primary contact number, removing the need for extension numbers that often caused confusion.
The old method remains available as a backup, in case the main number is unreachable.
Learn more in the customer info method documentation.
DBS and Click & Collect APIs now include new fields that give sellers better financial insights:
finalPrice
— final product price in sale currency with all discounts × 100convertedFinalPrice
— final product price in seller’s country currency with all discounts × 100Additional for Click & Collect:
convertedPrice
— product price in seller’s currency with all discounts except WB Wallet discount × 100convertedCurrencyCode
— seller’s country currency codeThese fields improve financial tracking, especially for sellers working across countries and currencies.
Updated methods:
A new API method now allows you to retrieve your seller balance — the same figure shown on the main dashboard in Seller Portal. Access is via a dedicated balance method with a «Finance» token.
More details: Release notes and documentation.
Since mid-July, some weekly sales report fields now return percentages instead of fractions, simplifying interpretation:
sale_percent
product_discount_for_report
supplier_promo
ppvz_spp_prc
ppvz_kvw_prc_base
ppvz_kvw_prc
sup_rating_prc_up
Also, the outdated field rid
has been removed.
These changes improve clarity and simplify accounting. Full details are in the financial reports documentation.
API search analytics gained new filters for substituted SKUs, providing more accurate insights:
includeSubstitutedSKUs
— include data for direct substituted SKU queriesincludeSearchTexts
— include data for standard search queriesBoth cannot be false
simultaneously.
New response field:
isSubstitutedSKU
— indicates whether the item was found via substituted SKU.Supported in:
For sellers with the «Advanced» plan, analytics limits were raised:
searchTexts
arrayAccess to search query methods now requires the «Jam» subscription.
Details: official docs.
/storage-coefficient
MethodThe old /storage-coefficient
method (logistics/storage deductions report) was fully disabled on June 23, 2025.
It will be replaced by two new methods covering deductions for underestimated packaging dimensions and warehouse measurements, giving sellers more accurate logistics cost control.
refund
ObjectWe updated the chat events method. Previously, the API returned a refund
object for return requests via chat. This has now been removed, and all chat events are unified under message
.
For handling returns, sellers should now use the dedicated Returns API methods. This clear separation avoids confusion and improves customer support transparency.
Learn more in: Customer chats docs and Customer returns docs.