Kroger product reviews API

Endpoint facts

Method

GET

API path

/kroger/product/reviews

Auth

apiKey

Credits

3 credits/request

Platform

Kroger

Response schema

#/definitions/kroger.reviewsResponseDoc

Overview

Returns one page of a Kroger product's customer reviews -- review text, star rating, recommendation flag, helpful-vote counts, and customer photo URLs -- alongside the product's full star histogram. Customer display names are deliberately not returned. 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

- Customer display names are deliberately **not** returned. This endpoint surfaces review content and its metrics only. - `rating` is the whole product's star histogram, not just the current page's — it stays constant across pages. - `photos` carries customer-submitted review images, one entry per available size. - A product with no reviews returns an empty `reviews` list with `total_count: 0` — a success, not an error. Example response: ```json { "code": 200, "msg": "OK", "data": { "upc": "0007120200411", "page": 1, "page_size": 16, "average_rating": 4.64, "total_count": 293, "rating": {"average": 4.64, "count": 293, "five_stars": 225, "four_stars": 47, "three_stars": 0, "two_stars": 0, "one_star": 7}, "reviews": [ { "id": "25562ac4-cf25-5ea3-a77c-461c4269540e", "rating": 4, "text": "I really enjoyed this product! The flavor is vibrant and tropical.", "submitted_at": "2025-02-05T17:30:35.000Z", "recommended": false, "featured": false, "ratings_only": false, "helpful_vote_count": 0, "not_helpful_vote_count": 0, "photos": [ {"url": "https://photos-us.bazaarvoice.com/photo/2/…", "size": "medium"} ] } ] } } ```

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