Loki Docs
Tools › Exercises › Get an exercise

Get an exercise

get_exerciseReads
What it does
Reads only. Changes nothing.
Permission
Exercises, read exercises:read

What your assistant is told

Fetch the full record for one exercise, by its catalog slug or its numeric id. Includes form instructions, cues, primary/secondary muscles, equipment, how a set of it is counted and loaded (trackingMode, loadMode, unilateral), and what to program it with (defaultRestSeconds, defaultIncrementKg). **Read this before logging a set for it** — the three mode fields decide which number a set carries and what its weight means; log_set refuses a set that disagrees. **Every vocabulary comes back named, not as a bare slug.** Muscles, equipment, the movement pattern, the bodyRegion and each safety tag carry a slug to filter by and a name to say out loud; a tag also carries the exact claim it makes, which is what to read before deciding that "my knee hurts" means knee-safe. **progression is the ladder**, present only for the exercises that get harder by CHANGING the exercise — mostly bodyweight, core and holds. harder is the next rung up: offer it when the user tops out the rep or seconds range, because a push-up has no load to add. easier is the regression for "I can't do one yet", and sameStep is the equal alternatives on the same rung. A barbell or machine lift has no ladder at all — that one progresses by defaultIncrementKg. The user's own custom exercises have no slug, so pass the id find_exercises gave you; every catalog exercise answers to its id as well. Resolves retired exercises too, so a reference out of the user's workout history always works. Check status: when it is "deprecated" the exercise is no longer in the catalog — program mergedInto instead when it is set, and don't suggest the retired one for new work.

Parameters

  • exercisetext, requiredCatalog slug (e.g. "barbell-back-squat") or numeric id (e.g. "412", for a custom exercise).