Skip to main content

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.

The History screen gives you a complete picture of every workout you have recorded. All your entries are mapped onto a FullCalendar monthly grid — on desktop — or a week list on smaller screens. Each day that contains at least one logged exercise shows the exercise name as an event label. Clicking any event or any day tile opens a detail modal listing every entry for that date, with inline edit and delete controls.

Using the history view

1

Open History from the sidebar

Navigate to History in the main navigation. The page fetches all your workout entries from GET /api/history and renders them as calendar events.
2

Find a date

Dates with logged workouts show one label per exercise. On mobile the view automatically switches to a week-by-week list for easier reading.
3

Click a date or event

Clicking any highlighted day or event label opens the Workout modal for that date. The modal lists every exercise you logged, along with its sets, reps, and weight.
4

Edit an entry

Click Edit next to any exercise in the modal. An edit form appears pre-filled with the current values. Adjust sets, reps, weight, or comments and click Save. The calendar refreshes automatically.
5

Delete an entry

Click Delete next to any exercise and confirm the prompt. The entry is permanently removed and the calendar updates immediately.

History response fields

Each item in the history list represents one saved workout entry.
FieldTypeDescription
idintegerUnique ID used for edit and delete operations
exercise_namestringDisplay name of the exercise performed
setsintegerNumber of sets recorded
repsintegerNumber of repetitions per set
weightfloatLoad in kilograms
commentsstring | nullFree-text notes attached to the entry
datestringServer timestamp in YYYY-MM-DD HH:mm:ss format
Entries are returned in the order they were created. The frontend sorts them visually by date when rendering the calendar events.

API reference

GET /api/history

curl https://api.gymflow.example/api/history \
  -H "Authorization: Bearer <token>"
[
  {
    "id": 341,
    "sets": 4,
    "reps": 8,
    "weight": 80.0,
    "comments": "Paused at the bottom on every rep",
    "date": "2026-05-19 09:14:33",
    "exercise_name": "Bench Press"
  },
  {
    "id": 342,
    "sets": 3,
    "reps": 12,
    "weight": 60.0,
    "comments": null,
    "date": "2026-05-19 09:22:01",
    "exercise_name": "Incline Dumbbell"
  }
]
The endpoint requires a valid JWT in the Authorization header. It returns only entries belonging to the authenticated user — you never see other users’ data.
Editing and deleting entries from the history view calls the same PUT /api/workouts/{id} and DELETE /api/workouts/{id} endpoints used when logging from the exercise library. See the Workouts page for the full request and response shapes.

Log a workout

Record a new exercise entry from the exercise library.

Track progress

Plot your weight-lifted over time for a single exercise.

History API

Full endpoint reference for the history resource.

Workouts API

Edit and delete endpoint reference for workout entries.

Build docs developers (and LLMs) love