Thrive AI Health
Api reference

List supported wearable providers

Returns every supported provider regardless of whether the caller has registered credentials. Safe to cache client-side. `auth_type` indicates the connection flavor (`oauth`, `credentials`, `native`); `supported_resources` lists the canonical metric slugs each provider can supply.

GET
/v1/devices

Query Parameters

limit?Limit
Default10
Range1 <= value <= 200
offset?Offset
Default0
Range0 <= value

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

application/json

curl -X GET "https://loading/v1/devices"
{
  "data": [
    {
      "slug": "string",
      "name": "string",
      "logo": "string",
      "description": "string",
      "auth_type": "oauth",
      "supported_resources": [
        "string"
      ]
    }
  ],
  "pagination": {
    "limit": 25,
    "offset": 0,
    "total": 0
  }
}
{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

Pre-signed URL for uploading files (lab documents, images)

Returns a single-use 15-minute Azure Blob SAS PUT URL. Supported `content_type` values: `application/pdf` (lab documents), `image/jpeg`, `image/png`, `image/webp` (chat attachments). Max 20 MB per upload. Pass the returned `file_url` to the downstream endpoint that consumes the file — for labs, that's `POST /v1/users/{user_id}/labs/upload`.

OAuth authorization URL for a provider

Returns the URL to redirect the member to. The partner client navigates the member to `oauth_url`; on consent, the provider redirects back to the partner-registered redirect URI. The `link_token` query param ties the authorization to the in-flight link request. Provider OAuth credentials are managed internally by Thrive AI (not partner-supplied); failures here indicate a Junction-side configuration issue rather than a missing partner setup step.