Retrieve the user's ranked health priorities
Returns priorities derived from the member's intake conversation and refreshed during weekly adaptation. Default scope is `status=active`; partners can request `dismissed`, `completed`, or `outdated` to render history surfaces. The `program.updated` event signals that priorities may have changed and partners should re-fetch.
Authorization
MemberBearer Member-scoped JWT minted by POST /v1/auth/token. Required on every /v1/users/{user_id}/... route; the token's sub claim must match the path user_id.
In: header
Path Parameters
uuidQuery Parameters
"active""active" | "dismissed" | "completed" | "outdated"Header Parameters
Response Body
application/json
application/json
curl -X GET "https://loading/v1/users/497f6eca-6276-4993-bfeb-53cbbbba6f08/priorities"{
"data": [
{
"user_priority_id": "b914d843-6cad-4da3-a38d-6578893897fb",
"title": "string",
"description": "string",
"target": "string",
"domains": [
"activity"
],
"status": "active",
"rank": 1,
"created_at": "2019-08-24T14:15:22Z",
"updated_at": "2019-08-24T14:15:22Z"
}
]
}{
"detail": [
{
"loc": [
"string"
],
"msg": "string",
"type": "string"
}
]
}Member's progressive-onboarding state
Returns eligibility, aggregate completion counts, and the full task list. Single-call source of truth for partner-side onboarding UI — render task list, progress count, and completion state from one response.
List health actions for a user
Paginated list of scheduled health actions. Filter by `status` and/or a `start_date`/`end_date` date window. `sort_by` defaults to `scheduled_at` ascending — typical partner usage is `sort_by=scheduled_at&sort_order=asc` for the upcoming-actions feed.