Thrive AI Health
Api reference

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.

PATCH
/v1/users/{user_id}

Authorization

MemberBearer
AuthorizationBearer <token>

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

user_id*User Id
Formatuuid

Header Parameters

org-id?string|null
x-user-id?string|null
x-request-id?string|null
traceparent?string|null
Idempotency-Key?|null

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

curl -X PATCH "https://loading/v1/users/497f6eca-6276-4993-bfeb-53cbbbba6f08" \  -H "Content-Type: application/json" \  -d '{}'
Empty
{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

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.

Delete the user and all associated data

Irreversible from the partner perspective. All member-scoped data owned by Thrive AI Health is purged. Returns `204 No Content`. Member-scoped — the caller must hold a valid bearer for `user_id`. A separate org-admin delete endpoint is planned for partner-driven account removals (e.g. offboarding) that happen without the member online.