Browse the docs

Provider guide

Health Connect: no portal app, your Android app reads it
Access Open, from your own Android app on the member's phone. There is no cloud API
Cost Google Play developer account, $25 one-time [MEM]; organisation account for the company name [MEM]
Approval Play Console health apps declaration reviewed with the release [MEM]
Managed app Not applicable
Latido slug health_connect
How data arrives Your app uploads to POST /v1/members/{id}/ingest

Nothing to paste into Latido's provider settings. Latido's native Android SDK is not available yet; your app reads Health Connect and posts to the ingest endpoint through your backend.

Checklist

  1. Add androidx.health.connect:connect-client and declare the android.permission.health.READ_* permissions you need in the manifest (e.g. READ_EXERCISE, READ_STEPS, READ_HEART_RATE, READ_SLEEP, READ_WEIGHT, READ_BLOOD_GLUCOSE) [MEM].
  2. Add the permissions-rationale activity Health Connect links to (your privacy policy screen) [MEM].
  3. For history older than 30 days before the first grant, request READ_HEALTH_DATA_HISTORY; for background sync, READ_HEALTH_DATA_IN_BACKGROUND [MEM].
  4. Sync with getChanges(changesToken) and upload batches to Latido's ingest endpoint.
  5. In Play Console, complete the Health apps declaration: each permission and why you need it [MEM].

Gotchas

  • HRV is RMSSD here (unlike Apple's SDNN).
  • Group by dataOrigin.packageName to dedupe: Samsung Health, Garmin, Oura, Fitbit and Zepp all write into Health Connect.

Sources