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.
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
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
curl -X POST "https://loading/v1/users/497f6eca-6276-4993-bfeb-53cbbbba6f08/devices/actions/register" \ -H "Content-Type: application/json" \ -d '{ "platform": "apple_health_kit" }'{
"data": {
"provider_slug": "string",
"health_data_user_id": "string",
"backfill_status": "pending"
}
}{
"detail": [
{
"loc": [
"string"
],
"msg": "string",
"type": "string"
}
]
}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.
Get a link token to start an OAuth or Cloud Link connection
First step of an OAuth flow: returns a short-lived token scoped to the member + provider. Pass the token to `GET /v1/devices/{slug}/oauth-url` (for the standard OAuth redirect flow) or to a hosted link UI (for Cloud Link).