# Changelog of Wildberries Scraper - Russian Marketplace Product Data (`haketa/wildberries-scraper`) Actor

- **URL**: https://apify.com/haketa/wildberries-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/haketa/wildberries-scraper.md

## Changelog

### 1.0.1 — 2026-11-01

- **Verification run (quality pass):** Ran fresh verification on the Apify platform with both the default datacenter proxy and a **Russian (RU) Residential** proxy, each returning **0 items**. Diagnostics confirmed Wildberries' in-house anti-bot (**wbaas**) now gates the catalog/search API: `search.wb.ru`, `u-search.wb.ru`, `catalog.wb.ru`, and `card.wb.ru` all return a bare `HTTP 403` to plain HTTP requests — from datacenter and non-Russian **and Russian residential** IPs — across API versions (v13/v14/v18/v19) and both Firefox and Chrome TLS fingerprints. The HTML front-end at `www.wildberries.ru` is served behind a JavaScript challenge page (`HTTP 498`). This is a Wildberries-side protection change.
- **Improved diagnostics:** The actor now counts edge-level blocks (HTTP 403/498) and emits an accurate, actionable final status message that distinguishes a wbaas WAF block from a genuinely empty result set, instead of a generic "check proxy or keywords" guess. No change to inputs, output fields, pagination, or the transform logic.
- **Input schema:** Corrected the `proxyConfiguration` help text — a **Russian Residential** proxy is required (datacenter is blocked), replacing the outdated "datacenter works for most runs" note.
- **README refresh:** Rewrote to the current gold standard — added a prominent **Access & reliability** section documenting the wbaas WAF gate and the RU-residential requirement, corrected the zero-results FAQ, grounded the Output field reference and example in the actual record shape emitted by the code, and refreshed the example timestamp. ~2,760 words.
- **No breaking changes:** Input contract and output field names are unchanged. The scraper remains correct for the catalog endpoint; a browser-based (challenge-solving) collector would be required to reliably bypass the current WAF.