create_plan
ChatGPTCreate an empty workout plan (a group of routines). Show the user the name and get confirmation first, then call once. At most 50 plans per account. Saves to the user's Reppy account; it shows up in the app signed in with the same account after its next sync.
create_routine
ChatGPTCreate a routine in a plan (at most 30 routines per plan). For each exercise send several common ENGLISH names in exerciseNames, whatever language you use with the user, and include the equipment (barbell, dumbbell, cable, machine, kettlebell, bodyweight), e.g. ["Barbell Bench Press", "Bench Press"]. The server matches them to its catalog; if an exercise does not match, nothing is saved and the error lists up to five close English names for that item: show them to the user and let the user choose, then call again. If the user means one of their own exercises, the name they gave it also works in exerciseNames; if several of their own exercises share a name, the error lists them with exerciseId, so call again with that exerciseId (instead of exerciseNames). Weights are kilograms. Limits: 1-50 exercises, 1-20 sets, reps 1-999, weight 0-1000 kg, rest 10-600 s in steps of 10 (default 60), name 1-30 characters. Show the user the final routine and get an explicit yes first, then call once. Saves to the user's Reppy account; it shows up in the app signed in with the same account after its next sync.
get_current_selection
ChatGPTGet the plan and routine the user has selected in the app (the one they will do next). Fields are null if nothing is selected or it was deleted.
get_exercise_stats
ChatGPTStats for one exercise from the user's finished workouts: workout count, completed sets, volume (kg x reps), last performed, best set and per-workout history. Identify the exercise with several common English names (include equipment), whatever language you use with the user, or with exerciseId. All times are ISO 8601 instants as sent by the user's device, normally in UTC (suffix Z) but possibly with an explicit offset such as +09:00: the server does not know the user's time zone. Honour an explicit offset, and convert the rest to the user's local time zone before showing them (ask the user for the time zone if you do not know it); never present a UTC clock time as local time.
get_plan
ChatGPTGet one workout plan with its routines. Weights are kilograms.
get_routine
ChatGPTGet one routine: exercises in order with English catalog names, target sets (reps, kg) and rest seconds. To keep an exercise when updating the routine, pass its exerciseId in exerciseNames.
get_workout
ChatGPTGet one finished workout: exercises as recorded, sets (reps, kg, completed), notes, duration and summary. All times are ISO 8601 instants as sent by the user's device, normally in UTC (suffix Z) but possibly with an explicit offset such as +09:00: the server does not know the user's time zone. Honour an explicit offset, and convert the rest to the user's local time zone before showing them (ask the user for the time zone if you do not know it); never present a UTC clock time as local time.
list_plans
ChatGPTList the user's workout plans with their routines (exercises, target sets, rest). Each routine exercise has its English catalog name. Weights are kilograms.
list_workouts
ChatGPTList finished workouts, newest start first, with sets (reps, kg, completed), notes and a summary. Optionally filter by time range and by one exercise (exerciseNames: several common English names, or exerciseId). All times are ISO 8601 instants as sent by the user's device, normally in UTC (suffix Z) but possibly with an explicit offset such as +09:00: the server does not know the user's time zone. Honour an explicit offset, and convert the rest to the user's local time zone before showing them (ask the user for the time zone if you do not know it); never present a UTC clock time as local time.
update_routine
ChatGPTReplace a routine’s name and whole exercise list (cannot be undone). Read it with get_routine first; to keep an existing exercise, pass its exerciseId in exerciseNames. For each exercise send several common ENGLISH names in exerciseNames, whatever language you use with the user, and include the equipment (barbell, dumbbell, cable, machine, kettlebell, bodyweight), e.g. ["Barbell Bench Press", "Bench Press"]. The server matches them to its catalog; if an exercise does not match, nothing is saved and the error lists up to five close English names for that item: show them to the user and let the user choose, then call again. If the user means one of their own exercises, the name they gave it also works in exerciseNames; if several of their own exercises share a name, the error lists them with exerciseId, so call again with that exerciseId (instead of exerciseNames). Weights are kilograms. Limits: 1-50 exercises, 1-20 sets, reps 1-999, weight 0-1000 kg, rest 10-600 s in steps of 10 (default 60), name 1-30 characters. Show the user the final routine and get an explicit yes first, then call once. Saves to the user's Reppy account; it shows up in the app signed in with the same account after its next sync.