Google Health Connect
Integration
Google Health Connect aggregates health and fitness data from Android devices and third-party apps. Open Wearables handles Android permissions, data sync, and normalization. One unified API for your backend.
What you get from Google Health Connect.
Daily totals from Android devices
Continuous from Wear OS and paired devices
Stages, duration from Android
All Android workout types
Active and basal calories
Heart rate variability
Blood oxygen from paired devices
During sleep and activity
From paired scales
From CGM or paired devices
How Google Health Connect integration works.
User grants Health Connect permissions
Open Wearables handles the Health Connect permission requests through a native Android SDK. Your users grant access via Android's standard consent screen.
Data is normalized to a unified schema
Health Connect data types are mapped to Open Wearables' unified health data schema. Steps, heart rate, sleep, workouts, and SpO2 all land in the same structure regardless of the Android source app.
Your application calls one unified API
The same endpoints work for every provider. No Health Connect-specific parsing logic, no Android platform dependencies in your backend.
Google Health Connect is just the start.
One unified health data API, every provider. Plus health scores and AI reasoning.
All providers, one schema
Garmin, Whoop, Oura, Strava, Apple Health, Polar, Suunto, Samsung Health. Same endpoints, same data format.
See all providers →Open health scores
Sleep, recovery, strain, stress, HRV, VO2 max. Open algorithms you can audit and tune for your population.
Explore scores →AI reasoning engine
MCP server for any LLM. Detect trends, flag anomalies, build coaching profiles for wellness, performance, or clinical use cases.
Learn more →Open Wearables vs SaaS vs native Health Connect SDK.
| Aspect | Native Health Connect SDK | SaaS APIs | Open Wearables |
|---|---|---|---|
| Health Connect permissions | You build and maintain the Android permission flow | Handled by provider SDK | Handled by Open Wearables SDK |
| Cloud API access | No native cloud API — data lives on-device only | Vendor-hosted REST API | Unified REST API, self-hosted |
| Data normalization | Health Connect-specific data types | Provider-defined schema | Unified schema across all providers |
| Multi-provider support | Separate integration per provider | Depends on vendor tier | One unified API for all providers |
| Per-user pricing | No platform fee | Charged per connected user | $0 per user |
| Data ownership | You own all data | Vendor stores your users' data | You own all data |
| Android version changes | Your team tracks every Android update | Vendor absorbs changes | Open Wearables absorbs upstream changes |
← scroll to see all →
Why Open Wearables for Google Health Connect.
Health Connect without the Android-only constraint
Google Health Connect has no cloud API. Open Wearables bridges the gap with a native Android SDK that reads Health Connect data on-device and syncs it to your backend over a standard REST interface.
Aggregates every Android health app
Health Connect is a hub for Android health data. Wear OS, Samsung Health, Fitbit, and dozens of third-party apps all write to it. Open Wearables reads from that hub in one integration.
No Health Connect-specific logic in your backend
Health Connect has its own permission model and data types. Open Wearables normalizes everything before it reaches your server. Your backend sees the same schema it uses for Garmin or Oura.
Combine with other providers
Pair Google Health Connect activity data with Oura sleep or Whoop recovery in one query. One schema, every device.
Up and running in minutes.
GET /v1/events/workouts
{
"date": "2026-01-15",
"source": { "provider": "google_health_connect", "device": "Pixel Watch 3" },
"type": "run",
"distance_m": 8200,
"steps": 9841,
"heart_rate_avg_bpm": 148,
"active_calories_kcal": 487
}
Open Wearables is open-source and self-hosted. The Google Health Connect integration uses a mobile SDK to sync data from Health Connect on-device.
Google Health Connect data in your app,
without the Android integration overhead.
Open Wearables handles Health Connect permissions, on-device sync, and normalization. MIT licensed. $0 per user.
Common questions.
Does Open Wearables support Google Health Connect?
Yes. Open Wearables includes a native Android SDK that integrates with Google Health Connect. Because Health Connect is on-device only with no cloud API, the SDK reads data on the user's device and syncs it to your Open Wearables backend.
Is this the same as the Google Fit API?
Google Health Connect is Google's current health data platform for Android, replacing the older Google Fit API. Open Wearables integrates with Health Connect, which covers data from Wear OS, Samsung Health, and Android health apps.
What data does Open Wearables expose from Google Health Connect?
Steps, heart rate, sleep, workouts, calories, HRV, SpO2, respiratory rate, body weight, and blood glucose from paired devices. Full schema is in the docs.
Which other providers can I connect alongside Google Health Connect?
Open Wearables currently integrates with Garmin, Polar, Whoop, Strava, Apple Health, Samsung Health, Suunto, and Oura. All providers share the same unified API schema.
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 →Other integrations
One API. Every provider. Zero per-user fees.
Deploy Open Wearables on your infrastructure. MIT licensed. Self-hosted.
