Wildberries Search & Product Scraper
Pricing
from $0.10 / 1,000 listing rows
Wildberries Search & Product Scraper
Collect Wildberries search results and product data by query or article number. Get prices, sellers, ratings and photo counts; full-card modes add gallery URLs or downloaded photos.
Pricing
from $0.10 / 1,000 listing rows
Rating
0.0
(0)
Developer
Aleksandr Karavaev
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
7 hours ago
Last modified
Categories
Share
Collect public Wildberries search results, look up products by article number, or retrieve product cards and gallery photos. The Actor starts a browser session, then collects the requested data over HTTP. It returns one Dataset row per unique nmId. It does not detect duplicate listings or compare images.
Choose a mode
| Mode | Input | Dataset output | Opens product pages? |
|---|---|---|---|
search_only | 1–5 search phrases | Search-result rows, including article number, available seller and price fields, pics, rating, feedback count and search position | No, after session startup |
lookup_only | Up to 200 article numbers or canonical product URLs | The same listing-format rows for articles found by Wildberries | No, after session startup |
products | Up to 200 article numbers or canonical product URLs | Product-card fields and gallery image URLs or downloaded files | Yes |
search | 1–5 search phrases | Product-card rows for results found in search | Yes |
search_only and lookup_only are the faster, lower-cost ways to collect listing data. They report the number of photos in pics when Wildberries provides it, but do not return photo URLs or image files. Use products or search for gallery images. Some fields depend on the data Wildberries supplies at collection time.
Search-result rows
{"mode": "search_only","queries": ["наматрасник 140х200"],"maxPagesPerQuery": 1,"maxItems": 20,"timeoutSeconds": 180}
maxItems applies separately to each query in search_only. Each query can use up to two search pages. When the same product appears in several queries, it is returned once with all accepted query/page/position references.
Look up article numbers
{"mode": "lookup_only","products": [192045310, "https://www.wildberries.ru/catalog/313247303/detail.aspx"],"maxItems": 10,"timeoutSeconds": 180}
Missing articles are reported as product_not_found in the MANIFEST record. If all requested articles are missing and no technical error occurs, the run succeeds with MANIFEST.status: "partial", an empty Dataset and exit code 0. Enter article numbers in products, rather than as search phrases.
Product cards and photos
{"mode": "products","products": [192045310],"imageMode": "download","maxImagesPerProduct": 3,"timeoutSeconds": 180}
imageMode: "urls" returns observed gallery URLs without saving image files. imageMode: "download" saves up to six images per product in the run's key-value store and returns their URLs, MIME type, dimensions, byte count and SHA-256. Large full-card batches may reach the run deadline before collecting every requested product; maxItems is a limit, not a throughput guarantee.
Read the results
Dataset rows from search_only and lookup_only use schema wb-search-row-v1. Product-card rows use wb-products-v1. Both include nmId, canonical product URL, collection time and provenance. Listing rows can include name, brand, seller, stock, sizes, pics, matchId, subjectId, reviewRating and feedbacks. pics: 0 means Wildberries reported zero photos; null means it did not provide the field. Full-card rows can include descriptions, attributes, variants, price fields and an images array.
Price values are the original integers supplied by Wildberries, with their source field and units identified in the row. They are not a verified final RUB checkout price or a personal discount. Missing optional data remains null; availability and prices can change after collection.
The Actor's Output tab links to the Dataset and to MANIFEST in the default key-value store. Check MANIFEST.status, counts, errors, reachedLimits and, for search_only, coverage.perQuery. A platform run can finish successfully while a collection is partial. Rows already produced remain in the Dataset.
Pricing and spending limits
The Actor uses pay per event: $0.0001 per listing row (search_only or lookup_only), $0.0035 per product-card row (products or search), and $0.00625 per allocated GiB when a run starts. At the default 2 GiB, the start charge is $0.0125. For example, one listing row costs $0.0126 and 100 listing rows cost $0.0225 at 2 GiB. Platform usage is included in these prices; there is no separate charge for writing a Dataset item. Apify displays the applicable price and any Store discount before a run.
Set a maximum cost per run in Apify to bound event charges; the minimum accepted cap is $0.02. When that cap is reached, the Actor stops before collecting another product. Results already saved remain available and MANIFEST reports charge_limit and partial if only part of the requested batch was collected. The start charge applies even when no products are found. A larger memory setting increases the start charge and may leave fewer results within a small cap.
Limits and support
- The supported region is
RU-MOW(Moscow destination, RUB search context). Other regions and proxy settings are not supported in this version. maxItemsis at most 200;maxPagesPerQueryis at most 2; collection time is at most 600 seconds. The Actor rejects unsupported fields and malformed product URLs before starting the browser.- Browser access or Wildberries responses may change, and a request can return fewer items than expected. Review the manifest before relying on a batch.
- Use the Issues tab on this Actor's Store page to report a reproducible problem. Include the run ID, input mode and affected
nmId; do not post credentials or session cookies.
This independent Actor is not affiliated with or endorsed by Wildberries. Users are responsible for their use of the collected public data.