Coaching
FitnessSyncer for Coaches lets a coach see the data each client chooses to share, plan workouts on their calendars, comment on what they did, and keep notes about them. Coaching is run from FitnessSyncer.com and the FitnessSyncer apps; to learn how it works for a coach and for a client, see Get started as a coach and Coaching in the help center.
What the API Reaches
Every endpoint in this documentation acts on the account that authorized the token. A coach’s token reads and writes the coach’s own sources, items and planned workouts, and never a client’s: no endpoint takes a client, and none lists a coach’s clients.
A client’s token is the same. What a client shares with their coach is chosen on FitnessSyncer.com or in the apps, and changes nothing about what an application the client authorized can read.
The Coaching Scopes
The coaching_read and coaching_write scopes are for the MCP server, whose coaching tools take a client_id. With coaching_read, a coach’s AI assistant can list the coach’s clients and join requests, read a client’s recent sessions, training load, comments, check-ins, habits, assessment results, notes and the automations that ran for them, read or analyze a client’s planned workouts and season plan, and, by passing client_id to the item, summary and analysis tools, read the health data the client shares. With coaching_write, it can comment on a client’s workout, mark a session reviewed, add a note, send a form, decide an automation’s draft, answer a join request, invite a client, and plan, change or delete a client’s workouts. What a coach can ask for is described under Coaching your clients on the MCP server’s help page.
Every one of these tools reads a client only as far as that client shares with that coach:
- Only the data types the client shares, and only from the day they began sharing.
- Only while the coaching is active. A paused or removed client is not reachable, and neither is any client of a coach whose plan or trial has lapsed.
- Planning a client’s workouts also needs the client’s permission for that coach to plan them.
- Each read of a client is recorded in that client’s access log, as it is on the website and in the apps.
Workouts a Coach Planned
An application reading a client’s own calendar through the Planned Workouts API sees the workouts their coach planned beside their own. Such a workout has a source of Coach, and while that coach still coaches the client, including while the coaching is paused, its byCoach is true.
While byCoach is true the workout is the coach’s to change. The client may only mark it skipped or not skipped, by sending skipped, and skipReason if there is one, and nothing else to Update a Planned Workout; any other change, and a delete, is refused with a 403. Offer the client a way to skip it rather than to edit it.
Once the coaching ends, or the coach’s plan lapses, byCoach is false and the workout is the client’s, to change or delete like any other. Its source still says Coach.