Thrive AI Health Partner API
Connect your application to Thrive AI Health's platform — wearable integrations, personalized coaching, activity and sleep tracking, lab analysis, and AI-generated health insights. REST over HTTPS for synchronous calls, partner-owned message queues for async events.
What you can build
One API surface covers everything — ingest wearable data, surface coaching nudges, analyze labs, render health insights in your app.
Wearable integrations
Connect Apple Health, Health Connect, Fitbit, and more. Partner backend registers OAuth credentials once; per-user connections flow through standard link tokens.
Activity, sleep, and body metrics
Daily summaries, sub-daily timeseries, and per-sample access for steps, heart rate, HRV, sleep stages, body composition, workouts, and more.
Personalized coaching
LLM-driven text and voice coaching. Sessions, streaming events over SSE, realtime voice tokens, and structured user feedback.
AI nudges & health actions
Trigger-driven coaching moments delivered to your queue, then fetched and rendered in-app. Scheduled action reminders, card feeds, and interaction tracking.
Lab analysis
Upload clinical documents, receive structured biomarker values with reference ranges, clinical analysis, and recommendations.
Health scores & bio-age
Composite health score, biological age, trends, and projections — the aggregate read model partners use to drive member dashboards.
Five steps to your first call
From onboarding credentials to a live member-scoped request.
- 1Receive credentials
Your onboarding contact provisions two secrets per environment: a
taih-tenant-keyand an event-signing HMAC secret. Store both in a backend secret manager. - 2Create your first member
POST /v1/userswith the tenant key returns the canonicaluser_idyou'll use for every member-scoped call. - 3Mint a member token
Exchange
user_idfor a short-lived bearer token viaPOST /v1/auth/token. TTL: 1 hour. - 4Make a user-scoped call
Send
authorization: Bearer <token>to any/v1/users/{user_id}/…endpoint. A good first call isGET …/health-profile. - 5Register an event queue
For async streams (lab results, daily device data, coaching nudges), register a destination queue — AWS SQS, Azure Event Hubs, or Azure Storage Queue.
# 1. Create a member (server-to-server, tenant key).
curl -X POST https://api.thriveaihealth.com/v1/users \
-H "taih-tenant-key: $TAIH_TENANT_KEY" \
-H "content-type: application/json" \
-d '{"external_id": "partner-member-123"}'
# 2. Mint a short-lived bearer token for that member.
curl -X POST https://api.thriveaihealth.com/v1/auth/token \
-H "taih-tenant-key: $TAIH_TENANT_KEY" \
-H "content-type: application/json" \
-d '{"user_id": "$USER_ID"}'
# 3. Read the consolidated health profile.
curl https://api.thriveaihealth.com/v1/users/$USER_ID/health-profile \
-H "authorization: Bearer $ACCESS_TOKEN"Before you integrate
The ground rules: environments, auth model, data shapes, rate limits, and how async events are signed.
Versioning
Only /v1/… is currently published. Every change inside v1 is additive and backwards-compatible — breaking changes ship only in a new major version.
Deprecation policy
6-month announcement window, 12 months of maintenance-mode bug fixes, and an 18-month sunset from first announcement. Sandbox is the place to rehearse migrations before production cutovers.
Support
Operational questions, incident reports, and integration help go through your Thrive AI Health onboarding contact. Changelog updates at /docs/changelog.