Whoop API
Integration
The Whoop API provides recovery, strain, HRV, and sleep data. Open Wearables handles OAuth, token refresh, and normalization. One unified API for your app.
What you get from the Whoop API.
Daily readiness, 0-100
Daily and per-activity
Score, stages, duration
Heart rate variability
Daily measurement
During sleep
Sport, duration, strain, HR
Where available
How Whoop API integration works.
User connects their Whoop account
Open Wearables handles the Whoop OAuth 2.0 flow. Your users authorize access through Whoop's standard consent screen. Token management and refresh are handled automatically.
Data is normalized to a unified schema
Whoop recovery scores, strain, sleep data, HRV, and respiratory rate are ingested and mapped to Open Wearables' unified health data schema. The same structure whether the user wears a Whoop, Garmin, or Oura.
Your application calls one unified API
The same endpoints work for every provider. No Whoop-specific integration logic in your codebase. No managing token expiry or Whoop API versioning.
Whoop is just the start.
One API, every provider. Plus health scores and AI reasoning.
All providers, one schema
Garmin, 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 Whoop API.
| Aspect | Native Whoop 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 | Whoop-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 Whoop.
Recovery-first data
Whoop's recovery and strain scores are the core. Open Wearables exposes them alongside sleep, HRV, and workout data in one normalized structure.
Automatic token refresh
Whoop OAuth tokens expire. Open Wearables handles the full token lifecycle so your users stay connected without re-authenticating.
No Whoop-specific logic
No need to learn Whoop's response format or versioning. Your application queries one schema regardless of the provider.
Combine with other providers
Pair Whoop recovery data with Garmin activity data or Oura sleep data in one query. One schema, every device.
Up and running in minutes.
GET /v1/summaries/sleep
{
"date": "2026-01-15",
"source": { "provider": "whoop" },
"recovery_score": 78,
"hrv_rmssd_ms": 62.4,
"resting_heart_rate_bpm": 52,
"sleep_performance_pct": 84
}
Open Wearables is open-source and self-hosted. To use the Whoop integration, apply for access through the Whoop developer portal and configure credentials in your deployment.
Whoop recovery 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 Whoop developer API access?
Yes. You need to apply for API access through the Whoop developer portal and obtain credentials for your application. Open Wearables handles the OAuth flow and data layer, but the credentials are yours to obtain directly from Whoop.
What Whoop metrics does Open Wearables expose?
Recovery score, strain, sleep performance, sleep stages, HRV, resting heart rate, respiratory rate, and workout data. The full schema is in the docs.
Does Open Wearables handle Whoop token refresh automatically?
Yes. Open Wearables manages OAuth token lifecycle including refresh. Your application queries Open Wearables without needing to handle Whoop token expiry directly.
Which other providers can I connect alongside Whoop?
Open Wearables currently integrates with Garmin, Polar, 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.
