Retrieve the user record
Read the partner-facing user record (UUID + `UserProfile` block). For a one-call dashboard view that also includes location, privacy, and connected devices, use `GET /v1/users/{user_id}/health-profile` instead.
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
uuidHeader Parameters
Response Body
application/json
application/json
curl -X GET "https://loading/v1/users/497f6eca-6276-4993-bfeb-53cbbbba6f08"{
"data": {
"user_id": "a169451c-8525-4352-b8ca-070dd449a1a5",
"profile": {
"name": "string",
"email": "user@example.com",
"phone": "string",
"timezone": "string",
"birthday": "string",
"weight": 0,
"weight_unit": "kg",
"height": 0,
"height_unit": "cm",
"preferences": "string",
"pre_existing_conditions": [
{}
],
"gender": "male",
"ethnicity": "string"
}
}
}{
"detail": [
{
"loc": [
"string"
],
"msg": "string",
"type": "string"
}
]
}Create a partner-linked user
Register a partner-scoped `user_id` (UUID) so subsequent member-scoped calls can be routed against it. `user_id` is the only required field; `first_name`, `last_name`, and `email` are optional seed values. The server keeps an internal identifier but never exposes it — the partner-supplied `user_id` is the canonical handle and is reused in every `/v1/users/{user_id}/*` path going forward.
Partial update of user profile
Update a subset of profile attributes. Omitted fields are left unchanged. Returns `204 No Content` on success — partners read the updated state via `GET` on this resource.