WooCommerce Scraper API for Product, Price and Review Data
WooCommerce storefronts publish a predictable set of product facts: title, price, variants, stock state, category, SKU, ratings, review count and an image gallery.
This page explains how to collect those public fields through a rendering API that handles JavaScript, proxy rotation and anti-bot, and how to turn the result into structured JSON for catalog, pricing or merchandising work. It also covers the credit math behind each request option so you can estimate cost before you scale.
What you can collect from a WooCommerce storefront page
Each public WooCommerce product page exposes the same core set of fields. A rendering API can return them in one call, so you do not need to maintain a headless browser or a proxy pool yourself.
- Product title
- Price (and pricing tiers where the storefront shows them)
- Variants (size, colour, etc.)
- Stock state (in stock / out of stock / backorder)
- Category
- SKU
- Star rating
- Review count
- Full image gallery
These fields feed three common workflows: a full catalog snapshot per store, a price-change log per SKU across competing shops, and a ratings/review-count feed for merchandising or review mining.
How a request is built
The workflow is a single HTTP call per page. You send the WooCommerce URL to the API; the service renders the page (including JavaScript), rotates proxies, and returns either rendered HTML or structured JSON.
- Create an account to get an API key. A free trial credit allowance is available at signup.
- Install an SDK (Python, Node.js, Go, PHP, Ruby, Java) or use plain cURL.
- Send the target URL with GET or POST. The API renders the page and handles anti-bot.
- Add options only when needed: render_js for JavaScript-heavy pages, stealth_proxy for CAPTCHAs, country_code for geo-targeting, and extract_rules or ai_extract_rules for structured output.
For structured output you have two paths. extract_rules maps CSS selectors (or XPath) to field names and returns parsed JSON. ai_extract_rules takes a natural-language spec and returns structured JSON without selectors. Both are useful; pick based on how stable the storefront markup is.
Field map: which output to reach for
Use this as a quick decision aid before writing a pipeline.
- Need raw HTML for a custom parser? Send the URL with render_js and read the HTML response.
- Need stable fields on a storefront whose markup you control or can inspect? Use extract_rules with CSS selectors mapped to field names.
- Need fields from many different WooCommerce themes without writing selectors per theme? Use ai_extract_rules with a natural-language spec.
- Need a text form for an LLM? Request Markdown output.
- Need a visual check of how a real browser renders the page? Request a full-page screenshot.
A useful rule of thumb: if the storefront theme is fixed and you can inspect it, extract_rules is cheaper and more deterministic. If you are crawling many independent shops, ai_extract_rules saves selector maintenance.
Credit math: what each option costs
Credits are consumed per successful request and the cost depends on the options you enable. The published per-request costs are:
- Base request: 1 credit
- JavaScript rendering enabled: 5 credits
- Premium proxies without JS rendering: 10 credits
- Premium proxies with JS rendering: 25 credits
- Stealth proxy: 75 credits
A worked example: scraping 10,000 product pages with JS rendering enabled costs 50,000 credits. The same 10,000 pages with stealth_proxy cost 750,000 credits. That gap is why you should only enable stealth_proxy on pages that actually challenge you, and keep JS rendering on for pages whose price or stock is loaded client-side.
API credits are valid for one month and do not roll over. Concurrent requests are the number of requests that can be sent at the same time.
Telling failures apart
When a WooCommerce scrape returns something unexpected, the cause usually falls into one of four buckets. Distinguishing them early saves debugging time.
- Blocked page: the response is a challenge page or a CAPTCHA. Try stealth_proxy or a different country_code.
- Empty extraction: the page rendered but your selectors matched nothing. Check the selector against the rendered HTML, not the raw source.
- Missing field: the field exists on some product pages but not others (for example, a product with no reviews). Treat it as optional in your schema.
- Wrong locale or currency: the storefront served a different regional version. Set country_code to match the market you want.
A quick sanity check: request the same URL once with render_js and once without. If the fields differ, the page depends on JavaScript and you should keep rendering on.
Legality and terms of service
Public-facing pages can usually be scraped, but the target site's terms of service govern what is permitted. Before deploying a pipeline:
- Read the storefront's terms of service and robots directives.
- Avoid post-login or account-only content.
- Keep request rates reasonable so you do not degrade the storefront for other users.
- Store only the fields you actually need.
This is general guidance, not legal advice; consult counsel for your jurisdiction and use case.
Plans and concurrency
Plans differ mainly in monthly credit volume and concurrent request limits. Lower tiers include JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots/extraction rules; higher tiers add priority email support, a dedicated account manager and team management. All prices are exclusive of VAT. A free trial credit allowance is available at signup without a card.
See the pricing table below for the exact plan rows, credit volumes and concurrency limits.
| Plan | Price / month | API credits | Concurrent requests | JS rendering | Rotating & premium proxies | Geotargeting | Screenshots & extraction rules | Priority email support | Dedicated account manager | Team management |
|---|---|---|---|---|---|---|---|---|---|---|
| Hobby | $19 | 75,000 | 25 | Included | Included | Included | Included | Not included | Not included | Not included |
| Freelance | $49 | 250,000 | 50 | Included | Included | Included | Included | Not included | Not included | Not included |
| Startup (Recommended) | $99 | 1,000,000 | 100 | Included | Included | Included | Included | Not included | Not included | Not included |
| Business | $249 | 3,000,000 | 200 | Included | Included | Included | Included | Included | Included | Included |
| Business + | $599 | 8,000,000 | 400 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 14 | $999 | 14,000,000 | 500 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 24 | $1,599 | 24,000,000 | 600 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 | 41,000,000 | 700 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 69 | $3,599 | 69,000,000 | 800 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 120 | $5,799 | 120,000,000 | 900 | Included | Included | Included | Included | Included | Included | Included |
All prices are exclusive of VAT. API credits are valid for one month and do not roll over. Requests start at 1 credit each. Plan availability and pricing are a captured reference and should be re-checked against the current pricing page before purchase.
Frequently asked questions
Do I need an account to scrape WooCommerce?
You do not need a separate WooCommerce account. You need an API key from the scraping service. Sign up, get the key and a free trial credit allowance, then send the storefront URL and the service handles rendering and anti-bot.
Is scraping WooCommerce legal?
Public-facing pages can usually be scraped, but the target storefront's terms of service govern what is allowed. Review those terms before deploying, and avoid post-login or account-only content. This is general guidance, not legal advice.
What data can I extract from WooCommerce?
Anything that renders on the public page. In practice that means product title, price, variants, stock state, category, SKU, star rating, review count and the image gallery. Use extract_rules with CSS selectors or ai_extract_rules with a natural-language spec to get structured JSON back.
How do I get structured JSON from WooCommerce?
There are two routes to parsed JSON. With extract_rules you supply CSS (or XPath) selectors and pair each one with the field name you want it stored under. With ai_extract_rules you describe the fields you want in plain language and skip selectors entirely. Either way, the API returns the result as parsed JSON rather than raw markup.
Which programming languages can I use to scrape WooCommerce?
Any language that can send an HTTP request. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too. Use whatever your stack already relies on.
How much does it cost to scrape WooCommerce?
A free trial credit allowance is available at signup without a card. Paid plans start at $19/month. Per-request cost depends on options: 1 credit for a base request, 5 credits with JavaScript rendering, 10 credits for premium proxies without JS rendering, 25 credits for premium proxies with JS rendering, and 75 credits for stealth_proxy. Credits are valid for one month and do not roll over.