Arlettie · OAuth Scopes

Arlettie OAuth Scopes

OAuth 2.0 probed

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

Tokens are issued from https://shopify.com/authentication/86227812661/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.

CompanyConsumerRetailE-CommerceFashionLuxuryPrivate SalesMarketplaceShopifyAgent CommerceMCPUCP
Scopes: 4 Flows: authorizationCode Method: probed

OAuth endpoints

Authorization URL
https://shopify.com/authentication/86227812661/oauth/authorize
Token URL
https://shopify.com/authentication/86227812661/oauth/token
Flows
authorizationCode

Scopes (4)

ScopeDescriptionFlows
openid Request an OIDC ID token identifying the authenticated customer. authorizationCode
email Release the customer's email and email_verified claims. authorizationCode
customer-account-api:full Full access to the authenticated customer's account API surface (orders, addresses, profile) for this shop. authorizationCode
customer-account-mcp-api:full Full access to the authenticated customer's account surface through the MCP transport — the customer-scoped counterpart to the anonymous UCP/MCP endpoint. authorizationCode

Source

OAuth Scopes

arlettie-scopes.yml Raw ↑
generated: '2026-08-17'
method: probed
source: https://lesechappees.arlettie.com/.well-known/oauth-authorization-server
docs: null
note: >-
  There is no OpenAPI to derive scopes from and Arlettie publishes no scopes reference page. This is
  the verbatim scopes_supported array from the live RFC 8414 authorization-server metadata served by
  the Les échappées storefront. Descriptions below are labelled by origin: two are OIDC-registered
  and carry their standard meaning; two are Shopify customer-account scopes whose meaning is inferred
  from their name and the resource they guard, and are marked as such rather than asserted.

schemes:
- name: shopify-customer-account-oauth
  issuer: https://shopify.com/authentication/86227812661
  source: well-known/arlettie-oauth-authorization-server.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://shopify.com/authentication/86227812661/oauth/authorize
    tokenUrl: https://shopify.com/authentication/86227812661/oauth/token
    code_challenge_methods_supported: [S256]

scopes:
- scope: openid
  description: Request an OIDC ID token identifying the authenticated customer.
  description_origin: oidc-core-registered
  flows: [authorizationCode]
  sources: [well-known/arlettie-oauth-authorization-server.json]
- scope: email
  description: Release the customer's email and email_verified claims.
  description_origin: oidc-core-registered
  flows: [authorizationCode]
  sources: [well-known/arlettie-oauth-authorization-server.json]
- scope: customer-account-api:full
  description: Full access to the authenticated customer's account API surface (orders, addresses,
    profile) for this shop.
  description_origin: inferred-from-scope-name
  flows: [authorizationCode]
  sources: [well-known/arlettie-oauth-authorization-server.json]
- scope: customer-account-mcp-api:full
  description: Full access to the authenticated customer's account surface through the MCP transport
    — the customer-scoped counterpart to the anonymous UCP/MCP endpoint.
  description_origin: inferred-from-scope-name
  flows: [authorizationCode]
  sources: [well-known/arlettie-oauth-authorization-server.json]
  note: >-
    Notable: this shop advertises an MCP-specific OAuth scope, which is what distinguishes the
    anonymous agent surface (catalog, cart, checkout) from a customer-authorized one (orders,
    saved addresses, account history).

summary:
  scope_count: 4
  granularity: coarse
  note: >-
    Both non-OIDC scopes are ":full" — there is no read/write or per-resource split, so a customer
    authorizing an agent grants the whole account surface or nothing.

x-evidence:
  fetched: '2026-08-17'
  url: https://lesechappees.arlettie.com/.well-known/oauth-authorization-server
  http_status: 200
  content_type: application/json

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/arlettie-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 email required.

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