Get Nike product reviews API

Endpoint facts

Method

GET

API path

/nike/product/reviews

Auth

apiKey

Credits

3 credits/request

Platform

Nike

Response schema

#/definitions/nike.productReviewsResponseDoc

Overview

Returns one page of a Nike product's normalized customer reviews, plus an aggregate rating summary (average rating and a per-star rating breakdown) that Nike's own product-detail endpoint does not otherwise expose. slug and style_color are the same values nike-product accepts (from a search result's colors[].slug/colors[].style_color fields). A product with no reviews yet returns a well-formed empty result rather than an error. Requesting a page beyond the available result pages returns a not-found error. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

3 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- A product with no reviews yet returns a well-formed empty result (`total_reviews: 0`, `reviews: []`), not an error. - `rating_histogram` is the count of ratings per star, ascending: index `0` is 1-star, index `4` is 5-star. - `total_reviews`/`total_pages` describe the full review set, independent of how many reviews are returned on this page. - An unknown or invalid `slug`/`style_color` combination returns `404`, the same as `nike-product`. - Requesting a `page` beyond the available result pages returns a not-found error. ```json { "code": 200, "msg": "OK", "data": { "slug": "vomero-premium-mens-road-running-shoes-l11miwwa", "style_color": "HQ2050-102", "page": 1, "page_size": 10, "total_pages": 23, "total_reviews": 224, "average_rating": 4.6, "rating_histogram": [6, 4, 7, 25, 182], "count": 10, "reviews": [ { "id": "1722809", "rating": 5, "headline": "Love them but you should know...", "body": "These are the cushiest shoes I have ever owned. Great if you have to stand on hard concrete style floors for hours...", "author": "Paul124122838", "location": "US", "recommended": false, "created_at": "2026-08-09T05:01:19Z" } ] } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related