The exercise endpoints expose the GymFlow exercise catalogue and its related muscle data. All three endpoints require a valid JWT in theDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/Lokhy87/gymApp/llms.txt
Use this file to discover all available pages before exploring further.
Authorization header — they follow the same authentication rules as the rest of the /api routes. They are typically called to populate selection lists before a user logs a workout. See Authentication for how to obtain a token.
List exercises
Returns all exercises, or a filtered subset by muscle group.GET /api/exercises
When provided, only exercises belonging to the specified muscle group are returned. Omit to return all exercises.
Unique identifier for the exercise. Use this value as
exercise_id when creating a workout.Display name of the exercise. This string must be used verbatim when querying the progress endpoint.
Filename or path to the exercise illustration. May be
null if no image is available.The ID of the muscle group this exercise belongs to. Matches the
id field returned by /api/muscle_groups.| Status | Meaning |
|---|---|
404 | No exercises exist (empty catalogue) or no exercises match the given muscle_group_id. |
List exercise–muscle mappings
Returns the join table between exercises and individual muscles, including the role each muscle plays (primary mover, secondary, etc.).GET /api/exercises_muscles
Example request
Unique identifier for this mapping record.
The muscle’s role in the exercise (for example
"primary" or "secondary").ID of the muscle involved.
ID of the exercise this mapping belongs to.
| Status | Meaning |
|---|---|
404 | No mappings found in the database. |
List muscle groups
Returns all muscle groups available in the catalogue.GET /api/muscle_groups
Example request
Unique identifier for the muscle group. Pass this as
muscle_group_id to filter exercises.Display name of the muscle group.
Filename or path to the muscle group illustration. May be
null.