OAuth (cloud)

Google Health API API Integration

The cloud path of Google Health — server-side OAuth access to a user's aggregated health data across their connected Android apps.

What You Get

Data available from Google Health API

Heart Rate

Steps

Distance

SpO2

Respiratory Rate

Body Measurements

Full Sleep Staging

~150 Exercise Types

How It Works

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

Rabts maps Google Health API'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

Server-side OAuth plus notify-only webhooks — a webhook tells Rabts a window of data changed, then Rabts pulls it.
Data can reconcile across every app contributing to a user's Google Health profile, matching what the native Google Health app shows.
~150 exercise types mapped to Rabts' unified workout taxonomy.
Requires Google's CASA OAuth verification for production access — a Google platform requirement for any app in this category.

Example

bash

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

FAQ

This is the cloud/server-side path (OAuth); Health Connect is the on-device Android SDK path. Rabts supports both under one Google integration.

A third-party security assessment Google requires for apps requesting sensitive health scopes — a Google requirement independent of Rabts.

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