Wearable Data API
A wearable data API is a single interface that lets your app read health and fitness data from many different wearables and sensors without integrating each one separately. Terra is a wearable data API that connects to 500+ sources — Apple Health, Garmin, Fitbit, Oura, WHOOP and more — and returns their data in one normalized schema.
What a wearable data API does
Every wearable speaks its own language: a different API, a different auth flow, a different data format — and some, like Apple Health, have no server API at all. A wearable data API sits in front of all of them so your app talks to one interface. You ask for sleep, heart rate, or workouts once, and get it back the same way no matter which device recorded it.
- Connects to many wearables and sensors through one integration instead of dozens.
- Handles the OAuth and authentication with every provider on your behalf.
- Normalizes each provider's data into a single, consistent schema.
- Delivers new data to your backend in near real time by webhook.
How Terra's wearable data API works
Users connect once
Drop in the Terra auth widget or SDK and your users authenticate their device in a few taps. Terra manages the OAuth flow, tokens, and re-authentication with every provider, so you never touch a provider's login.
Data arrives by webhook
As new activities, sleep, and body metrics land, Terra pushes them to your backend in near real time. Every payload is signed with HMAC and retried on failure — no polling loops to build or maintain.
One schema, every source
Whether the data came from an Oura ring or a Garmin watch, it arrives in the same normalized shape. Sleep stages, heart rate, HRV, workouts and more map to consistent fields, so you write your logic once.
One API, every kind of health product
Coaching & fitness apps
Pull workouts, heart rate, and recovery from whatever device your athletes already wear, and turn it into personalized training without building a device team.
Health & wellness apps
Bring sleep, activity, nutrition, and body composition into one place to power habit tracking, insights, and engagement across your whole user base.
Insurers & research
Collect consented, longitudinal health data at scale — for wellness programs, clinical studies, and risk models — with HIPAA, GDPR, and SOC 2 Type II compliance built in.
Normalized data, ready to use
Every source maps to the same schema, so you parse once. This is a sleep record delivered to your webhook — the shape is identical whether it came from Oura, Garmin, or Apple Health. Sleep stages, heart-rate summaries, and metadata are already broken out for you.
{
"status": "success",
"type": "sleep",
"user": {
"user_id": "0d2b3f9a-8c41-4e2b-b0f1-6a3d9c1e77aa",
"provider": "OURA",
"reference_id": "your-app-user-42"
},
"data": [
{
"metadata": {
"start_time": "2026-07-06T23:14:00+00:00",
"end_time": "2026-07-07T07:02:00+00:00"
},
"sleep_durations_data": {
"asleep": {
"duration_deep_sleep_state_seconds": 5400,
"duration_REM_sleep_state_seconds": 6120,
"duration_light_sleep_state_seconds": 12480
},
"awake": { "duration_awake_state_seconds": 900 }
},
"heart_rate_data": {
"summary": { "avg_hr_bpm": 52, "min_hr_bpm": 46 }
}
}
]
}Frequently asked questions
Do I need each provider's own API to use Terra?
No. Terra maintains the integrations for you and manages the OAuth and authentication flow with every provider. You integrate Terra once and get access to all 500+ sources, rather than registering for and maintaining each provider's developer program yourself.
How is Apple Health different from the other integrations?
Apple Health, Samsung Health, and Google Fit have no web API — their data lives on the phone. Terra reaches them through its mobile SDKs for iOS, Android, React Native, and Flutter, while cloud providers like Garmin, Oura, and WHOOP connect server-to-server. Either way, the data comes back in the same normalized schema.
Does Terra deliver data by webhook or polling?
Webhooks are the primary delivery method. Terra pushes new activities, sleep, and body-metric updates to your backend as they become available, so you don't run polling loops. You can also request historical data on demand for a user when you need to backfill.
Can I pull historical data for a user?
Yes. Alongside the real-time webhook stream, Terra lets you retrieve a user's past data so you can enrich models, backfill a new signup's history, or provide deeper insights from day one.
What health data types does the API return?
Terra normalizes 5,000+ metrics across sleep stages, heart rate, HRV, VO2max, SpO2, continuous glucose, nutrition, workouts, body composition, and menstrual cycle — mapped to a consistent schema regardless of which device recorded them.
How does Terra handle normalization across devices?
Every provider reports data in its own format. Terra maps each one into a single standardized schema, so a sleep record from an Oura ring and one from a Garmin watch expose the same fields. You write your logic against Terra's schema once instead of parsing per provider.
Is the wearable data API compliant for health data?
Yes. Terra is HIPAA compliant, GDPR compliant, and SOC 2 Type II certified, and all health data is encrypted in transit and at rest. Users grant explicit consent when they connect a device.
How many wearables and sources does Terra support?
Terra connects to 500+ wearables, sensors, fitness apps, and blood-testing providers through one integration — including Apple Health, Garmin, Fitbit, Google Fit, Samsung Health, Oura, WHOOP, Polar, Strava, Withings, and hundreds more.
Cookie Preferences
Crunch Time: Embrace the Cookie Monster Within!
We use cookies to enhance your browsing experience and analyse our traffic. By clicking “Accept All”, you consent to our use of cookies according to our Cookie Policy. You can change your mind any time by visiting out cookie policy.