Xbox Reviews and Ratings Through One API
Xbox review pages are JavaScript-driven and protected by bot detection, so a plain HTTP client often gets a shell of a page instead of the ratings and review text you need.
A hosted scraping API puts the browser, proxy rotation and rendering behind a single request: you send a public Xbox review URL, and the service returns the review fields as structured data. This page explains what you can collect, which request options change the output and the credit cost, and where the practical limits sit.
What you can collect from public Xbox review pages
A single Xbox review page can yield the game title, the review score, the reviewer handle, the review text, helpful vote counts, the review date and genre tags. Those fields support three common research tasks:
- Ratings snapshot. Star ratings, total review counts and genre-aggregated scores per title, useful for market research on how a title is received.
- Feedback trends. Review text, helpful votes and date stamps per title, useful for sentiment tracking and quality monitoring over time.
- Title comparison. Review counts and average user ratings across Xbox store titles, aggregated by genre, release date or publisher.
A worked example: if you want to compare two titles, request each title's review page, then compare average user rating alongside review count. A high average on a small review count is weaker evidence than a similar average on a large count, and helpful-vote counts help you weight which review text is most visible to other players. Review dates let you separate launch-window sentiment from later patches.
How a request works
The workflow is four steps:
- Create an account to get an API key and the starting free credits.
- Install an SDK for your stack (Python, Node.js, Go, PHP, Ruby or Java) or use plain cURL.
- Send the public Xbox review URL with your API key. The renderer executes the page in a real browser, rotates the IP and returns the response.
- Add advanced parameters when the default response is not enough.
For structured output, pass extract_rules with CSS selectors mapped to field names, or ai_extract_rules with a natural-language spec; the response comes back as parsed JSON. The page also supports a Markdown output format for LLM-ready text, full-page screenshots via the Screenshot API, and JavaScript scenarios that click, scroll or wait for dynamic content before extraction.
Request options and what each one costs
Credit cost per request depends on the options you enable. The table below maps the option to its effect and its credit cost. The credit figures and the credit-validity terms are owner-supplied commercial values: {{OWNER_CREDIT_COSTS}} and {{OWNER_CREDIT_VALIDITY}}. Confirm current pricing on the pricing page before budgeting.
| Option | What it does | Credit cost per successful request |
|---|---|---|
render_js | Executes the page in a real browser | {{OWNER_CREDIT_COST_RENDER_JS}} |
premium_proxy without JS rendering | Premium proxy pool | {{OWNER_CREDIT_COST_PREMIUM_PROXY_NO_JS}} |
premium_proxy with JS rendering | Premium proxy plus browser rendering | {{OWNER_CREDIT_COST_PREMIUM_PROXY_JS}} |
stealth_proxy | Stealth proxy for CAPTCHA-heavy targets | {{OWNER_CREDIT_COST_STEALTH_PROXY}} |
country_code | Routes through 200+ countries and territories (40+ on classic proxies) | Included in plan |
extract_rules / ai_extract_rules | CSS/XPath or natural-language extraction to JSON | Included in plan |
| Screenshots | Full-page capture | Included in plan |
Because Xbox review pages are JavaScript-driven, a working request will usually include render_js, so budget the render_js credit cost per page before any proxy upgrade.
Concurrency limits versus target-side throttling
These are two different constraints and they need different responses:
- Plan concurrency. The API enforces a concurrency limit per plan — the number of requests that can be sent at the same time. If you exceed it, requests queue or fail at the API boundary. The fix is to lower in-flight requests or move to a plan with higher concurrency.
- Target-side throttling. Xbox may throttle aggressive request patterns regardless of your plan. The fix is to space out requests or use multiple sessions.
There is no per-target rate limit published by the API; the concurrency ceiling is the plan-level control. If you see failures only on Xbox pages while other targets succeed, suspect target-side throttling rather than your plan limit.
Before you build: a short checklist
- Confirm the pages you need are public and not behind a login; post-login content is out of scope.
- Read the target site's terms of service before deploying.
- Estimate credits per page from the options table, then multiply by page count and refresh frequency.
- Decide whether you need raw HTML, structured JSON via
extract_rules, or Markdown for LLM input. - Set a request spacing policy so you do not trip target-side throttling.
- Keep a record of the review date on each row so sentiment comparisons are time-anchored.
| Option | What it does | Credit cost per successful request |
|---|---|---|
| render_js | Executes the page in a real browser | {{OWNER_CREDIT_COST_RENDER_JS}} |
| premium_proxy without JS rendering | Premium proxy pool | {{OWNER_CREDIT_COST_PREMIUM_PROXY_NO_JS}} |
| premium_proxy with JS rendering | Premium proxy plus browser rendering | {{OWNER_CREDIT_COST_PREMIUM_PROXY_JS}} |
| stealth_proxy | Stealth proxy for CAPTCHA-heavy targets | {{OWNER_CREDIT_COST_STEALTH_PROXY}} |
| country_code | Routes through 200+ countries and territories (40+ on classic proxies) | Included in plan |
| extract_rules / ai_extract_rules | CSS/XPath or natural-language extraction to JSON | Included in plan |
| Screenshots | Full-page capture | Included in plan |
Credit figures and credit-validity terms are owner-supplied commercial values ({{OWNER_CREDIT_COSTS}}, {{OWNER_CREDIT_VALIDITY}}); confirm current pricing before budgeting.
Frequently asked questions
Do I need an Xbox account to scrape Xbox reviews?
No external account is required. You sign up for an API key, send the public review URL and the service handles rendering and proxy rotation. Post-login content is not part of the workflow.
Is scraping Xbox reviews legal?
Public-facing pages can usually be scraped, but review the target site's terms of service before deploying and avoid post-login content. Legal compliance depends on your jurisdiction and use case.
What is the rate limit for scraping Xbox reviews?
The API enforces concurrency limits per plan rather than per-target rate limits. If Xbox throttles aggressive patterns, space out requests or use multiple sessions.
How do I get structured JSON from Xbox reviews?
Pass extract_rules with CSS selectors mapped to field names, or ai_extract_rules with a natural-language spec. The response comes back as parsed JSON.
Which programming languages can I use?
SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too. Pick whatever your stack already uses.
How much does it cost to scrape Xbox reviews?
Free-credit allowance, starting plan price and per-request credit costs are owner-supplied commercial terms: {{OWNER_FREE_CREDIT_ALLOWANCE}}, {{OWNER_PLAN_PRICES}} and {{OWNER_CREDIT_COSTS}}. Credit validity and rollover terms are {{OWNER_CREDIT_VALIDITY}}. Confirm current pricing before budgeting.