Fly By Jing · OAuth Scopes

Fly By Jing OAuth Scopes

OAuth 2.0 searched

Fly By Jing uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

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.

CompanyFood and BeverageConsumer Packaged GoodsEcommerceShopifyDirect to ConsumerMCPAgentic Commerce
Scopes: 0 Flows: Method: searched

Scopes (0)

Fly By Jing implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

Source

OAuth Scopes

fly-by-jing-scopes.yml Raw ↑
generated: '2026-07-19'
method: searched
docs: https://flybyjing.com/.well-known/openid-configuration
source: >-
  scopes_supported advertised in the live OIDC discovery document for the Fly By
  Jing storefront (Shopify Customer Account API).
flow: authorization_code
authorization_endpoint: https://account.flybyjing.com/authentication/oauth/authorize
token_endpoint: https://account.flybyjing.com/authentication/oauth/token
scopes:
- name: openid
  description: OpenID Connect sign-in; returns an ID token identifying the customer.
- name: email
  description: Access to the authenticated customer's email address and email_verified claim.
- name: 'customer-account-api:full'
  description: >-
    Full access to the Shopify Customer Account API for the signed-in customer
    (orders, profile, addresses, subscriptions, and other account data).
- name: 'customer-account-mcp-api:full'
  description: >-
    Full access to the Customer Account MCP API surface, exposing the customer's
    account data to MCP-based agents on behalf of the signed-in customer.
notes: >-
  Scopes are defined and enforced by Shopify's Customer Account platform, not by
  Fly By Jing directly. This is the storefront-facing customer identity surface;
  there is no separate first-party OAuth server.