Skip to content
AiKYNETIX

Get the coach's hidden player-metric set for an activity

GET
/api/me/hidden-metrics/
curl --request GET \
  --url 'http://localhost:8000/api/me/hidden-metrics/?activity=example' \
  --header 'Authorization: Bearer <token>'

Server-side metric curation (#424). Returns the metric-group keys the signed-in coach has hidden on the player Summary for one (activity, exercise) pair — moved off device-local localStorage so the server-rendered session PDF prints the same visible set. hidden lists groupLeftRight group keys (a metric key for singletons, a bilateral stem for L/R pairs). Empty when nothing is curated. Per-admin — no owner gate.

Authorizations

Section titled “Authorizations”

Parameters

Section titled “Parameters”

Query Parameters

Section titled “Query Parameters”
activity
required
string

Activity key (e.g. running).

exercise
string

Exercise within the activity; omit for the activity-level set.

Responses

Section titled “Responses”

200

Section titled “200”
Media typeapplication/json

GET/PUT /api/me/hidden-metrics/ response — the coach’s hidden metric-group set for one (activity, exercise) pair (#424).

Server-side curation moved off device-local localStorage so the server-rendered session PDF prints the same visible set the coach curated in the player. hidden lists metric group keys (the groupLeftRight output — a metric key for singletons, a bilateral stem for L/R pairs), not raw metric keys.

object
activity
required
string
exercise
required
string
hidden
required
Array<string>
Examplegenerated
{
  "activity": "example",
  "exercise": "example",
  "hidden": [
    "example"
  ]
}

400

Section titled “400”
Media typeapplication/json
object
detail
required

Human-readable message, or a stable machine code for the cases a client branches on. The standard envelope for 400 (validation — a field-keyed object may appear instead), 401 (missing / invalid credentials), 403 (authenticated but not permitted), and 404 (absent — cross-team records are collapsed to 404 so the API never leaks the existence of another team’s data).

string
Examplegenerated
{
  "detail": "example"
}

401

Section titled “401”
Media typeapplication/json
object
detail
required

Human-readable message, or a stable machine code for the cases a client branches on. The standard envelope for 400 (validation — a field-keyed object may appear instead), 401 (missing / invalid credentials), 403 (authenticated but not permitted), and 404 (absent — cross-team records are collapsed to 404 so the API never leaks the existence of another team’s data).

string
Examplegenerated
{
  "detail": "example"
}