EGYM · OAuth Scopes

EGYM OAuth Scopes

OAuth 2.0 derived

EGYM 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/v1/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.

CompanyFitnessHealthWellnessCorporate WellnessConnected EquipmentGym ManagementMember ManagementCheck-InMeasurementsWorkoutsAnalyticsWebhooksGermany
Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
/api/v1/oauth/token
Flows
clientCredentials

Scopes (0)

EGYM 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:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-08-12'
method: derived
source: openapi/egym-equipment-vendor-standalone-openapi.yml
schemes:
- name: partner
  source: openapi/egym-equipment-vendor-standalone-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v1/oauth/token
scopes: []