Kroger search API

Endpoint facts

Method

GET

API path

/kroger/search

Auth

apiKey

Credits

3 credits/request

Platform

Kroger

Response schema

#/definitions/kroger.searchResponseDoc

Overview

Searches Kroger products by keyword and returns normalized product cards (price, unit price, brand, size, stock level) plus the facet groups Kroger offers for the query (brands, nutrition, savings, price range and more). Served from Kroger's own search JSON API with real upstream pagination; if that path is unavailable it falls back to parsing the rendered search page, and the source field reports which path answered. Facet filters and sort apply to the JSON path only: when any of them is set, a JSON-path failure returns an error rather than silently falling back to unfiltered results. 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

Browser cluster behavior

Some targets require real browser execution because the data is loaded through JavaScript, dynamic rendering, or interaction-like browser behavior.

For supported endpoints, Crawlora can route requests through a managed browser cluster. This allows Crawlora to execute JavaScript, load dynamic content, apply browser-level request behavior, and normalize the rendered result into JSON.

You do not need to operate your own Playwright, Puppeteer, Chrome, proxy, queue, or retry infrastructure.

Response behavior

- **Filters and sort apply to the `json_api` path only.** When any of them is set and that path fails, the request returns an error instead of falling back to the rendered page — the HTML path cannot honor these filters, so returning its unfiltered results would be wrong. Unfiltered requests still fall back as before. - Each result's `upc` is usable directly as the `upc` query parameter to [`/kroger/product`](kroger-product.md). - For browsing a specific product category instead of keyword search, see [`/kroger/category`](kroger-category.md), which returns results in this same shape. - `total_count` reflects the number of results Kroger's own page reports as loaded, not necessarily every result matching the query — Kroger's search page loads results in batches behind a "Load More Results" control. - `source` reports which upstream path served the response: `json_api` (Kroger's own search API, the primary path) or `html` (the rendered-page fallback, used only when the JSON path is unavailable). - **Pagination is real on the `json_api` path** — it uses Kroger's own page offset/size, and `has_more` reports whether further pages exist. On the `html` fallback `has_more` is always `false` and paging past page 1 remains best-effort. - `facets` lists the refinement groups Kroger offers for the query (brands, nutrition, savings, price range and more), each value with its result count. Only populated on the `json_api` path. - `brand` and `stock_level` are populated on the `json_api` path only; the rendered result cards carry neither. - A missing `query` returns `400` before any upstream request is made. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "edward & sons", "page": 1, "total_count": 37, "products": [ { "upc": "0004318200391", "url": "https://www.kroger.com/p/edward-sons-not-chick-n-bouillon-cubes/0004318200391?fulfillment=PICKUP&searchType=default_search", "title": "Edward & Sons® Not-Chick'n Bouillon Cubes", "image_url": "https://www.kroger.com/product/images/medium/front/0004318200391", "price": 2.99, "currency": "USD", "unit_price": "$1.20/oz", "size": "2.5 oz", "snap_ebt_eligible": true, "low_stock": false } ] } } ```

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