Ultrahuman API
Integration
The Ultrahuman API provides recovery, sleep, HRV, skin temperature, and metabolic data from the Ultrahuman Ring AIR. Open Wearables handles OAuth, token refresh, and normalization. One unified API for your app.
What you get from the Ultrahuman API.
Daily readiness, 0-100
Nightly sleep quality score
Heart rate variability during sleep
Daily measurement
Breaths per minute during sleep
Nightly deviation from baseline
Light, deep, REM, awake
Continuous glucose monitoring
Daily activity and movement data
How Ultrahuman API integration works.
User connects their Ultrahuman account
Open Wearables handles the Ultrahuman OAuth 2.0 flow. Your users authorize access through Ultrahuman's consent screen. Token lifecycle is managed automatically.
Data is normalized to a unified schema
Ultrahuman recovery scores, sleep data, HRV, skin temperature, and CGM data 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 Ultrahuman-specific parsing logic in your codebase. No managing token expiry or Ultrahuman API versioning.
Ultrahuman is just the start.
One API, every provider. Plus health scores and AI reasoning.
All providers, one schema
Oura, 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 Ultrahuman API.
| Aspect | Native Ultrahuman 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 | Ultrahuman-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 Ultrahuman.
Recovery and metabolic data combined
Ultrahuman Ring AIR tracks recovery, HRV, and sleep alongside optional CGM glucose data. Open Wearables exposes all of it through one unified API.
Automatic token refresh
Ultrahuman OAuth tokens expire. Open Wearables handles the full token lifecycle so your users stay connected without re-authenticating.
Skin temperature deviation
Ultrahuman's nightly skin temperature tracking is a key biometric for recovery baselines. Open Wearables normalizes it alongside HRV and sleep data in the same schema.
Combine with other providers
Pair Ultrahuman recovery data with Garmin activity data or Oura sleep scores in one query. One schema, every device.
Up and running in minutes.
GET /v1/events/sleep-sessions
{
"date": "2026-01-15",
"source": { "provider": "ultrahuman" },
"sleep_score": 79,
"recovery_score": 84,
"hrv_rmssd_ms": 62.4,
"skin_temp_deviation_c": -0.1,
"deep_sleep_min": 88
}
Open Wearables is open-source and self-hosted. To use the Ultrahuman integration, apply for access through the Ultrahuman developer portal and configure credentials in your deployment.
Ultrahuman recovery and sleep 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 Ultrahuman API credentials?
Yes. You need to apply for API access through the Ultrahuman developer portal. Open Wearables handles the OAuth flow and data layer, but the credentials are yours to obtain directly from Ultrahuman.
What Ultrahuman metrics does Open Wearables expose?
Recovery score, sleep score, HRV, resting heart rate, respiratory rate, skin temperature deviation, sleep stages, movement data, and CGM glucose data where available. Full schema is in the docs.
Does Open Wearables handle Ultrahuman token refresh automatically?
Yes. Open Wearables manages OAuth token lifecycle including refresh. Your application queries Open Wearables without needing to handle Ultrahuman token expiry directly.
Which other providers can I connect alongside Ultrahuman?
Open Wearables currently integrates with Oura, 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.
