Wildberries will retire its Sales by Regions API on November 3: a migration checklist
Wildberries announced that GET /api/v1/analytics/region-sale will be disabled on November 3, 2026. It directs developers to the Order Feed report and its migration instructions for regional sales statistics.
If regional sales feed a daily dashboard, identify its source now. Once the old request stops updating, yesterday's numbers can still look plausible. That is risky when they drive advertising, replenishment or inventory decisions.
Four checks before the cutoff
- Find every use of
region-sale: API integrations, BI dashboards, CSV exports, spreadsheets and alert rules. - Map each field and its meaning against the official Order Feed instructions. Similar column names do not guarantee identical counting rules.
- Compare both sources over an overlapping period available to your account: order counts, amounts, regions, returns and refresh lag. Investigate differences before switching your primary report.
- Record the cutover date and keep a historical snapshot. If the new source fails, display its last successful refresh time rather than converting missing data to zero.
This primarily concerns sellers and teams using WB API or third-party analytics; it is not an action required of every seller. It is also separate from the five comparative CSV metrics change: that change removed fields from an export, whereas this one retires a specific API endpoint.
ProfitVena analysis depends on connected sources and available data. If your workflow relies on WB regional metrics, verify the source and freshness of each measure. ProfitVena is part of Wicsora. We make no claim that a particular connector has already migrated without checking its live state.
Source: official WB API notice, checked October 13, 2026. Review the current Wildberries API documentation before changing an integration.
