Momence · OAuth Scopes

Momence OAuth Scopes

OAuth 2.0 derived

Momence 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.

Tokens are issued from /api/v2/auth/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.

FitnessWellnessStudio ManagementBookingSchedulingMembershipsPaymentsClass Management
Scopes: 0 Flows: password, authorizationCode Method: derived

OAuth endpoints

Authorization URL
/api/v2/auth/authorize
Token URL
/api/v2/auth/token
Flows
passwordauthorizationCode

Scopes (0)

Momence 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.

Momence OAuth2 does not define scopes - the API is always used as a specific user and all permissions are inferred from that user's Momence account role, per https://api.docs.momence.com/docs/getting-started and https://api.docs.momence.com/docs/authorization.

📄 Provider scope reference: https://api.docs.momence.com/docs/getting-started

Source

OAuth Scopes

momence-scopes.yml Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/momence-openapi.yml
docs: https://api.docs.momence.com/docs/getting-started
note: Momence OAuth2 does not define scopes - the API is always used as a specific
  user and all permissions are inferred from that user's Momence account role, per
  https://api.docs.momence.com/docs/getting-started and
  https://api.docs.momence.com/docs/authorization.
schemes:
- name: OAuth2
  source: openapi/momence-openapi.yml
  flows:
  - flow: password
    tokenUrl: /api/v2/auth/token
  - flow: authorizationCode
    authorizationUrl: /api/v2/auth/authorize
    tokenUrl: /api/v2/auth/token
scopes: []