List metrics
list_metricsThe metrics available to one person (yours by default, an athlete's when athlete is passed), including Nolio metrics hidden from their personal display: definitions only, not values. Each entry carries id (mti_…), key, unit and is_wb_compatible. Its values are on metrics/values/ with item=<id> via nolio_api_read, except an entry with a non-null computation: it is aggregated from workouts and never stored, read it on metrics/computed/ with item=<id>. metrics/records/ is another world, the best efforts held over a duration or a distance (power profile, best 10 km pace). A metric of yours missing from an athlete's list is not enrolled yet: write its value for them anyway (metrics/values/ with athlete), the first value enrolls them, unless it is aggregated from workouts (a count, sum or average over sessions), which is refused. A %-metric workout target cites the key (e.g. "FTP") of an entry with is_wb_compatible true; the athlete does not need a value yet, the target resolves once they have one. Check unit fits how the sport is targeted (a W metric on a pace-based run is usually a mismatch). A catalogue runs to hundreds of entries: pass q when you look for one.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Keeps the metrics whose key contains this text (accents, spaces and case ignored): "vma" finds VMA. | |
| athlete | No | Athlete public id (usr_…). Omit for your own metrics. | |
| is_wb_compatible | No | true: only metrics a %-metric workout target can cite; false: only the others. Omit for all. |