generated: '2026-08-12'
method: derived
source: openapi/egym-data-export-openapi.yml, openapi/egym-data-hub-openapi.yml, openapi/egym-equipment-vendor-server-openapi.yml,
  openapi/egym-equipment-vendor-standalone-openapi.yml, openapi/egym-mms-api-v1-openapi.yml,
  openapi/egym-mms-api-v2-openapi.yml
summary:
  types:
  - apiKey
  - http
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - clientCredentials
schemes:
- name: mms
  type: apiKey
  in: header
  parameter: x-api-key
  description: Authentication is validated via an API key that is generated by EGYM for each
    gym location. This API key will not be identical with the access token used in the EGYM
    Gym API v1
  sources:
  - openapi/egym-data-export-openapi.yml
  - openapi/egym-data-hub-openapi.yml
  - openapi/egym-equipment-vendor-server-openapi.yml
  - openapi/egym-mms-api-v2-openapi.yml
- name: user
  type: http
  scheme: bearer
  bearerFormat: JWT
  sources:
  - openapi/egym-equipment-vendor-server-openapi.yml
  - openapi/egym-equipment-vendor-standalone-openapi.yml
- name: partner
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v1/oauth/token
    scopes: 0
  sources:
  - openapi/egym-equipment-vendor-standalone-openapi.yml
- name: accesstoken
  type: apiKey
  in: header
  parameter: X-ACCESS-TOKEN
  description: The token that will allow access the EGYM gym api for a specific gym.
  sources:
  - openapi/egym-mms-api-v1-openapi.yml