Gymshark · OAuth Scopes

Gymshark OAuth Scopes

OAuth 2.0 searched

Gymshark publishes 14 OAuth 2.0 scopes via the authorizationCode, clientCredentials, implicit, and deviceCode flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Gymshark API on a user’s behalf.

Tokens are issued from https://auth.gymshark.com/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.

CompanyRetailE-CommerceApparelFitnessConsumerDirect to ConsumerIdentityOpenID Connect

Scopes: 14 Flows: authorizationCode, clientCredentials, implicit, deviceCode Method: searched

OAuth endpoints

Authorization URL
https://auth.gymshark.com/authorize

Token URL
https://auth.gymshark.com/oauth/token

Flows
authorizationCodeclientCredentialsimplicitdeviceCode

Scopes (14)

Scope	Description	Flows
openid	Request an ID token and perform OpenID Connect authentication.
profile	Request the default profile claims (name, family_name, given_name, nickname, picture, created_at).
offline_access	Request a refresh token so the client can obtain new access tokens without the user present.
name	Request the `name` claim.
given_name	Request the `given_name` claim.
family_name	Request the `family_name` claim.
nickname	Request the `nickname` claim.
email	Request the `email` claim.
email_verified	Request the `email_verified` claim.
picture	Request the `picture` claim.
created_at	Request the account `created_at` claim.
identities	Request the linked-identity array for the account (Auth0 extension).
phone	Request the `phone_number` and `phone_number_verified` claims.
address	Request the `address` claim.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-04'
method: searched
source: https://auth.gymshark.com/.well-known/openid-configuration
docs: null
note: >-
  Read verbatim from the `scopes_supported` array of Gymshark's own OpenID Connect
  Discovery document. Gymshark publishes no scope/permission reference page, so there
  are no product- or resource-level scopes to add — every scope advertised here is a
  standard OpenID Connect / Auth0 identity scope covering the customer profile, not a
  Gymshark business API. Scope descriptions below are the OpenID Connect Core 1.0 §5.4
  / Auth0 definitions of these standard scopes, not Gymshark-authored copy.
schemes:
- name: gymshark-oidc
  source: well-known/gymshark-openid-configuration.json
  issuer: https://auth.gymshark.com/
  flows:
  - flow: authorizationCode
    authorizationUrl: https://auth.gymshark.com/authorize
    tokenUrl: https://auth.gymshark.com/oauth/token
  - flow: clientCredentials
    tokenUrl: https://auth.gymshark.com/oauth/token
  - flow: implicit
    authorizationUrl: https://auth.gymshark.com/authorize
  - flow: deviceCode
    deviceAuthorizationUrl: https://auth.gymshark.com/oauth/device/code
    tokenUrl: https://auth.gymshark.com/oauth/token
scopes:
- scope: openid
  description: Request an ID token and perform OpenID Connect authentication.
  standard: OpenID Connect Core 1.0
- scope: profile
  description: Request the default profile claims (name, family_name, given_name, nickname,
    picture, created_at).
  standard: OpenID Connect Core 1.0
- scope: offline_access
  description: Request a refresh token so the client can obtain new access tokens without
    the user present.
  standard: OpenID Connect Core 1.0
- scope: name
  description: Request the `name` claim.
- scope: given_name
  description: Request the `given_name` claim.
- scope: family_name
  description: Request the `family_name` claim.
- scope: nickname
  description: Request the `nickname` claim.
- scope: email
  description: Request the `email` claim.
  standard: OpenID Connect Core 1.0
- scope: email_verified
  description: Request the `email_verified` claim.
- scope: picture
  description: Request the `picture` claim.
- scope: created_at
  description: Request the account `created_at` claim.
- scope: identities
  description: Request the linked-identity array for the account (Auth0 extension).
- scope: phone
  description: Request the `phone_number` and `phone_number_verified` claims.
  standard: OpenID Connect Core 1.0
- scope: address
  description: Request the `address` claim.
  standard: OpenID Connect Core 1.0
coverage:
  scopes_total: 14
  resource_scopes: 0
  identity_scopes: 14
x-evidence:
  fetched: '2026-08-04'
  url: https://auth.gymshark.com/.well-known/openid-configuration
  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/gymshark-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.