v1 — REST + signed event streams

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.

Capabilities

What you can build

One API surface covers everything — ingest wearable data, surface coaching nudges, analyze labs, render health insights in your app.

Quickstart

Five steps to your first call

From onboarding credentials to a live member-scoped request.

  1. 1
    Receive credentials

    Your onboarding contact provisions two secrets per environment: a taih-tenant-key and an event-signing HMAC secret. Store both in a backend secret manager.

  2. 2
    Create your first member

    POST /v1/users with the tenant key returns the canonical user_idyou'll use for every member-scoped call.

  3. 3
    Mint a member token

    Exchange user_id for a short-lived bearer token via POST /v1/auth/token. TTL: 1 hour.

  4. 4
    Make a user-scoped call

    Send authorization: Bearer <token> to any /v1/users/{user_id}/… endpoint. A good first call is GET …/health-profile.

  5. 5
    Register 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"
Core concepts

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.