Skip to content

Integrations

14 wearable APIs, one integration

WearLink connects 14 wearable and health-data providers and normalises all of them into one schema. Each page below covers the auth model, sync mechanism, available data and the specific things that slow that integration down.

A constellation of wearable devices connected to a central node

Connectable now (5)

Cloud OAuth providers with approved production applications. Your end-users can connect these today through the hosted flow.

Oura Ring API

Connectable now

Cloud OAuth · OAuth 2.0 authorisation code

The Oura Ring API (v2) is one of the cleaner wearable APIs to work with — the documentation is accurate and the daily-summary endpoints are stable. The complexity is not in reading it, it is in keeping it read: Oura backfills and revises data after the fact, so a sleep record you fetched this morning can legitimately change by this evening.

Sleep stages & sleep score · Readiness score · HRV (rMSSD) · Resting heart rate · +4

WHOOP API

Connectable now

Cloud OAuth · OAuth 2.0 authorisation code

WHOOP's developer API exposes the four objects the product is built around — cycles, recovery, sleep and workouts. The data is high quality and the model is coherent, which makes WHOOP a favourite for recovery and readiness products.

Recovery score · Strain · Sleep stages & sleep performance · HRV · +4

Fitbit API

Connectable now

Cloud OAuth · OAuth 2.0 with PKCE

Fitbit has the largest installed base of any dedicated wearable, which makes it the provider most consumer health products need first. It is also the API with the most historical baggage — the surface has accreted since 2011 and it shows in inconsistent date handling and endpoint shapes.

Steps · Sleep stages · Heart rate (intraday where granted) · Calories · +3

Strava API

Connectable now

Cloud OAuth · OAuth 2.0 authorisation code

Strava is the best-instrumented activity API in the consumer space and the only provider in the WearLink catalogue with a true push model — an activity upload triggers a webhook within seconds, not on a poll cycle. If your product cares about workouts rather than sleep or recovery, Strava is usually the fastest path to a working demo.

Activities & workouts · GPS routes · Heart rate streams · Power & cadence · +2

Withings API

Connectable now

Cloud OAuth · OAuth 2.0 authorisation code

Withings is the connected-scale and blood-pressure provider, which makes it the one that matters most for clinical-adjacent products — weight management, hypertension programmes, GLP-1 follow-up and remote patient monitoring. Its data is measurement-shaped rather than continuous: discrete readings taken when a user steps on a scale or straps on a cuff.

Weight & body composition · Blood pressure · Sleep · Heart rate · +1

In provider onboarding (6)

Adapters are implemented; production OAuth applications are pending vendor approval. The status page updates the moment that changes.

Garmin API

Provider onboarding

Cloud OAuth · OAuth 1.0a — Garmin has not moved to OAuth 2.0 for the Health API

Garmin has the broadest data surface of any provider in the catalogue — if a metric exists in consumer wearables, a Garmin device probably measures it. For endurance, military, occupational-health and research use cases it is frequently non-negotiable.

Steps & daily activity · Sleep stages · HRV · Stress & body battery · +5

Polar AccessLink API

Provider onboarding

Cloud OAuth · OAuth 2.0 authorisation code

Polar's AccessLink API serves a smaller but committed base — endurance athletes, coaching platforms and sports-science teams. Heart rate quality is the reason people choose it; Polar's chest straps remain a reference standard.

Training sessions · Heart rate · Steps · Calories · +1

Suunto API

Provider onboarding

Cloud OAuth · OAuth 2.0 authorisation code

Suunto is an outdoor and dive-focused brand whose cloud API centres on workout files. For mountaineering, trail and diving products it covers device categories nobody else in this list reaches.

Workouts · Heart rate · HRV · Steps · +3

Ultrahuman Ring API

Provider onboarding

Cloud OAuth · Partner API credentials

Ultrahuman is the India-headquartered smart-ring maker and the provider most relevant to South Asian consumer health products, where its installed base is meaningful in a way it is not elsewhere.

Sleep · HRV · Resting heart rate · Steps · +3

Dexcom CGM API

Provider onboarding

Cloud OAuth · OAuth 2.0 authorisation code

Dexcom is continuous glucose monitoring, and it is the provider whose data is most directly clinical. Interest has grown sharply beyond diabetes care — metabolic health, GLP-1 programmes and performance nutrition products all want CGM traces.

Continuous blood glucose · Glucose trend & rate of change · Calibration events · Device events

Eight Sleep API

Provider onboarding

Cloud OAuth · Account credentials against the client API

Eight Sleep measures sleep from the mattress rather than the wrist, which produces a genuinely different signal: no compliance problem, no charging gap, and thermal data no wearable can supply.

Sleep stages · Bed & ambient temperature · HRV · Respiratory rate · +1

FAQ

Frequently asked questions

How many wearables does WearLink support?
14 providers: Oura, WHOOP, Fitbit, Strava, Withings, Garmin, Polar, Suunto, Ultrahuman, Dexcom, Eight Sleep, Apple Health, Google Health Connect, Samsung Health. 5 cloud providers (Oura, WHOOP, Fitbit, Strava, Withings) plus 3 mobile-SDK sources are connectable today; the remaining 6 are in provider OAuth onboarding.
Do I need separate code for each wearable?
No. That is the point of the aggregation layer. Every provider normalises into the same schema — a sleep record from an Oura Ring and a sleep record from a Garmin watch are the same object with the same field names and units.
Can I get Apple Health data without an iOS app?
No, and no vendor can offer this. Apple HealthKit is an on-device framework with no cloud API. Reading it requires an iOS app the user has installed and granted permission to. The same is true of Google Health Connect and Samsung Health on Android.
How long does a wearable integration take to build in-house?
Teams typically budget one week per provider and spend three to six months across a handful, because the cost is not the first successful API call — it is OAuth refresh, webhook re-registration, backfill, deduplication across overlapping providers, and keeping up when providers change their schemas.
What does "onboarding" mean on a provider?
The adapter is implemented and tested against the vendor sandbox, but the vendor has not yet approved a production OAuth application, so end-users cannot connect it. Garmin additionally requires a commercial Health API agreement. The provider status page is reconciled against the live API so this label cannot drift.

Connect your first wearable today

Free for up to 3 connected users. No credit card. Your first API key is issued the moment you sign up.