Kroger store API

Endpoint facts

Method

GET

API path

/kroger/store

Auth

apiKey

Credits

3 credits/request

Platform

Kroger

Response schema

#/definitions/kroger.storeResponseDoc

Overview

Returns one Kroger store's public detail: postal address, geographic coordinates, phone number, displayed opening hours (including any daily break hours), and whether it has a drive-thru. store_id is the same store/location id kroger-products and kroger-suggest accept. 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

- `hours` rows use Kroger's own day groupings (e.g. `Mon - Fri`), not one row per weekday. `break_hours` carries any daily closure window (Kroger publishes these for pharmacy counters). - `is_today` marks the row covering the current day in the store's own timezone, as Kroger computes it. - Only shopper-facing fields are returned. Kroger's upstream payload also carries an internal operational block (EDI flags, processing times, internal facility codes); that is deliberately not surfaced. - An unknown `store_id` returns `404`. Example response: ```json { "code": 200, "msg": "OK", "data": { "store_id": "01600531", "name": "Waterville", "brand": "KROGER", "phone": "(419) 878-1040", "open_text": "Open Until 8 PM", "address": { "address_lines": ["8730 Waterville Swanton Rd"], "city": "Waterville", "state": "OH", "postal_code": "43566", "country": "US" }, "location": {"latitude": 41.509023, "longitude": -83.75036}, "hours": [ {"days": "Sun", "hours": "10:00 AM - 5:00 PM", "is_today": false}, {"days": "Mon - Fri", "hours": "8:00 AM - 8:00 PM", "is_today": true} ], "break_hours": [{"days": "Sun - Sat", "hours": "1:00 PM - 1:30 PM", "is_today": true}], "has_drive_thru": true } } ```

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