Review Scraper API for Ratings and Buyer Sentiment
A review scraper API turns a public review page into a repeatable data source.
Instead of maintaining headless browsers and proxy pools yourself, you submit a review URL and choose what comes back: the fully rendered page, or structured fields such as star rating, review text, reviewer name, review date, verified-purchase flag, and helpful-vote count. This page explains the request controls, the output shapes, and the practical decision points for teams building rating and sentiment pipelines.
What a single request returns
The API accepts a public review page URL and renders it server-side. You can request rendered HTML or structured output. The structured path uses extract_rules with CSS selectors mapped to field names, or ai_extract_rules with a natural-language specification; either way the response arrives as parsed JSON. The review surface the API is designed around includes star rating, review text, reviewer name, review date, verified-purchase flag, and helpful-vote count.
Field and control map
Use this map to plan a request before you write code. Each row pairs a review field with the request control that affects it.
Three workflows teams build
The most common patterns are aggregating product review datasets, tracking sentiment over time, and monitoring competitor ratings across review sites. Product review extraction supports sentiment analysis and competitive intelligence. Rating collection supports pricing analysis against customer feedback and market trends. Sentiment trend analysis supports strategic positioning and competitor comparison. Each workflow is a loop over review URLs with a stable extraction specification.
From signup to structured output
Step 1: create an account to obtain an API key and whatever starting credit allowance the service currently advertises; check the signup page or plan details for the exact figure rather than assuming a number. Step 2: install an SDK for Python, Node, Go, PHP, or Ruby, or skip the SDK and call the API directly over HTTP. Step 3: send the review URL by POST or GET; the service renders the page, handles anti-bot measures, and returns rendered HTML or structured JSON when extract_rules or ai_extract_rules is supplied. Step 4: add advanced parameters only when the page needs them — render_js for JavaScript, stealth_proxy for CAPTCHA-heavy targets, country_code for geo-targeting, and ai_extract_rules for natural-language extraction.
Worked example: one URL, two output shapes
Suppose you want the verified-purchase flag and star rating from a public product review page. First request the page with render_js=true and no extraction rules. The response is the post-render HTML, which you can inspect to confirm the selectors exist. Then send the same URL with extract_rules mapping your chosen CSS selectors to field names such as rating, review_text, reviewer, review_date, verified_purchase, and helpful_votes. The second response is parsed JSON you can load directly into a sentiment or analytics pipeline. If the page is JavaScript-heavy and the first response looks empty, the rendering step is the place to check before changing selectors.
Rendering failure versus throttling failure
Two failure modes look similar but need different fixes. A rendering failure shows up as a page shell with no review content even though the request succeeded; confirm render_js=true is set and that the target page actually loads reviews after JavaScript runs. A throttling failure shows up as blocked or rate-limited responses from the target site; the API applies concurrency limits per plan rather than per-target rate limits, so if a target throttles aggressive patterns, space out requests or use multiple sessions. Checking which symptom you see prevents wasted selector rewrites.
Pre-flight checklist
Before scaling a review pipeline, confirm each item: the target review pages are public; you have a stable extraction specification for the fields you need; render_js is enabled for JavaScript-heavy pages; country_code is set only where content genuinely varies by geography; request spacing matches the target site's tolerance; and your plan's concurrency limit matches your expected parallel load.
Plan structure and credit mechanics
Plans are organized by monthly API credits and concurrent requests. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots with extraction rules are included across the standard tiers; higher tiers add priority email support, a dedicated account manager, and team management. Confirm the current support scope and response expectations with the provider before relying on them. API credits are valid for one month and do not roll over, and requests start at one credit each. Enabling JS rendering costs five API credits per successful request. Premium proxies cost ten or twenty-five API credits per successful request depending on whether JS rendering is enabled. Geotargeting reaches more than two hundred countries and territories, with more than forty available on classic proxies. Check the current pricing page for the applicable VAT treatment. Monthly plan prices and credit allowances change over time, so verify the figures on the live pricing page before committing to a tier.
Language and integration options
SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java, and plain cURL works for any stack. The dashboard request builder generates a snippet in Python, Node, Go, PHP, Ruby, or cURL after you paste a URL and set parameters, which is the fastest path if you do not want to write request code by hand. Integrations also exist for n8n and Make for no-code automation, and a CLI is available for terminal use.
| Review field | Where it appears | Request control that affects it |
|---|---|---|
| Star rating | Structured output or rendered HTML | extract_rules or ai_extract_rules |
| Review text | Structured output or rendered HTML | extract_rules or ai_extract_rules |
| Reviewer name | Structured output or rendered HTML | extract_rules or ai_extract_rules |
| Review date | Structured output or rendered HTML | extract_rules or ai_extract_rules |
| Verified-purchase flag | Structured output or rendered HTML | extract_rules or ai_extract_rules |
| Helpful-vote count | Structured output or rendered HTML | extract_rules or ai_extract_rules |
| Post-render HTML | Raw response body | render_js |
| Geo-specific content | Rendered page | country_code |
| CAPTCHA-protected page | Rendered page | stealth_proxy |
Field availability depends on the target review page's public markup; the API returns what the page exposes.
Frequently asked questions
Can I scrape review data without writing code?
Yes. The dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby, or cURL. For fully no-code automation, n8n and Make integrations are also available.
How do I handle JavaScript when scraping review data?
Pass render_js=true on the request. The page runs in a real headless browser, JavaScript executes server-side, and the post-render HTML is returned.
Can I scrape review data from a specific country?
Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when review content varies by geography.
What's the rate limit for scraping review data?
The API applies concurrency limits per plan, not per-target rate limits. If a target site throttles aggressive patterns, space out requests or use multiple sessions.
How do I get structured JSON from review data?
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 review data?
Any language works. SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java, and plain cURL works too.