eCommerce Product Data Scraping API
eCommerce product pages are rarely simple HTML.
They load prices, stock states and galleries through JavaScript and often sit behind bot-detection layers. This page explains how a managed scraping API can return that data as rendered HTML or structured JSON, what product fields are typically available, and how request options affect credit usage.
What the API handles for you
Instead of maintaining a fleet of headless browsers and a rotating proxy pool, you send a URL to the API. The service renders the page, applies anti-bot measures and returns the result. Your client can stay a thin HTTP call, whether you use one of the published SDKs or plain cURL.
The API supports product detail pages, category pages and search pages. You can request rendered HTML when you want to parse the page yourself, or use extraction rules to receive structured JSON. JavaScript rendering, proxy rotation and geotargeting are available as request options.
Three common eCommerce workflows
Teams typically use the API for one of three jobs:
- Product detail aggregation across multiple stores, collecting SKU, brand, price, sale price, stock state, ratings, review count and image gallery.
- Price monitoring at scale, checking competitor prices on a schedule and comparing changes over time.
- Review extraction for sentiment analysis, gathering ratings and review text from public product pages.
Each workflow benefits from the same underlying rendering and anti-bot layer, but the output format and request options differ.
Product fields the scraper can read
A typical eCommerce product page exposes a consistent set of attributes. The table below maps each field to what it usually represents and why it matters for a data pipeline.
These fields are available when they render on the public page. If a field is loaded only after a login or a private API call, it falls outside what a public-page scraper can return.
Choosing between rendered HTML and structured JSON
The API can return rendered HTML or parsed JSON. The right choice depends on how stable your target pages are and how much post-processing you want to own.
- Rendered HTML is useful when you already have a parser, when you need the full page for debugging, or when the data shape changes frequently.
- extract_rules lets you map CSS selectors to field names and receive JSON directly. This is a good fit for stable product templates.
- ai_extract_rules accepts a natural-language specification and returns parsed JSON. It is useful when selectors are brittle or when you want to describe the fields in plain language.
A practical checklist:
- Confirm the target page is public and does not require login.
- Decide whether you need the whole page or only specific fields.
- If you need specific fields, start with extract_rules and fall back to ai_extract_rules when selectors break.
- Validate the returned JSON against your downstream schema before scheduling the job.
How request options affect credit usage
Credits are consumed per successful request, and the cost depends on which options are enabled. The table below summarizes the published credit costs for common combinations.
A request that enables a premium proxy together with JavaScript rendering costs 25 credits; with JavaScript rendering disabled, a premium proxy request costs 10 credits. Plan capacity by multiplying the expected number of requests by the credit cost of the option combination you actually enable. Credits are valid for one month and do not roll over.
From signup to first request
The setup path is short:
- Create an account to receive an API key and 1,000 free credits. No credit card is required for the trial.
- Install an SDK if you want one. Published SDKs cover Python, Node.js, Go, PHP, Ruby and Java; plain cURL also works.
- Send a GET or POST request with the target URL. The API renders the page and returns HTML or JSON depending on your options.
- Add advanced parameters only when needed: render_js for JavaScript-heavy pages, stealth_proxy for tougher anti-bot layers, country_code for geotargeting, and ai_extract_rules for natural-language extraction.
A first request can be as simple as sending one product URL and inspecting the returned HTML before adding extraction rules.
Legal and compliance considerations
Public-facing pages can usually be scraped, but the target site's terms of service should be reviewed before deploying a job. Post-login content should be avoided.
The source publisher states that it does not collect or store personal data from scraped sites unless the user explicitly requests it. Compliance with GDPR and CCPA depends on what you collect and how you use it, so treat the API as a transport layer and apply your own data-handling policy to the output.
Reliability and scale
The platform is designed to scale across thousands of headless browsers and rotating proxies. The source publisher reports typical response times of 1–5 seconds with high accuracy across most sites, including JavaScript-heavy ones. Concurrency limits vary by plan, from 25 concurrent requests on the entry plan up to 900 on the largest published enterprise tier.
Treat these figures as the source publisher's published capacity guidance rather than a guarantee for every target site. Anti-bot systems change frequently, so validate success rates against your specific targets before committing to a large schedule.
| Field | What it represents | Typical use |
|---|---|---|
| SKU | Merchant's unique product identifier | Joining records across stores |
| Brand | Manufacturer or seller name | Catalog normalization |
| Price | Current listed price | Price monitoring |
| Sale price | Discounted price when active | Promotion tracking |
| Stock state | In stock, low stock or out of stock | Availability checks |
| Ratings | Average customer score | Popularity comparison |
| Review count | Number of public reviews | Sentiment sample sizing |
| Image gallery | Product image URLs | Visual merchandising |
Fields are available only when they render on the public page.
| Option combination | Credits per successful request |
|---|---|
| Requests start at | 1 credit each |
| JavaScript rendering | 5 |
| Premium proxy without JavaScript rendering | 10 |
| Premium proxy with JavaScript rendering | 25 |
| Stealth proxy | 75 |
Credits are valid for one month and do not roll over. Premium proxy costs 10 credits without JavaScript rendering and 25 with it.
Frequently asked questions
Do I need an account to scrape eCommerce?
No external account is required. You sign up for an API key (1,000 free credits, no card), send the target URL, and the API handles the rest.
Is scraping eCommerce legal?
Public-facing pages can usually be scraped, but you should always review the target site's terms of service before deploying a job. Avoid post-login content.
What data can I extract from eCommerce?
Anything that renders on the public page. Common fields include SKU, brand, price, sale price, stock state, ratings, review count and image gallery. Use extract_rules with CSS selectors or ai_extract_rules for AI-driven extraction to receive structured JSON.
How do I get structured JSON from eCommerce?
Pass extract_rules with CSS selectors mapped to field names, or use ai_extract_rules with a natural-language specification. The response comes back as parsed JSON.
Which programming languages can I use to scrape eCommerce?
Any language that can make HTTP requests. Published SDKs cover Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works as well.
How much does it cost to scrape eCommerce?
Signup includes 1,000 free credits with no card required. Paid plans start at $19 per month for higher volume and concurrency. Credit cost per request depends on options: 5 credits for JavaScript rendering, 25 for a premium proxy with JavaScript rendering, and 75 for a stealth proxy.