Provider status
What WearLink can connect today, not someday
Most vendors publish a logo wall. This page separates providers an end-user can connect right now from those still waiting on vendor approval, and checks itself against the running API on every load.
5
live cloud providers
3
on-device SDK sources
6
in vendor onboarding
Checking the live API…
| Provider | Category | Status | Notes |
|---|---|---|---|
| Fitbit | Cloud OAuth | Connectable now | — |
| Oura | Cloud OAuth | Connectable now | — |
| Strava | Cloud OAuth | Connectable now | Webhook subscription registered (id 342762) |
| WHOOP | Cloud OAuth | Connectable now | — |
| Withings | Cloud OAuth | Connectable now | OAuth configured; provider-side production tier not yet confirmed |
| Apple Health | Mobile SDK | Mobile SDK · on-device | Backend ready; iOS SDK skeleton ships in Swift package |
| Google Health Connect | Mobile SDK | Mobile SDK · on-device | Backend ready; Android SDK skeleton ships in Kotlin package |
| Samsung Health | Mobile SDK | Mobile SDK · on-device | Backend ready; Android SDK skeleton ships in Kotlin package |
| Dexcom | Cloud OAuth | Provider onboarding | OAuth application pending |
| Eight Sleep | Cloud OAuth | Provider onboarding | OAuth application pending |
| Garmin | Cloud OAuth | Provider onboarding | OAuth application pending |
| Polar | Cloud OAuth | Provider onboarding | OAuth application pending |
| Suunto | Cloud OAuth | Provider onboarding | OAuth application pending |
| Ultrahuman | Cloud OAuth | Provider onboarding | OAuth application pending |
Status is reconciled against the is_configured field of GET /api/v1/oauth/providers.
Definitions
What the three statuses actually mean
The adapter is implemented, production OAuth credentials are issued, and an end-user can complete a connection today. Data flows through the same normalisation layer as every other live provider and arrives on the same webhook events.
Apple Health, Health Connect and Samsung Health have no cloud API by design. The data lives on the phone and can only be read by an app the user has installed and granted permission to. These require the WearLink iOS or Android SDK inside your own app.
The adapter is written and tested, but the vendor has not yet approved our production OAuth application. This step is outside our control and its duration varies enormously. We would rather show you this state than imply a connection you cannot make.
Coverage
Why provider coverage is not a single number
A provider being connectable does not mean every metric is available from every device that vendor sells. Hardware generations differ. Blood oxygen, skin temperature and ECG in particular vary by model and by region, sometimes for regulatory reasons rather than technical ones. A user on an older device may never produce some of the streams their newer counterpart does.
Access tiers matter too. Fitbit requires explicit approval for intraday data, and several providers distinguish sandbox from production quotas. Where that applies we note it in the table rather than averaging it into a status.
To know whether a specific metric is available from a specific provider, the data-type pages list providers per metric, and each integration page documents that provider’s auth model, sync mechanism and the quirks that slow integrations down.
FAQ
Frequently asked questions
Which wearables can WearLink connect right now?
What does "onboarding" mean?
Why is Apple Health listed as "SDK" rather than live?
How does this page stay accurate?
Connect the providers that are live today
Free for up to 3 connected users. The hosted connect flow works from the first request, and the status above is the same one the API enforces.