Zumba Fitness · OAuth Scopes

Zumba Fitness OAuth Scopes

OAuth 2.0 searched

Zumba Fitness 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.

Company
Scopes: 0 Flows: Method: searched

Scopes (0)

Zumba Fitness 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: https://www.zumba.com/.well-known/openid-configuration

Source

OAuth Scopes

zumba-fitness-scopes.yml Raw ↑ 
generated: '2026-07-21'
method: searched
source: https://www.zumba.com/.well-known/openid-configuration (scopes_supported)
docs: https://www.zumba.com/.well-known/openid-configuration
issuer: https://www.zumba.com
authorization_endpoint: https://www.zumba.com/oauth/authorize
token_endpoint: https://www.zumba.com/oauth/access_token
scopes:
- name: openid
  description: Required to initiate an OpenID Connect flow; issues an ID token identifying the end user (sub claim).
- name: email
  description: Grants access to the user's email and email_verified claims.
- name: profile
  description: Grants access to basic profile claims (given_name, family_name, pid).
claims_supported:
- sub
- iss
- aud
- iat
- exp
- auth_time
- nonce
- email
- email_verified
- given_name
- family_name
- pid