Adidas product data via API, with rendering and proxies handled
Send an Adidas product URL and receive rendered HTML or structured fields such as price, sizes, colours, ratings and images, without operating browsers or proxy rotation yourself.
Choose the controls below according to what the page needs.
What teams collect from Adidas pages
Most product-page work falls into three buckets. Size data supports inventory forecasting and supply planning. Current prices support competitor comparison and pricing decisions. Shipping details support logistics and distribution planning. A useful run therefore starts by naming which of those decisions the data will feed, because that determines whether you need raw HTML, selected fields, or a screenshot.
How a request flows
Create an account to obtain an API key. Install the SDK for your stack, or use raw cURL. Pass an Adidas URL with your key; rendering and bot handling occur server-side and the response is HTML or JSON. Add advanced controls only when needed: render_js for JavaScript-heavy pages, stealth_proxy for stronger anti-bot handling, country_code for regional content, and extract_rules or ai_extract_rules for structured output. A practical checklist is: confirm the exact product URL, decide HTML versus JSON, enable rendering if fields appear only after scripts run, set the country when regional variation matters, and test one URL before scaling.
Choosing the right output
A single product response can include SKU, price, size variants, colour options, material, brand line, ratings and the image gallery. CSS-based extraction is appropriate when selectors are stable and you want precise field control. Natural-language extraction is appropriate when page structure changes often and you prefer to describe the fields you need. Screenshots help visual verification, Markdown suits downstream language-model workflows, and scripted JavaScript scenarios suit interactions such as clicks or scrolling before capture.
Failure checks before you scale
Do not treat a blocked or empty response as a parsing problem first. Check whether the page requires JavaScript, whether regional routing is needed, and whether stealth_proxy is warranted. If throttling persists, reduce request aggressiveness by spacing calls or using multiple sessions. Plan concurrency, rather than a target-specific rate limit, is the stated API constraint.
| Control | Use it when | What you get |
|---|---|---|
| render_js | Content appears only after JavaScript runs | Post-render HTML from a headless browser |
| stealth_proxy | Blocking becomes aggressive | Additional anti-bot handling for that request |
| country_code | Content varies by country | Request routed through that country |
| extract_rules | You have stable CSS selectors | Parsed JSON mapped to named fields |
| ai_extract_rules | You prefer a natural-language field spec | Parsed JSON from described fields |
Parameter names are preserved exactly as supplied; live endpoint behaviour requires owner configuration and verification.
Frequently asked questions
Will I get blocked when scraping Adidas?
Requests are routed through rotating residential proxies and a real headless browser so they resemble ordinary browsing. When blocking becomes aggressive, turn on stealth_proxy for that request.
Can I scrape Adidas without writing code?
Yes. The dashboard request builder accepts a URL and parameters, then produces a ready snippet in Python, Node, Go, PHP, Ruby or cURL.
How do I handle JavaScript when scraping Adidas?
Set render_js=true. The page runs in a headless browser on the server, JavaScript executes, and the returned HTML reflects the rendered page.
Can I scrape Adidas from a specific country?
Yes. Supply country_code to route the request through a residential IP in that country, which helps when product content differs by region.
What's the rate limit for scraping Adidas?
Limits are based on plan concurrency rather than a per-target rate limit. If the target throttles aggressive patterns, space requests out or use multiple sessions.
How do I get structured JSON from Adidas?
Use extract_rules to map CSS selectors to field names, or ai_extract_rules with a natural-language specification. The API returns the extracted fields as parsed JSON.