Nike Product Data, Sizes, and Drop Tracking
A Nike product page carries more than a name and a price: SKU, color variants, sizes, stock state, release date, category, and the full image gallery all sit behind client-side rendering and bot checks.
This page explains what a managed scraping API returns for Nike URLs, which request controls matter for each job type, and how the plan structure is organized so you can size a pipeline before writing code.
What a Nike product page returns
When the target is a Nike product page, the API is designed to return the fields a pricing or catalog pipeline actually needs: SKU, color variants, sizes, price, stock state, release date, category, and the full image gallery. These are the fields named for the product-page surface, so a drop-tracking job and a competitor-analysis job can share one request shape and differ only in how the output is stored.
For pages outside the product template, the API returns rendered HTML. You then apply extraction logic: CSS selectors via extract_rules, or natural-language extraction via ai_extract_rules. The distinction matters — the product-page field list is the expected shape for product URLs, while selector-based extraction is the general-purpose path for anything else that renders on the public page.
Three jobs this fits
Product-detail collection. Structured fields from the Nike catalog support competitor analysis and positioning work without hand-copying pages.
Price monitoring. Repeated requests against the same product URLs let you track price trends and stock state over time; the source frames this as a basis for dynamic pricing and inventory decisions.
Review analysis. Review text on Nike pages can be pulled and analyzed for feedback trends, which is useful when product development or merchandising teams want signal from customer language.
A fourth pattern appears in the source as a delivery format rather than a job: product pages can be returned as clean Markdown, which is convenient when the downstream consumer is a language model rather than a database.
Request controls, mapped to the problem they solve
Four request parameters matter for Nike work. Treat them as answers to specific failure modes rather than a checklist to enable everywhere.
render_js=true — use when the page needs client-side JavaScript executed before the HTML is useful. The API runs the page in a headless browser and returns post-render HTML.
stealth_proxy — use when a target becomes aggressive about blocking. Residential proxy rotation and headless browsing are the default posture; stealth_proxy is the escalation when normal traffic patterns are not enough.
country_code — use when Nike content varies by geography. The request routes through a residential IP in the named country.
ai_extract_rules (or extract_rules) — use when you need structured JSON out of a page rather than raw HTML. Selector rules and natural-language rules are two paths to the same output shape.
A useful failure distinction: if a request returns a block page or a challenge, the fix is on the proxy/stealth side. If it returns a full page but your parsed fields are empty or wrong, the fix is on the extraction-rule side. Mixing the two diagnoses wastes credits.
Worked example: a drop-tracking job
Suppose you want to watch a specific sneaker through a release window. Using the field list from the product-page surface, one request per product URL per interval is enough to build a time series with these columns: SKU, color variants, sizes, price, stock state, release date, category, image gallery. The release date field lets you schedule the polling window; the stock state field tells you when the drop has actually landed; the size list tells you which variants sold out first.
If the same product page also needs review text, that is a second extraction pass on the same URL with a different rule set, not a different endpoint. Keeping the two passes separate makes it easier to change one without breaking the other.
Setup path
Getting from zero to a first Nike request takes four moves: create an account to get an API key and starting credits; install an SDK for your stack (Python, Node, Go, PHP, Ruby, or Java) or use raw cURL; send a GET request with the target Nike URL; add advanced parameters only when the page needs them. The dashboard also includes a request builder that generates a snippet in Python, Node, Go, PHP, Ruby, or cURL, which is the no-code entry point for readers who want to test a URL before committing to a script.
How the plan structure is organized
Plans are split into standard tiers and enterprise tiers, and each tier is defined by four numbers plus a set of feature inclusions: monthly price, API credits, concurrent requests, and which features are included. Credits are valid for one month and do not roll over; requests start at one credit each. JavaScript rendering costs five credits per successful request. Premium proxies cost ten or twenty-five credits per successful request depending on whether JS rendering is enabled. Geotargeting reaches 200+ countries and territories on premium proxies, 40+ on classic proxies. Screenshots and extraction rules are included from the entry tier upward; priority email support, a dedicated account manager, and team management appear at the Business tier and above. Prices are exclusive of VAT.
The full plan table with every tier, credit count, concurrency figure, and feature inclusion is delivered as a structured table alongside this page; use it to compare tiers rather than relying on any single row quoted here.
What the reliability claims cover — and what they don't
The platform rotates proxies to avoid IP-based blocking, renders pages in a headless browser to mimic normal browsing, scales across thousands of headless browsers, and typically responds in one to five seconds with high accuracy across most sites, including JavaScript-heavy ones. It also states that the service does not collect or store personal data from scraped sites unless the user explicitly requests it.
These are the vendor's own descriptions of its platform. They are not an independent benchmark of success rates against Nike specifically, and they do not guarantee that any given URL will return the fields you expect on the first attempt. Plan for a validation pass on a sample of product URLs before scaling a pipeline.
| Plan | Monthly price | API credits | Concurrent requests | Priority email support | Dedicated account manager | Team management |
|---|---|---|---|---|---|---|
| Hobby | $19 /mo | 75,000 | 25 | Not included | Not included | Not included |
| Freelance | $49 /mo | 250,000 | 50 | Not included | Not included | Not included |
| Startup (Recommended) | $99 /mo | 1,000,000 | 100 | Not included | Not included | Not included |
| Business | $249 /mo | 3,000,000 | 200 | Included | Included | Included |
| Business + | $599 /mo | 8,000,000 | 400 | Included | Included | Included |
| Enterprise 14 | $999 /mo | 14,000,000 | 500 | Included | Included | Included |
| Enterprise 24 | $1,599 /mo | 24,000,000 | 600 | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 /mo | 41,000,000 | 700 | Included | Included | Included |
| Enterprise 69 | $3,599 /mo | 69,000,000 | 800 | Included | Included | Included |
| Enterprise 120 | $5,799 /mo | 120,000,000 | 900 | Included | Included | Included |
Prices are exclusive of VAT. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules are included on every tier listed; the table above shows only the features that vary by tier. Credit consumption rules: requests start at 1 credit each; JS rendering costs 5 credits per successful request; premium proxies cost 10 or 25 credits per successful request depending on whether JS rendering is enabled. Credits are valid for one month and do not roll over.
Frequently asked questions
What data can I extract from Nike?
The product-page surface returns SKU, color variants, sizes, price, stock state, release date, category, and the full image gallery. For other content that renders on the public page, two extraction paths return structured JSON: extract_rules with CSS selectors, or ai_extract_rules for AI-driven extraction.
How do I get started scraping Nike?
Create an account, take the API key, and send a GET request with the target Nike URL. The service renders the page, rotates proxies, and returns the data. The account starts with 1,000 free credits for testing.
Will I get blocked when scraping Nike?
Requests rotate residential proxies and run through a real headless browser, so they resemble normal traffic. If a target becomes aggressive, enable stealth_proxy on the request.
Can I scrape Nike 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. n8n workflows are also supported for catalog and drop-monitoring automation without scraper code.
How do I handle JavaScript when scraping Nike?
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 Nike from a specific country?
Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when Nike content varies by geography.
What is the difference between a blocked request and a bad extraction result?
A blocked request returns a challenge or block page; the fix is on the proxy and stealth side (stealth_proxy). A request that returns a full page but produces empty or wrong fields is an extraction-rule problem; the fix is on the extract_rules or ai_extract_rules side. Diagnosing which one you have before changing parameters saves credits.
How are credits consumed on a Nike request?
Requests start at one credit each. Enabling JavaScript rendering costs five credits per successful request. Premium proxies cost ten or twenty-five credits per successful request depending on whether JS rendering is enabled. Credits are valid for one month and do not roll over.