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.
Path Parameters
Query Parameters
Header Parameters
Response Body
application/json
application/json
curl -X GET "https://loading/v1/devices/string/oauth-url?link_token=string"{
"data": {
"oauth_url": "string"
}
}{
"detail": [
{
"loc": [
"string"
],
"msg": "string",
"type": "string"
}
]
}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.
Register a native health platform (Apple Health / Health Connect)
Called after the partner's app obtains OS-level health permissions. Creates the user link with the underlying health-data service and triggers the historical backfill. Partners poll `GET /v1/users/{user_id}/devices/{provider_slug}/status` to track backfill completion.