Zen Planner · OAuth Scopes

Zen Planner OAuth Scopes

OAuth 2.0 derived

Zen Planner 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 https://api.partners.daxko.com/v3/partners/oauth2/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.

FitnessGym ManagementStudio ManagementMartial ArtsMembershipSchedulingClass BookingDaxko

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://api.partners.daxko.com/v3/partners/oauth2/token

Flows
clientCredentials

Scopes (0)

Zen Planner 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.

The Daxko Partners platform (which hosts the Zen Planner API) does not publish named OAuth permission scopes - its client_credentials token flow uses the scope field as a customer/client identifier rather than a permissions scope, per https://docs.partners.daxko.com/tutorials/authentication/.

📄 Provider scope reference: https://docs.partners.daxko.com/tutorials/authentication/

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/zenplanner-openapi.yml
docs: https://docs.partners.daxko.com/tutorials/authentication/
note: The Daxko Partners platform (which hosts the Zen Planner API) does not publish
  named OAuth permission scopes - its client_credentials token flow uses the scope
  field as a customer/client identifier rather than a permissions scope, per
  https://docs.partners.daxko.com/tutorials/authentication/.
schemes:
- name: oauth2
  source: openapi/zenplanner-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.partners.daxko.com/v3/partners/oauth2/token
  description: OAuth 2.0 against the Daxko Partners token service. Partner/API access tokens
    are obtained from https://api.partners.daxko.com/v3/partners/oauth2/token and member tokens
    from https://operations.oauth2.partners.daxko.com/token.
scopes: []