Under Practice & system → Integrations you set up connections with other systems. This is part of the Gym plan and higher, and only the owner can do it.
Payouts via Stripe. The first tile is about your payouts. See Setting up payouts for your business.
The public API. If you want your website to show your class timetable, or your turnstile or accounting to access your data, you create an API key. Give it a name, so you know later what it’s for, and choose what it’s allowed to do. A key that isn’t allowed to do anything has no purpose.
One key per system. If one system drops out or a key leaks, you revoke only that one and the rest keeps working.
Save it straight away. You see the key once. We only store an encrypted fingerprint, so even we can’t look it up for you. Lost it? Revoke it and create a new one.
What’s happening. Below the keys is the traffic from the last seven days, including what went wrong. That way you see whether an integration still works.
For your developer. Every call goes with the key in the header: Authorization: Bearer fit_live_…. Ask us for the technical documentation.
A signal for every event. Want your system to hear straight away when a member joins, a payment succeeds or fails, or someone books? Then use a webhook; see Webhooks: a signal to your own system.