Oura Ring API: at a glance
Summary based on publicly available vendor documentation. Vendor terms, endpoints and limits change; we verify them against current documentation at the start of every project.
- Integration methods
- Oura API v2 cloud REST API
- OAuth 2.0 applications (recommended by Oura)
- Webhook subscriptions notifying your endpoint of data updates
- Business and research programs available from Oura by agreement
- Data types
- Daily sleep scores and detailed sleep periods
- Readiness
- Daily activity
- Heart rate time series
- Daily SpO2
- Stress and resilience
- Workouts, tags and ring configuration
- Authorization requirements
- User consent through OAuth for each requested scope
- Scopes grouped by data category
- Users can revoke access from their Oura account
- Personal access tokens deprecated; OAuth recommended
- Developer approval & agreements
- Registered OAuth application with Oura
- Review by Oura may be required to exceed initial user limits
- Business or research programs under separate agreement
- Terms and limits verified against current Oura documentation at project start
- API limitations
- Data availability can depend on the member's Oura membership status
- Gen3 and Ring 4 users without an active membership have limited API data
- Applications may be capped in user numbers before review
- Data appears after the ring syncs through the Oura app
- Rate limits apply; verify current values in Oura documentation
- Healthcare use cases
- Sleep research and sleep health programs
- Recovery and readiness monitoring
- Clinical research and decentralized trials
- Post-discharge monitoring
- Wellness and employer programs
Integration Methods
Oura integrations use the API v2 with OAuth 2.0. Users authorize your application through Oura's consent page, and your backend stores and refreshes tokens securely. Data is requested from REST endpoints by date range and category.
Webhook subscriptions let Oura notify your endpoint when data for a user is created, updated or deleted, so your backend fetches only what changed. This reduces polling and helps stay within rate limits. Subscriptions need to be renewed before they expire, which we automate.
- OAuth 2.0 authorization with secure token storage
- Webhook receivers with verification and renewal
- Date-range fetches triggered by notifications
- Handling of updated and deleted records
Data Types
The API exposes daily sleep, readiness and activity summaries, detailed sleep periods, heart rate time series, daily SpO2, stress and resilience, workouts, user tags and ring configuration. Sleep and recovery data are the most common reason healthcare and research teams integrate Oura.
Scores such as sleep and readiness are calculated by Oura's algorithms, which can change over time. We store underlying measurements alongside scores where available and record when data was retrieved, so analyses can account for algorithm updates.
API Limitations
Data availability can depend on the member's Oura membership. Gen3 and Ring 4 users without an active membership have limited data available through the API, which affects study design and participant requirements. We confirm the current rules with Oura before enrolment begins.
Data reaches Oura's servers after the ring syncs through the Oura app, so freshness depends on how often members open the app. Rate limits apply to API requests and are checked against current documentation.
Membership dependency
Members without an active membership may expose limited data via the API.
User caps
Applications may need Oura review before connecting more users.
Sync timing
New data is available only after the ring syncs with the Oura app.
Healthcare Use Cases
Oura integrations commonly support sleep research, recovery monitoring, clinical research and decentralized trials, post-discharge follow-up and wellness programs. Oura data can be combined with sources such as Apple HealthKit or a continuous glucose monitor for broader context.
Oura data is consumer wellness data and is not a substitute for clinical-grade measurement, such as polysomnography for sleep, unless validated for the intended use. We keep provenance clear so clinical teams can interpret it appropriately.
Frequently asked questions
Can we still use Oura personal access tokens?
Oura has deprecated personal access tokens and recommends OAuth applications. Multi-user programs should be built on OAuth.
Does a participant need an Oura membership?
Data availability can depend on membership status. Gen3 and Ring 4 users without an active membership have limited API data. We confirm current rules with Oura during planning.
Is there a limit on how many users we can connect?
Oura may limit the number of users an application can connect before review. Larger programs may need Oura's business or research programs under agreement.
How do we get notified of new data?
Oura API v2 supports webhook subscriptions that notify your endpoint when data changes. Your backend then fetches the updated records.
Can Oura sleep data replace a clinical sleep study?
No. Oura data is consumer wellness data and should not replace clinical-grade measurement such as polysomnography unless validated for the specific use.