Wearable API Integrations
One platform. Every major wearable. A unified API schema for all wearable health data. Open Wearables handles OAuth, data normalization, and provider-specific complexity so your team does not have to.
All providers. One schema.
Open Wearables connects all major wearable providers through one unified REST API and normalizes every reading into a single schema, so your application uses the same endpoints no matter which device a user wears. Providers fall into two groups that differ in integration work. Cloud-based platforms like Garmin, Whoop, Oura, Polar, Suunto, Strava, Fitbit, and Ultrahuman connect over OAuth, so you register with each developer program and Open Wearables handles the flow, token refresh, and webhook ingestion. On-device platforms like Apple HealthKit, Samsung Health, and Google Health Connect require shipping a mobile SDK, because that data is only readable on the phone, but need no OAuth or program approval. Both paths produce identically shaped data, so Sleep Score and Resilience Score compute the same way across whichever combination of providers a given user has actually connected.
Garmin
Activities, HRV, sleep, stress, body battery, VO2 max, and more from the full range of Garmin Connect devices. Open Wearables handles Garmin's push notification callbacks and OAuth flow.
Whoop
Recovery score, strain, sleep performance, HRV, and resting heart rate from Whoop 4.0 and later. Token refresh and data sync handled automatically.
Oura Ring
Sleep score, readiness, sleep stages, HRV, respiratory rate, body temperature deviation, and SpO2 from Oura Ring. OAuth 2.0 handled by Open Wearables.
Strava
Activity summaries, heart rate, GPS data, elevation, power output, and webhook-triggered syncs on new workouts. Strava rate limits managed internally.
Apple Health
Heart rate, HRV, sleep, workouts, SpO2, steps, and energy data from iPhone and Apple Watch via HealthKit. Lightweight iOS SDK component handles permissions and sync.
Samsung Health
Heart rate, sleep, workouts, SpO2, stress, and body composition from Galaxy phones and Galaxy Watch devices.
Google Health Connect
Heart rate, steps, sleep, workouts, SpO2, and body measurements from Android devices via Health Connect. Lightweight Android SDK component handles permissions and sync.
Polar
Training sessions, HRV, Nightly Recharge, sleep, VO2 max, and running index via Polar AccessLink API. Covers Vantage, Ignite, Grit, Pacer, and Unite series.
Suunto
Workouts, GPS data, heart rate, altitude, cadence, and power output from Suunto devices synced to Suunto App.
Ultrahuman
Recovery score, sleep, HRV, skin temperature deviation, and metabolic data from Ultrahuman Ring AIR. OAuth and token refresh handled automatically.
Google Health API
24/7 metrics, workouts, and sleep aggregated from every source connected to a user's Google Health account, including Fitbit, Health Connect, and Google Fit. Cross-source reconciliation and webhooks handled automatically.
Fitbit
Workouts and activity data via OAuth 2.0. The Fitbit Web API is being shut down in September 2026; Open Wearables provides a direct migration path to the Google Health API.
Don't see your provider?
Request a new integration on GitHub. Open an issue and we'll review it.
At a glance.
OAuth providers
| Provider | Key data points | Status |
|---|---|---|
| Garmin | Activities, HRV, sleep, stress, body battery, VO2 max | Live |
| Whoop | Recovery, strain, sleep, HRV, resting HR | Live |
| Oura | Sleep, readiness, HRV, body temp, SpO2 | Live |
| Strava | Activities, heart rate, GPS, power | Live |
| Polar | Training, HRV, Nightly Recharge, VO2 max | Live |
| Suunto | Workouts, GPS, HR, altitude, cadence | Live |
| Ultrahuman | Recovery, sleep, HRV, skin temp, metabolic | Live |
| Google Health API | 24/7 metrics, workouts, sleep (aggregated) | Live |
| Fitbit | Workouts, activity | Sunsetting 2026 |
← scroll to see all →
SDK-based providers
| Provider | Key data points | Status |
|---|---|---|
| Apple Health | HR, HRV, sleep, workouts, SpO2, steps | Live |
| Samsung Health | HR, sleep, workouts, SpO2, stress, body composition | Live |
| Google Health Connect | HR, steps, sleep, workouts, SpO2 | Live |
← scroll to see all →
Common questions.
Do I need API credentials for each provider?
Yes. Each provider requires its own developer credentials, which you obtain directly from the provider. Open Wearables handles the OAuth flow, data normalization, and unified API layer once credentials are configured.
Can I connect multiple providers for the same user?
Yes. A single user can connect multiple providers simultaneously. All data is normalized to the same schema and accessible through one unified API, regardless of the source.
Does Open Wearables handle OAuth token refresh?
Yes. Token lifecycle management, including refresh, is handled automatically for all cloud API providers.
What does the unified API schema look like?
All provider data is normalized to a consistent structure. Activity, sleep, heart rate, HRV, and other metrics follow the same field names and types regardless of whether the data comes from Garmin, Whoop, or Oura. Full schema reference is in the docs.
Is Open Wearables production-ready?
Yes. Open Wearables is actively maintained and used in production. Check the GitHub releases for the current status of each provider integration.
Open Wearables is built and maintained by Momentum, a digital health agency reshaping healthcare through technology. Since 2016, they have been turning medical discoveries into compliant, scalable digital solutions. Momentum offers commercial services on top of Open Wearables for teams that need custom integrations, enterprise deployment, or SLA-backed support.
themomentum.ai →One API. Every provider. Self-hosted.
Deploy Open Wearables on your infrastructure. MIT licensed. Self-hosted.
Comparing options? See how Open Wearables compares to Terra, ROOK, Sahha and others →