Julep Beauty · OAuth Scopes

Julep Beauty OAuth Scopes

OAuth 2.0 searched

Julep Beauty 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.

CompanyBeautyCosmeticsSkincareRetailE-CommerceDirect to ConsumerShopifyAgentic CommerceUniversal Commerce Protocol
Scopes: 0 Flows: Method: searched

Scopes (0)

Julep Beauty 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.

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-07-19'
method: searched
source: https://www.julep.com/.well-known/openid-configuration
name: Julep customer-account OAuth scopes
description: >-
  Scopes advertised by the OpenID Connect / OAuth authorization-server metadata served on
  Julep's own domain for its Shopify Customer Accounts deployment. Captured verbatim from
  scopes_supported; Julep publishes no separate scope reference page, so no descriptions
  beyond the standard OIDC meanings and the Shopify Customer Account API naming are
  asserted here.
issuer: https://shopify.com/authentication/2228781091
authorization_endpoint: https://account.julep.com/authentication/oauth/authorize
token_endpoint: https://account.julep.com/authentication/oauth/token
flows:
- authorization_code
- refresh_token
- 'urn:ietf:params:oauth:grant-type:jwt-bearer'
pkce: S256
docs: null
docs_note: >-
  No provider-published scope/permission reference page was found on www.julep.com; the
  authoritative list below is the discovery document itself.
scopes:
- name: openid
  description: Standard OpenID Connect scope requesting an ID token for the signed-in customer.
  standard: true
- name: email
  description: Standard OpenID Connect scope releasing the email and email_verified claims.
  standard: true
- name: 'customer-account-api:full'
  description: >-
    Full access to the customer-account surface on behalf of the signed-in customer.
    Named by the discovery document; Julep publishes no finer-grained breakdown.
  standard: false
- name: 'customer-account-mcp-api:full'
  description: >-
    Full access to the customer-account surface over the MCP transport, for agents acting
    on behalf of the signed-in customer.
  standard: false
claims_supported: [iss, sub, aud, exp, iat, nonce, sid, email, email_verified]

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/julep-beauty-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.