Oura API
Integration
The Oura API provides sleep, readiness, HRV, and biometric data from Oura Ring. Open Wearables handles OAuth, token refresh, and normalization. One unified API for your app.
What you get from the Oura API.
Nightly score with breakdown
Light, deep, REM, awake
Daily readiness, 0-100
Heart rate variability
Daily measurement
During sleep
Nightly deviation
Blood oxygen, where available
Steps, calories, active time
How Oura API integration works.
User connects their Oura account
Open Wearables handles the Oura OAuth 2.0 flow. Your users authorize access through Oura's standard consent screen. Token lifecycle is managed automatically.
Data is normalized to a unified schema
Oura sleep scores, readiness scores, HRV, activity data, and biometrics are ingested and mapped to Open Wearables' unified health data schema. Consistent structure regardless of which provider the data comes from.
Your application calls one unified API
The same endpoints work for every provider. No Oura-specific parsing logic in your codebase. No managing token expiry or Oura API versioning.
Oura is just the start.
One API, every provider. Plus health scores and AI reasoning.
All providers, one schema
Garmin, Whoop, 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 Oura API.
| Aspect | Native Oura API | SaaS APIs | Open Wearables |
|---|---|---|---|
| OAuth implementation | You build and maintain it | Handled by provider | Handled by Open Wearables |
| Token refresh | You manage expiry and refresh logic | Handled by provider | Automatic |
| Data normalization | Oura-specific JSON response format | Provider-defined schema | Unified schema across all providers |
| Multi-provider support | Separate integration per provider | Depends on vendor tier | One unified API for all providers |
| 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 | Vendor absorbs changes | Open Wearables absorbs upstream changes |
| Maintenance burden | Ongoing per provider | Vendor-managed | Minimal |
← scroll to see all →
Why Open Wearables for Oura.
Richest sleep data on the market
Oura Ring captures sleep stages, HRV, body temperature, SpO2, and readiness in more detail than most other consumer wearables. Open Wearables exposes all of it through one unified API.
Automatic token refresh
Oura OAuth tokens expire. Open Wearables handles the full token lifecycle so your users stay connected without re-authenticating.
Body temperature deviation
Oura's nightly body temperature data is unique among consumer devices. Open Wearables normalizes it alongside HRV and sleep data in the same schema.
Combine with other providers
Pair Oura sleep data with Garmin activity data or Whoop recovery scores in one query. One schema, every device.
Up and running in minutes.
GET /v1/events/sleep-sessions
{
"date": "2026-01-15",
"source": { "provider": "oura" },
"sleep_score": 82,
"readiness_score": 76,
"hrv_rmssd_ms": 58.1,
"body_temp_deviation_c": 0.2,
"deep_sleep_min": 94
}
Open Wearables is open-source and self-hosted. To use the Oura integration, apply for access through the Oura developer portal and configure credentials in your deployment.
Oura sleep and readiness data in your app,
without the integration overhead.
Open Wearables handles OAuth, token refresh, and normalization. MIT licensed. $0 per user.
Common questions.
Do I need Oura API credentials?
Yes. You need to apply for API access through the Oura developer portal. Open Wearables handles the OAuth flow and data layer, but the credentials are yours to obtain directly from Oura.
What Oura metrics does Open Wearables expose?
Sleep score, sleep stages, readiness score, HRV, resting heart rate, respiratory rate, body temperature deviation, activity data, and SpO2. Full schema is in the docs.
Does Open Wearables handle Oura token refresh automatically?
Yes. Open Wearables manages OAuth token lifecycle including refresh. Your application queries Open Wearables without needing to handle Oura token expiry directly.
Which other providers can I connect alongside Oura?
Open Wearables currently integrates with Garmin, Polar, Whoop, Strava, Apple Health, Samsung Health, Google Health Connect, and Suunto. 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.
