Oishii · OAuth Scopes

Oishii OAuth Scopes

OAuth 2.0 searched

Oishii publishes 4 OAuth 2.0 scopes via the authorizationCode, refreshToken, and urn:ietf:params:oauth:grant-type:jwt-bearer flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Oishii API on a user’s behalf.

Tokens are issued from https://shopify.com/authentication/26346881082/oauth/token.

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.

CompanyAgricultureVertical FarmingFood and BeverageConsumer ProductsE-CommerceRetailAgent CommerceShopifyMCPUniversal Commerce Protocol

Scopes: 4 Flows: authorizationCode, refreshToken, urn:ietf:params:oauth:grant-type:jwt-bearer Method: searched

OAuth endpoints

Authorization URL
https://shopify.com/authentication/26346881082/oauth/authorize

Token URL
https://shopify.com/authentication/26346881082/oauth/token

Flows
authorizationCoderefreshTokenurn:ietf:params:oauth:grant-type:jwt-bearer

Scopes (4)

Scope	Description	Flows
openid	OpenID Connect authentication; issue an ID token for the signed-in customer.	authorizationCode
email	Release the customer's email address and email_verified claim.	authorizationCode
customer-account-api:full	Full access to the Shopify Customer Account API on behalf of the signed-in customer (orders, addresses, profile).	authorizationCode
customer-account-mcp-api:full	Full access to the customer-account MCP API on behalf of the signed-in customer — the authenticated agent surface complementing the anonymous storefront MCP server.	authorizationCode

📄 Provider scope reference: https://oishii.com/.well-known/openid-configuration

Source

OAuth Scopes

generated: '2026-08-04'
method: searched
source: https://oishii.com/.well-known/oauth-authorization-server
docs: https://oishii.com/.well-known/openid-configuration
note: >-
  Scopes are declared by the Shopify customer-account authorization server that oishii.com delegates
  identity to. Oishii publishes no OpenAPI, so these are read verbatim from the RFC 8414 / OIDC discovery
  documents served on the oishii.com host — not derived from a spec. The two customer-account scopes are
  coarse-grained (":full"); there is no per-resource scope surface.
schemes:
- name: shopify-customer-account
  source: well-known/oishii-oauth-authorization-server.json
  issuer: https://shopify.com/authentication/26346881082
  flows:
  - flow: authorizationCode
    authorizationUrl: https://shopify.com/authentication/26346881082/oauth/authorize
    tokenUrl: https://shopify.com/authentication/26346881082/oauth/token
    pkce: S256
  - flow: refreshToken
    tokenUrl: https://shopify.com/authentication/26346881082/oauth/token
  - flow: urn:ietf:params:oauth:grant-type:jwt-bearer
    tokenUrl: https://shopify.com/authentication/26346881082/oauth/token
scopes:
- scope: openid
  description: OpenID Connect authentication; issue an ID token for the signed-in customer.
  flows: [authorizationCode]
  sources: [well-known/oishii-openid-configuration.json]
- scope: email
  description: Release the customer's email address and email_verified claim.
  flows: [authorizationCode]
  sources: [well-known/oishii-openid-configuration.json]
- scope: customer-account-api:full
  description: Full access to the Shopify Customer Account API on behalf of the signed-in customer (orders, addresses, profile).
  flows: [authorizationCode]
  sources: [well-known/oishii-oauth-authorization-server.json]
- scope: customer-account-mcp-api:full
  description: Full access to the customer-account MCP API on behalf of the signed-in customer — the authenticated agent surface complementing the anonymous storefront MCP server.
  flows: [authorizationCode]
  sources: [well-known/oishii-oauth-authorization-server.json]
x-evidence:
  fetched: '2026-08-04'
  url: https://oishii.com/.well-known/oauth-authorization-server
  http_status: 200

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/oishii-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.

GitHub Google LinkedIn

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