The history endpoint returns every workout entry recorded by the authenticated user, with no pagination. Each object includes the exercise name as a denormalised string so no secondary request is needed to display a complete log. This endpoint requires a valid JWT. See Authentication for how to obtain a token.Documentation 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.
Get workout history
GET /api/history
This endpoint accepts no query parameters. All entries for the authenticated user are returned in the order they are stored in the database.
Example request
[] is returned when the user has no logged workouts.
Unique identifier for the workout entry. Use this with
PUT /api/workouts/{id} or DELETE /api/workouts/{id} to modify the record.Number of sets performed.
Number of repetitions per set.
Weight used. Returns
0 when no weight was recorded at logging time.Free-text notes attached to the entry.
null when none were provided.Server-side timestamp when the entry was created, formatted as
Y-m-d H:i:s (e.g. "2024-05-15 09:32:00"). This date is always set by the server and cannot be overridden by the client.Display name of the exercise performed. This is the same string that must be passed as the
exercise parameter to GET /api/progress.| Status | Meaning |
|---|---|
401 | Missing or invalid Bearer token. |