1
Create OAuth client credentials
An authorized company administrator creates Public API credentials from the
coach dashboard:
- Open Settings → Plugins in the FITsociety coach dashboard.
- Open the Public API plugin.
- If API access is new for your company, complete the access application: describe your goal, the data and actions you need, your software, and whether an external developer is involved. If yes, provide their name, company and email. Valid applications are approved automatically, once per company. Companies with API access already enabled can continue managing their integrations without applying again.
- On the OAuth clients tab, click Add API client.
- Give the client a recognizable name (for example
CRM sync), pick the scopes it needs, and accept any required data consents. - Copy the client secret immediately. It is shown once; store it securely.
fspc_ and a client secret prefixed fsps_.The application grants company access to create credentials and new
webhook subscriptions. You still select scopes and accept any required
data consents for each credential. See the developer documentation
for API authentication, endpoints and webhook setup.
2
Exchange credentials for an access token
Call the token endpoint with HTTP Basic auth
(Response:Access tokens live for 1 hour. If you omit
client_id as username, client_secret as password):scope, the token gets all
scopes assigned to the client; requested scopes must be a subset of the
client’s assigned scopes.3
Make your first call
GET /public/v1/me returns the profile of the authenticated API client —
a safe read that confirms auth works end to end:401, check that the token has not expired and that you are
sending Authorization: Bearer fspt_... — the Public API does not accept
x-api-key.4
Pick a starter scope set
Start minimal and read-only, then add scopes as your integration grows:
Useful next additions:
bookings:read, calendar_events:read,
finance_invoices:read. Only add *:write scopes once the read path
works, because writes hit live company data. The full catalog is on the
Authentication page, or fetch it live from
GET /public/v1/scopes.The starter scopes above need no consent. Scopes that expose health data or
private communication are
consent-gated and require
the matching consents flag when the API client is created.5
Where to go next
- Contracts — response envelopes, pagination, idempotency, and rate limits. Read this before writing production code.
- Errors — the error envelope and error keys you should handle.
- The API Reference tab — endpoint-level request and response detail, generated from the OpenAPI contract.
- The domain guides in the sidebar (clients, bookings, finance, progress, forms, reports, webhooks) — validation rules and privacy guardrails per domain.