Food & Drink — entry 007 of 20
Kroger
Kroger's public API exposes product search, pricing, and store-locator data across its US supermarket banners for registered developer applications using an OAuth client-credentials token. A live GET against the real gateway, api.kroger.com, returned a genuine 401 'access_token is missing' JSON error while carrying an echoed Access-Control-Allow-Origin header, resolving cors unknown -> yes and reconfirming API Key auth in the same probe.
AuthenticationAPI KeySign up with the provider to obtain credentials.
HTTPSSupportedTraffic is encrypted in transit.
CORSEnabledCallable directly from browser JavaScript.
PricingFreeNo paid tier — free for the documented use case.
FormatsJSONResponses can be requested as JSON.
GreatAPIs Score
Score64
Authentication15/25API key required
Pricing20/20Free to use
Docs0/20No docs or spec available
Formats9/15Single response format
Freshness20/20Verified within 6 months
Auth quickstart
- Sign up with the provider to get an API key.
- Send it on every request as a header
Authorization: <key> - The exact header isn't documented — Authorization is a common default; confirm in the provider's docs.
Stored keyNo key stored
Your key is stored only in this browser (localStorage) and sent directly to the API — never to greatapis.