Base URL and environments

All requests go to the production host. Prefix every path with the base URL.

Authentication

Send your API key in the X-API-Key header on every request. There is no OAuth handshake and no per-request signing.
A Gymdesk API key starts with gd_ and carries 64 hexadecimal characters.
An API key carries the access of the academies it is scoped to. Store it as a secret in the system that consumes the API. Do not commit it to source control.

Getting an API key

Gymdesk issues API keys. Your Gymdesk contact generates a key for your academies and shares it with you securely. You do not create the key yourself, and you do not enter it into Gymdesk. The key lives wherever you consume the API from.
1

Ask for a key

Ask your Gymdesk contact for a key scoped to the academies you want to read.
2

Confirm its scope

Confirm the academies the key covers with GET /me.
3

Store it

Store the key in your integration, for example your accounting tool or Zapier.
Gymdesk shows the key one time only, when it creates or regenerates it. Gymdesk stores just a hash of the key, so nobody can show it to you again.

Your first request

Call GET /me to confirm your key works and to see what it can access.
academyIds lists the academies the key can read. The list is already resolved, so it names every academy the key reaches. An empty list means the key reaches no academy at all, and every scoped request returns 404.