Google Health Connect API integration
Mobile SDKOn-device only. This requires your own mobile app — there is no cloud API for it.
Health Connect is Android's on-device health data store and the successor to Google Fit. This matters urgently: the Google Fit APIs have been deprecated, and products still calling them are on a clock.
Like HealthKit, Health Connect is on-device. There is no cloud endpoint to call, so an Android app is a prerequisite. Unlike HealthKit, it is a separate system component rather than a built-in framework, which means availability varies by Android version and by whether the user has it set up.
WearLink's Kotlin SDK reads Health Connect records and pushes them into the same normalised pipeline as the cloud providers. If you are migrating off Google Fit, this is the replacement path.
How the Google Health Connect integration works
- Authentication
- On-device Android permissions
- Sync model
- SDK push from your Android app.
- API base
- On-device (Health Connect) — no cloud API
- Integration type
- Mobile SDK
Google Health Connect data available through WearLink
Everything below arrives in the shared normalised schema. The same field names and units apply whether the record came from Google Health Connect or from any other provider, so your scoring, charting and storage code is written once.
- Steps
- Heart rate
- Sleep
- Workouts
- Whatever else the user grants
Webhook events you can subscribe to
steps.createdheart_rate.createdsleep.createdworkout.createdConnect a Google Health Connect user
Two calls: create a connect session for your end user, then read their normalised data. You never handle Google Health Connect OAuth credentials, token refresh or webhook registration.
# 1. Create a connect session for your end-user
curl -X POST https://wearlink.io/api/v1/connections/session \
-H "Authorization: Bearer $WEARLINK_API_KEY" \
-H "Content-Type: application/json" \
-d '{"user_id": "'"$USER_ID"'", "provider": "google-health-connect"}'
# → { "connect_url": "https://wearlink.io/widget/connect?token=..." }
# Redirect the user there; they authorise google-health-connect and land back on your redirect_uri.
# 2. Pull normalised data whenever you want
curl -H "Authorization: Bearer $WEARLINK_API_KEY" \
"https://wearlink.io/api/v1/users/$USER_ID/summaries?provider=google-health-connect&days=7"What makes the Google Health Connect API hard to integrate directly
These are the things that turn an estimated one-week integration into a one-month one. They are worth knowing whether you use WearLink or build it yourself.
Google Fit is deprecated — migrate
The Google Fit APIs are being retired in favour of Health Connect. Anything still built on Fit needs a migration plan, not a monitoring plan.
On-device only
No server API. Without an Android app you cannot read Health Connect data.
Availability is not universal
Health Connect depends on Android version and user setup. Your app needs a graceful path for devices where it is absent.
It aggregates other apps, so duplicates happen
The same workout can arrive from Health Connect and from its originating provider. Provider priority resolves it.
Google Health Connect API — frequently asked questions
- Is Google Fit still supported?
- The Google Fit APIs are deprecated in favour of Health Connect. New integrations should target Health Connect, and existing Google Fit integrations need a migration plan.
- Do I need an Android app for Health Connect?
- Yes. Health Connect is an on-device data store with no cloud API, so the data can only be read by an app running on the device.
- What does WearLink provide for Health Connect?
- A Kotlin/JVM SDK that reads the record types you request and pushes them into the same normalised pipeline as every cloud provider, so the backend shape is identical.
Other integrations
Start with Google Health Connect — free for up to 3 users
No credit card. Create an account, add your provider credentials once, and your users connect through a hosted widget or our mobile SDK.