Technical documentation: all current API routes, permissions and examples are available at docs.fitsociety.io. Developers should start with the Public API quickstart.
Working with an external developer? Agree in advance which system to connect, which data is needed, which actions the connection may perform and who will manage it. Have an administrator create the client in the correct company. Give your developer the documentation link and only the necessary connection details through a secure channel; do not share your coach password. Use a separate client for each integration so you can revoke its access individually later.
An API client provides access for one external integration within your company. An authorized administrator creates it. Your developer uses its client ID and client secret to configure the connection.
In this article
1. Create an API client
Select the correct company in the coach dashboard.
Go to Settings → Plugins and Integrations → Public API.
Open OAuth clients and choose Add API client.
Enter a recognizable name, such as “CRM integration”, and review the selected scopes.
Accept only the required data consents for this integration and choose Create client.
Copy the client ID and the client secret shown once. Store them securely and transfer them securely to your developer.
Use a separate client for each integration. Do not share a coach password or put secrets in a support message or public code.
2. Choose only the necessary permissions
Scopes define what an integration may do. For example, clients:read allows reading client data; clients:write allows supported write actions. Review the preselection: a new integration is not automatically read-only.
Health data and private communication require additional explicit consent. Company-wide status automation has separate permissions: client_status_automation:read and client_status_automation:write. Permission to update clients alone does not grant the latter.
The permissions of existing API clients are not automatically expanded. Want to use different scopes? Create a new client in this screen with the required permissions, have your developer switch over, then revoke the old client.
3. Have the connection checked
Your developer exchanges the credentials through OAuth for a temporary access token. That token is valid for one hour. Start with a read request, such as the API client profile, following the technical quickstart.
The Public API has no separate sandbox. Write actions affect real company data. Check one agreed workflow together before automating more actions.
4. Renew, revoke or troubleshoot access
Rotate secret: use this if the secret is lost or exposed. The old credentials and active access tokens become invalid; update the integration immediately.
Revoke: stops this API client and invalidates its active tokens. This cannot be undone; create a new client for a new connection.
401: have the token and credentials checked.
403: check scopes, data consent and company access.
429: the integration is sending too many requests; your developer must respect the required wait.
Need help? Share the error code, the time and, if available, the request ID with support, without secrets or access tokens.
Related articles
Technical documentation for your developer (English)