Thrive AI Health
Api reference

Disconnect a linked device

Revokes provider tokens / deletes credentials and purges historical data for the member from this provider. Irreversible — re-linking starts a fresh backfill from the provider's earliest available data.

DELETE
/v1/users/{user_id}/devices/{provider_slug}

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
provider_slug*Provider Slug

Header Parameters

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

Response Body

application/json

curl -X DELETE "https://loading/v1/users/497f6eca-6276-4993-bfeb-53cbbbba6f08/devices/string"
Empty
{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

List devices currently linked to the user

Paginated list of every provider the member has connected. `status=error` flags providers whose credentials have broken (typically a partner-side reconnect prompt).

Member's credentials for the health-data read API

Returns credentials the partner's mobile/web app can use to read health data directly from the underlying health-data service when lower-latency reads are needed than the Partner API provides. Treat the token as a member-level secret; do not log it.