Garmin API
Integration
The Garmin Connect API covers activities, HRV, sleep, stress, and body battery from hundreds of devices. Open Wearables handles OAuth, push notification callbacks, and data normalization. One unified API for your app.
What you get from the Garmin Connect API.
Run, bike, swim, strength, 100+ types
Resting, average, max
Heart rate variability
Stages, duration, score
Energy level, 0-100
Daily stress level
Daily totals, floors climbed
Periodic estimate
During sleep and activity
Weight, BMI, body fat
How Garmin API integration works.
User connects their Garmin account
Open Wearables handles the Garmin Connect API OAuth flow. Your users authorize access through Garmin's standard consent screen. Token management is handled automatically.
Data is normalized to a unified schema
Activity data, sleep metrics, heart rate, HRV, stress, and body composition from Garmin are ingested and mapped to Open Wearables' unified health data schema. Consistent structure across all connected providers.
Your application calls one unified API
The same endpoints work for every provider. No Garmin-specific parsing logic, no managing Garmin's push notification callbacks directly.
Garmin is just the start.
One unified health data API, every provider. Plus health scores and AI reasoning.
All providers, one schema
Whoop, Oura, Strava, Apple Health, Polar, Suunto, Samsung Health, Google Health Connect. Same endpoints, same data format.
See all providers →Open health scores
Sleep, recovery, strain, stress, HRV, VO2 max. Open algorithms you can audit and tune for your population.
Explore scores →AI reasoning engine
MCP server for any LLM. Detect trends, flag anomalies, build coaching profiles for wellness, performance, or clinical use cases.
Learn more →Open Wearables vs SaaS vs native Garmin API.
| Aspect | Native Garmin API | SaaS APIs | Open Wearables |
|---|---|---|---|
| OAuth implementation | You build and maintain it | Handled by provider | Handled by Open Wearables |
| Push notification callbacks | You build and host callback endpoints | Handled by provider | Handled by Open Wearables |
| Data normalization | Garmin-specific data format | Unified schema, vendor-hosted | Unified schema, self-hosted |
| Multi-provider support | Separate integration per provider | One API, vendor infrastructure | One unified API, your infrastructure |
| Per-user pricing | No platform fee | Charged per connected user | $0 per user |
| Data ownership | You own all data | Vendor stores your users' data | You own all data |
| API version changes | Your team tracks and adapts | Provider absorbs upstream changes | Open Wearables absorbs upstream changes |
← scroll to see all →
Why Open Wearables for Garmin.
Garmin Connect API, without the complexity
The Garmin Connect API uses push notification callbacks for real-time data delivery. Open Wearables hosts and manages those callbacks so you don't have to build or maintain that infrastructure.
The broadest wearable data set
Garmin devices capture more data types than almost any other consumer wearable. Activities, HRV, sleep, stress, body battery, VO2 max, body composition. Open Wearables exposes all of it.
Works across the full Garmin device range
From entry-level Forerunner to Fenix and Epix. Open Wearables integrates with Garmin via the Health API, which covers the full Connect ecosystem regardless of device model.
Combine Garmin with other providers
Pair Garmin activity and HRV data with Whoop recovery scores or Oura sleep in one query. One schema, every device.
Up and running in minutes.
GET /v1/events/workouts
{
"date": "2026-01-15",
"source": { "provider": "garmin", "device": "Fenix 7X" },
"type": "run",
"distance_m": 12400,
"hrv_rmssd_ms": 55.2,
"body_battery_end": 42,
"stress_avg": 28
}
Open Wearables is open-source and self-hosted. To use the Garmin integration, apply for Garmin Health API access through the Garmin Developer Portal and configure credentials in your deployment.
Garmin health data in your app,
without the integration overhead.
Open Wearables handles OAuth, push callbacks, and normalization. MIT licensed. $0 per user.
Common questions.
Do I need Garmin API credentials?
Yes. You need to apply for Garmin Health API access through the Garmin Developer Portal. Open Wearables handles the OAuth flow and data layer, but the credentials are yours to obtain directly from Garmin.
What Garmin metrics does Open Wearables expose?
Activities, heart rate, HRV, sleep, stress, body battery, steps, VO2 max, body composition, and respiration rate. Full schema is in the docs.
Does Open Wearables support Garmin's push notification system?
Yes. Open Wearables handles Garmin's push notification callbacks and syncs new data automatically. Your application does not need to host or manage callback endpoints directly.
Which other providers can I connect alongside Garmin?
Open Wearables currently integrates with Polar, Whoop, Strava, Apple Health, Samsung Health, Google Health Connect, Suunto, and Oura. All providers share the same unified API schema.
Is Open Wearables production-ready?
Yes. Open Wearables is actively maintained and used in production. Check the GitHub releases for the current status of each provider integration.
Open Wearables is built and maintained by Momentum, a digital health agency reshaping healthcare through technology. Since 2016, they have been turning medical discoveries into compliant, scalable digital solutions. Momentum offers commercial services on top of Open Wearables for teams that need custom integrations, enterprise deployment, or SLA-backed support.
themomentum.ai →Other integrations
One API. Every provider. Zero per-user fees.
Deploy Open Wearables on your infrastructure. MIT licensed. Self-hosted.
