Kroger · OAuth Scopes

Kroger OAuth Scopes

OAuth 2.0 searched

Kroger publishes 6 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the Kroger API on a user’s behalf.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

GroceriesGrocery RetailRetailE-CommerceProduct CatalogStore LocationsShopping CartLoyaltyAuthenticationPartner APIFortune 100
Scopes: 6 Flows: Method: searched

Scopes (6)

ScopeDescriptionFlows
product.compact Read the compact product response shape. Named in the Kroger Postman guide as the scope to configure for the Public API production collection, and present in the documented example JWT payload.
product.full.read Read the full product response shape. Used as the worked example in the "Understanding OAuth2" scope section.
product.personalized Product data personalized to the authenticated customer. Requested alongside cart.basic:rw and profile.full in the Auth Code Tutorial.
cart.basic:rw Read and write the authenticated customer's cart — the scope the Cart API tutorial requests before adding, updating or removing items.
profile.full Access the authenticated customer's profile. Requested in the Auth Code Tutorial's scope string.
coupon.basic Appears in the documented example access-token payload (scope: "product.compact coupon.basic"). Recorded because it is a real published string, and it is evidence of a Kroger API surface this catalog does not currently carry an entry for.

Source

OAuth Scopes

kroger-scopes.yml Raw ↑
specification: API Commons OAuth Scopes
specificationVersion: '0.1'
provider: Kroger
providerId: kroger
generated: '2026-08-27'
method: searched
source: >-
  Kroger developer documentation, read anonymously from the portal content API
  (https://developer.kroger.com/api/v1/developer/content/search.json, HTTP 200).
docs:
  - https://developer.kroger.com/documentation/public/security/guides-oauth
  - https://developer.kroger.com/documentation/public/security/auth-tutorial
  - https://developer.kroger.com/documentation/support/api-troubleshooting/troubleshooting
note: >-
  Kroger does NOT publish a consolidated scope reference page. There is no
  OpenAPI in this repo to derive a securitySchemes.oauth2.scopes block from, and
  the portal's own API-catalog endpoints (/api/v1/developer/apis,
  /contracts/document/...) return 401 anonymously. Every scope listed below is a
  literal string quoted in a public Kroger doc page; nothing here is inferred
  from a naming pattern. Treat the list as incomplete by construction — the
  authoritative set is the one Kroger assigns to an application at registration.
naming_convention:
  documented: >-
    "In general, scopes are a composition of the resource, the shape of the data,
    and the action, if available. For example, the scope product.full.read gives
    the application permission to read the full response of the product
    resource."
  shape: '<resource>.<data-shape>[.<action>]  |  <resource>.<data-shape>:<rw>'
assignment:
  self_service: false
  description: >-
    Kroger assigns a set of scopes to the application during registration, driven
    by which API Products were selected. An application is not authorized to use
    any scope outside that set; changes are by request to Kroger.
enforcement:
  missing_scope_status: 403
  missing_scope_body: '{"errors":{"timestamp":...,"code":"Forbidden","reason":"missing required scopes"}}'
scopes:
  - scope: product.compact
    api: Products API
    grant: client_credentials
    description: >-
      Read the compact product response shape. Named in the Kroger Postman guide
      as the scope to configure for the Public API production collection, and
      present in the documented example JWT payload.
    evidence: https://developer.kroger.com/documentation/public/getting-started/postman
  - scope: product.full.read
    api: Products API
    grant: client_credentials
    description: >-
      Read the full product response shape. Used as the worked example in the
      "Understanding OAuth2" scope section.
    evidence: https://developer.kroger.com/documentation/public/security/guides-oauth
  - scope: product.personalized
    api: Products API
    grant: authorization_code
    description: >-
      Product data personalized to the authenticated customer. Requested
      alongside cart.basic:rw and profile.full in the Auth Code Tutorial.
    evidence: https://developer.kroger.com/documentation/public/security/auth-tutorial
  - scope: cart.basic:rw
    api: Cart API
    grant: authorization_code
    description: >-
      Read and write the authenticated customer's cart — the scope the Cart API
      tutorial requests before adding, updating or removing items.
    evidence: https://developer.kroger.com/documentation/public/security/auth-tutorial
  - scope: profile.full
    api: Identity API
    grant: authorization_code
    description: >-
      Access the authenticated customer's profile. Requested in the Auth Code
      Tutorial's scope string.
    evidence: https://developer.kroger.com/documentation/public/security/auth-tutorial
  - scope: coupon.basic
    api: Coupon API (not listed in this repo's apis[])
    grant: client_credentials
    description: >-
      Appears in the documented example access-token payload
      (scope: "product.compact coupon.basic"). Recorded because it is a real
      published string, and it is evidence of a Kroger API surface this catalog
      does not currently carry an entry for.
    evidence: https://developer.kroger.com/documentation/public/security/service-to-service
    confidence: medium
scope_count: 6
completeness: partial
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This scope set
curl "https://apis.io/api/v1/scopes/kroger-scopes"
All oauth scopes
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.