SDK (Android)

Google Health Connect API Integration

Health Connect is Android's on-device health data hub — Rabts reads it via the mobile SDK, no OAuth required.

What You Get

Data available from Google Health Connect

Heart Rate & HRV (RMSSD)

Blood Pressure

SpO2

Respiratory Rate

Body Measurements

Full Sleep Staging

Steps & Distance

How It Works

The athlete authorizes access via Google Health Connect's own OAuth flow — no credentials touch your servers.

Rabts maps Google Health Connect's data into the same unified schema used across every other provider — consistent units, consistent field names.

Query it through the unified REST API, or subscribe to webhooks for real-time updates as new data arrives.

Notes & Limitations

Push-based via the Android SDK — no OAuth, since Health Connect data lives on-device.
25+ Health Connect record types mapped to Rabts' unified schema.
HRV is measured as RMSSD; SDNN isn't available through Health Connect.
Workout sessions currently carry duration, type, and timing — heart rate and calorie aggregates per session are planned.

Example

bash

curl https://api-sport.rabts.com/api/v1/users/{user_id}/timeseries \
  -H "X-Open-Wearables-API-Key: YOUR_API_KEY"

FAQ

No — Health Connect is on-device and SDK-based, unlike the cloud Google Health API which does require OAuth setup.

Any app the user has granted permission to — Samsung Health, Fitbit, Garmin Connect, and others can all write into the same Health Connect store.

Create a free account and start pulling normalized Google Health Connect data through one API.