Kroger API

Name: Kroger API
Brand: Kroger API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontoauth2,basic8 EndpointsREST

For Agents

Search Kroger products, find nearby stores, look up the authenticated shopper's profile, and add items to their cart through OAuth-protected endpoints.

Install Jentic One Beta

Connect the Kroger API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Kroger API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Kroger API.

Search the Kroger product catalogue by term, location, brand, and fulfillment method

Retrieve detailed product information by product ID including pricing per store location

Search store locations by ZIP code, latitude/longitude, chain, or department availability

GET STARTED

Start building with Kroger API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Kroger API, keeping it validated and agent-ready. The Kroger Public API exposes 8 endpoints for searching products, looking up store locations across the Kroger family of supermarket banners, adding items to a shopper's cart, and reading the authenticated customer profile. Authentication uses OAuth 2.0 with both client-credentials and authorization-code flows, plus HTTP Basic for the token endpoint, so partner apps can mix anonymous product browsing with authenticated cart and identity calls. Kroger operates more than 2,700 stores in the United States, and the location endpoints accept ZIP, latitude/longitude, and chain filters.

Use Cases

Patterns agents use Kroger API for, with concrete tasks.

★ Recipe-to-cart shopping experience

A meal-planning app converts a recipe into Kroger UPCs by searching the product catalogue with /products, then uses PUT /cart/add to drop the matched items into the authenticated shopper's cart for pickup or delivery. Kroger handles inventory, pricing, and fulfilment options. The integration is typically built in 3-5 days once OAuth client credentials are issued.

Call GET /products?filter.term=organic+spinach&filter.locationId=01400376 to find a UPC, then PUT /cart/add with that UPC and quantity 1.

Store locator for delivery and pickup

A retail app uses /locations to render a list of nearby Kroger banners — Kroger, Ralphs, King Soopers, Fred Meyer, and others — filtered by ZIP, distance, and available services such as pharmacy or fuel. The /locations/{locationId} endpoint returns hours and amenity flags so the app can pick the right pickup window. This pattern serves the bulk of the API's external traffic.

Call GET /locations?filter.zipCode.near=45202&filter.radiusInMiles=10 and return the names, addresses, and pharmacy availability of the matching stores.

Personalised product browsing

An authenticated shopping experience reads the shopper profile from /identity/profile and combines it with location-scoped product searches to surface store-specific pricing, promotions, and availability. The OAuth authorization-code flow links the shopper's Kroger identity to the partner app while keeping credentials on Kroger.

After completing the OAuth authorization-code flow, call GET /identity/profile and use the returned profileId to scope subsequent product queries.

Agent-driven grocery ordering via Jentic

An assistant agent searches Jentic for 'add items to grocery cart' and is matched to PUT /cart/add along with the product search and location operations needed to resolve UPCs. Jentic handles the OAuth token refresh on the agent's behalf so the agent can compose 'find the nearest Kroger, search for these items, add them to my cart' as a single workflow.

Use the Jentic MCP tool kroger_add_to_cart to add UPCs ['0001111041700','0007003820027'] with quantity 2 each to the authenticated shopper's cart.

Key Endpoints

8 endpoints — jentic publishes the only available openapi specification for kroger api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/connect/oauth2/token

Issue an OAuth access token

GET

/connect/oauth2/authorize

Start the authorization-code flow

GET

/products

Search products by term and location

GET

/products/{productId}

Get product details by ID

GET

/locations

Search store locations

GET

/locations/{locationId}

Get a specific store location

PUT

/cart/add

Add items to the authenticated cart

GET

/identity/profile

Get the authenticated customer profile

POST

/connect/oauth2/token

Issue an OAuth access token

GET

/connect/oauth2/authorize

Start the authorization-code flow

GET

/products

Search products by term and location

GET

/products/{productId}

Get product details by ID

GET

/locations

Search store locations

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Kroger client ID, client secret, and per-shopper refresh tokens are stored encrypted in the Jentic vault (MAXsystem). Jentic refreshes access tokens automatically — secrets never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'add items to grocery cart', 'find nearby kroger stores') and Jentic returns the matching Kroger operations along with their required scopes and parameters.

Time to first call

Direct Kroger integration: 3-5 days for OAuth authorization-code wiring, token refresh, and scope handling. Through Jentic: under a day — search, load, execute.

FAQs

Specific to using Kroger API through Jentic.

Why is there no official OpenAPI spec for Kroger API?

Kroger does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Kroger API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Kroger API use?

Kroger uses OAuth 2.0 with both client-credentials and authorization-code grants — product and location search work with client credentials, while /cart/add and /identity/profile require authorization-code tokens scoped to the shopper. The token endpoint authenticates with HTTP Basic. Jentic stores the client secret and refresh tokens encrypted in MAXsystem.

Can I add items to a Kroger shopper's cart with the Kroger API?

Yes. PUT /cart/add accepts a list of items, each with a UPC and quantity, against the OAuth token of the authorised shopper. The shopper must have completed the authorization-code flow first so the token carries the cart.basic:write scope.

What are the rate limits for the Kroger API?

Kroger enforces a daily call limit per developer application — typically 10,000 calls per day for the standard tier — with separate ceilings for product search, location search, and cart endpoints. Refer to developer.kroger.com for exact figures and design batched calls where possible.

How do I search for products in a specific store through Jentic?

Search Jentic for 'kroger product search', load GET /products, and execute it with filter.term and filter.locationId. The locationId can be sourced from a prior call to GET /locations. Install with pip install jentic.

Does the Kroger API support placing a final order or checkout?

No. The Public API stops at adding items to the cart. Final checkout, payment, fulfilment selection, and order tracking happen inside the Kroger app or website — there is no public endpoint that submits an order.