Zumba Fitness Authentication

generated: '2026-07-21'
method: searched
source: https://www.zumba.com/.well-known/openid-configuration (live)
summary: >-
  Zumba operates an OpenID Connect 1.0 / OAuth 2.0 authorization server at
  https://www.zumba.com. Consumer sign-in is delegated via the authorization_code
  grant with PKCE (S256). ID tokens are signed RS256 against the published JWKS.
schemes:
- type: openIdConnect
  name: zumba_oidc
  issuer: https://www.zumba.com
  openIdConnectUrl: https://www.zumba.com/.well-known/openid-configuration
- type: oauth2
  name: zumba_oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://www.zumba.com/oauth/authorize
    tokenUrl: https://www.zumba.com/oauth/access_token
    refreshUrl: https://www.zumba.com/oauth/access_token
    scopes:
      openid: Authenticate the end user and issue an ID token
      email: Access the user's email address and email_verified claim
      profile: Access basic profile claims (given_name, family_name)
endpoints:
  authorization: https://www.zumba.com/oauth/authorize
  token: https://www.zumba.com/oauth/access_token
  userinfo: https://www.zumba.com/oauth/userinfo
  jwks: https://www.zumba.com/.well-known/jwks.json
  end_session: https://www.zumba.com/oauth/logout
grant_types_supported:
- authorization_code
- refresh_token
response_types_supported:
- code
pkce:
  supported: true
  code_challenge_methods:
  - S256
token_endpoint_auth_methods_supported:
- client_secret_post
- client_secret_basic
id_token_signing_alg_values_supported:
- RS256
subject_types_supported:
- public