Oura Ring API Integration Guide 2026: Access and Data
CTO & Co-Founder
CTO & Co-Founder at Nirmitee.io. Architects healthcare integrations across FHIR, SMART on FHIR, ABDM and NHCX, writing from production experience taking hospital software from sandbox to go-live.

Yes, you can integrate Oura through the Oura API V2, which Oura calls "the only available integration point for Oura data". No developer fee is listed. You can build with up to 10 users before Oura must approve your app, and Oura has not published how long approval takes. Users with a Gen3 or later ring need an active Oura Membership, or the API returns nothing for them. The rule that decides most healthcare projects is the storage clause in the API agreement, which says you shall not store or cache data obtained through the MCP Server, so have counsel confirm how far it reaches before you plan to keep readings in an EHR. You need your own server, no SDK, and no mobile app of your own.
Want a team to build this for you? Our medical device integration services cover the vendor approval, the data pipeline and EHR delivery.
Oura integration at a glance
| Question | Answer |
|---|---|
| Official API? | Yes. Oura API V2 (REST, OAuth2, webhooks). V1 was removed on 22 Jan 2024. |
| Cost to the developer | No fee listed. Agreement 3(h): Oura reserves the right to charge fees. |
| Does the end user need a subscription or device? | Yes. An Oura Ring, and for Gen3 and later an active Oura Membership. |
| Same-day start? | Yes, for up to 10 users. Sandbox endpoints let you build without a ring. |
| Who approves scale-up? | Oura. "There is no limit once an application is approved." Criteria and wait time not published. |
| HIPAA / BAA | The agreement does not mention HIPAA. BAA not published. |
| Raw or summary data? | Mostly daily summaries and per-period sleep records. Heart rate is a time series. No raw PPG or accelerometer. |
| First build | About 3 weeks to a working integration (our estimate), plus legal review of storage and Oura approval. |
Integration strategies
| Route | Own mobile app? | Own server? | Vendor approval or contract? | SDK? | Latency | Supported data | Not supported | Best for |
|---|---|---|---|---|---|---|---|---|
| Oura API V2 (REST) | No. Server-side OAuth from a web page works. | Yes for the server flow. A client-side flow exists with 30-day tokens and no refresh. | No for 10 users. Oura approval beyond that. | No | After the user's Oura app syncs. Sleep needs the user to open the app. | All V2 data types listed below | Raw sensors, ECG, writes, lapsed members | Any product reading Oura data |
| Webhooks | No | Yes, public HTTPS endpoint | Same as REST | No | About 30 seconds after the app syncs | Notifications that new data is ready. You then fetch it with REST. | Heart rate, personal info and ring battery level have no webhook | Fresh data without polling. Oura calls it "the preferred way". |
| Sandbox endpoints | No | Yes | No | No | n/a | Test data in the same shape | Real users | Building before you have rings |
| Personal access tokens | Deprecated December 2025 and "no longer available for use". | |||||||
| Phone SDK | Not published. | |||||||
| Apple Health / Health Connect | Yes, the Oura app reads and writes both. Apple Health gets active energy, heart rate, sleep and stages, steps, respiratory rate, mindful minutes, weight and workouts, but not HRV. Health Connect gets active calories, distance, exercise, steps, sleep, heart rate and HRV. Gen3 and later need an active membership. | |||||||
| Aggregators, checked 10 November 2026 | Terra, Junction, Thryve and ROOK list Oura as a cloud API source. Sahha has it in public beta, sandbox only. Spike lists it with no route stated. Validic lists Oura as restricted and not taking new applications. Pricing is not published. The Oura agreement says aggregators may not store or cache User Data or Oura Data. | |||||||
| Member file download | No | No | No | No | Manual | Whatever the Membership Hub file holds | Anything ongoing | One-off research pulls by the user |
For a wellness, sleep or coaching product, use the REST API with webhooks and the server-side OAuth flow. It is free today and the data set is broad. For a healthcare buyer, use the same route, but finish the legal read of the storage clause and the competing-product clause before you design storage, and plan for users whose membership lapses mid-program. Avoid aggregators if your plan depends on storing Oura data, since the agreement singles them out.
Build it yourself, use an aggregator, or work with a partner
| Question | Build in-house | Wearable aggregator | Build with a partner (Nirmitee) |
|---|---|---|---|
| Whose Oura API app? | Yours | Depends on the aggregator. Some, such as Sahha, ask you to register your own Oura app. | Yours. We build it in your account. |
| Storage clause risk | Your counsel reads it | Highest. The agreement names aggregators and bars them from storing or caching Oura data. | Your counsel reads it. We design storage around the answer. |
| Webhooks and token renewal | You build and run them | The aggregator runs them | We build them, then hand them to you or run them |
| Data model | Oura's own fields | The aggregator's schema | FHIR Observations for your EHR or remote monitoring stack |
| Other devices later | One new build per device | Many devices through one API | Same pattern reused across devices |
| Time to first real user | Depends on your team | Depends on the aggregator's onboarding | About 3 weeks of build in our estimate, plus Oura approval past 10 users |
| Cost shape | Engineering time | Aggregator fee. Pricing for Oura on these platforms is not published. | Project fee, scoped after a call |
What data you can get
From the OpenAPI spec 1.43. All paths sit under /v2/usercollection/.
| Data (endpoint) | Scope | Granularity | History window | Push or pull |
|---|---|---|---|---|
| Daily activity (daily_activity) | daily | Daily summary | Not published | Pull, webhook |
| Daily readiness (daily_readiness) | daily | Daily summary | Not published | Pull, webhook |
| Daily sleep score (daily_sleep) | daily | Daily summary | Not published | Pull, webhook |
| Sleep periods (sleep) | daily | Per sleep period (fields such as sleep stages, HRV and respiratory rate. Full field list in the spec) | Not published | Pull, webhook |
| Sleep time recommendation (sleep_time) | daily | Daily | Not published | Pull, webhook |
| Daily SpO2 (daily_spo2) | spo2 | Daily average during sleep | Not published | Pull, webhook |
| Daily stress (daily_stress) | daily | Daily summary | Not published | Pull, webhook |
| Daily resilience (daily_resilience) | daily | Daily summary | Not published | Pull, webhook |
| Cardiovascular age (daily_cardiovascular_age) | heart_health | Daily | Not published | Pull, webhook |
| VO2 max (vO2_max) | heart_health | Per estimate | Not published | Pull, webhook |
| Heart rate (heartrate) | heartrate | Time series | Not published | Pull only. Heart rate is not in the webhook data type list. |
| Workouts (workout) | workout | Per workout | Not published | Pull, webhook |
| Sessions (session) | session | Per session | Not published | Pull, webhook |
| Tags and enhanced tags (tag, enhanced_tag) | tag | Per tag | Not published | Pull, webhook |
| Rest mode periods (rest_mode_period) | daily | Per period | Not published | Pull, webhook |
| Personal info (personal_info) | personal, email | Current profile, including weight and height | n/a | Pull |
| Ring battery level, ring configuration | Not published | Not published | Not published | Pull |
The scope and webhook columns are checked against the spec's scope list and webhook data type list (read 11 Nov 2026). Most types are daily summaries. Heart rate is a time series. Each user consents to each data type, so any type can be missing for a given user.
What is inside one Oura sleep record
The sleep endpoint gives far more than a nightly score. These fields come from the spec's sleep model.
| Field | What it holds |
|---|---|
| sleep_phase_5_min | One character per 5 minutes: 1 deep, 2 light, 3 REM, 4 awake |
| movement_30_sec | One character per 30 seconds: no motion, restless, tossing and turning, or active |
| heart_rate and hrv | Sample series. Each has an interval field that gives the seconds between samples. |
| average_hrv, lowest_heart_rate | Night values. Oura notes the API figures come from 30-second samples, while the app shows 5-minute aggregates, so they can differ from the app. |
| type | Long sleep, nap, late nap, rest or deleted. Only some types count toward daily scores. |
Readiness adds temperature_deviation, which the spec defines only as a temperature deviation in degrees Celsius, plus contributor scores from 1 to 100 for body temperature, HRV balance and previous day activity. The heart rate series tags each sample with a source: awake, rest, sleep, workout, live or session. That is how you separate workout heart rate from resting heart rate.
What you cannot get
- Any data for Gen3 and later users without an active Oura Membership. The API returns 403 and partner apps lose access.
- Raw PPG, accelerometer or ECG data. None are in the endpoint list.
- Writes. Every V2 usercollection path is read-only.
- A published history window or numeric rate limits.
- Fresh sleep data until the user opens the Oura app. Activity and stress may sync in the background.
- Data types a user declined at consent.
How to get access
- Register an API Application at cloud.ouraring.com/oauth/applications. You get a Client ID and Client Secret.
- Build against the sandbox endpoints (/v2/sandbox/usercollection/...) if you have no rings yet.
- Connect up to 10 real users. "API Applications are limited to 10 users before requiring approval from Oura."
- When development is finished, request approval from your application's page. Oura approves. Criteria and wait time not published.
- After approval there is no user limit.
- For higher rate limits, email api-support@ouraring.com.
From zero to your first Oura data in four steps
- Register an app. Create an API Application at cloud.ouraring.com/oauth/applications and note the Client ID and Client Secret.
- Call the sandbox. The sandbox returns test data in the real shape, so you need no ring. Every request must send a User-Agent header.
curl 'https://api.ouraring.com/v2/sandbox/usercollection/daily_activity?start_date=2021-11-01&end_date=2021-12-01' \ --header 'Authorization: Bearer <token>' \ --header 'User-Agent: YourAppName/1.0' - Connect a real user. Send them to cloud.ouraring.com/oauth/authorize with only the scopes you need, for example daily, heartrate and spo2. Swap the code for tokens at api.ouraring.com/oauth/token on your server.
- Load history once, then listen. Oura's advice is one request for historical data when the user first connects, then webhooks for every update after that. Poll the heart rate series, since it has no webhook.
Terms you must know
From the Oura API agreement at cloud.ouraring.com/legal/api-agreement. The agreement now also covers an Oura MCP Server, and some clauses name it.
- Storage, 3(m). "you shall not store or cache any data accessed or obtained through the MCP Server". Aggregators may not "store or cache any User Data or Oura Data". Healthcare: if the clause reaches API data, an EHR or trial database cannot keep Oura readings. Wellness: trend screens built on stored history are at risk too. Get counsel's read before design.
- Deletion, 5(f). Act on deletion requests within 72 hours. Both readers: build a delete path across your database, backups and any EHR copy. In an EHR, a 72-hour delete can clash with record-keeping rules.
- Competing products, 4(a)(ix) and (ii). No competing product and no purpose "competitive with Oura in any way". Healthcare: a sleep or readiness score of your own may be read as competing. Wellness: sleep apps face the same risk. Get Oura's view in writing.
- Advertising, 4(a)(viii). No advertising or promoting Oura Data or User Data. Both readers: no ad targeting from Oura data.
- Charging users, 4(a)(xiii). You may not charge users for access to the MCP Server or related services. Read it in full before you price a subscription.
- Branding, 6(e). No Oura name or marks in your app name or icon.
- Fees, 3(h). Oura may charge fees for the API in future.
- Termination, 14(b) and 14(c). Either party may terminate at any time. Oura may suspend without notice. Healthcare: have a fallback in the protocol. Wellness: do not depend on Oura alone.
- Medical use. No medical-device clause found. That does not make clinical use safe. FDA status of the ring is not in the developer docs.
- PHI, HIPAA, BAA. Not mentioned. Ask Oura before PHI flows.
- AI training and data selling. No specific clause in our research. Read the full agreement.
Cost and payment terms
- Developer fee: none listed. Oura may charge in future (3(h)).
- End user: an Oura Ring, plus an active Oura Membership for Gen3 and later. Membership price not confirmed on an Oura page in our research.
- Higher rate limits: by email. No price published.
- Aggregators: pricing not published.
Use cases
Sleep coaching program
A member connects Oura in your app and approves the daily scope. When the member opens the Oura app in the morning, the ring syncs and Oura sends a webhook about 30 seconds later. Your server fetches the sleep periods and daily sleep score and shows the coach stage times, HRV and trends.
- Member forgets to open the Oura app. Sleep data never arrives. Fix: a morning nudge, and a "last synced" indicator for the coach.
- Membership lapses. 403 from the API. Fix: detect 403, tell the member, pause the program.
- The storage clause may rule out long-term trend charts. Fix: get counsel's read before you design the history screen.
Remote monitoring pilot
A clinic enrolls patients who already own Oura rings. Daily SpO2, resting heart rate and respiratory rate from sleep feed a nurse dashboard. If the clinic wants values in the EHR, you map them to FHIR Observations, after legal sign-off on storage and PHI.
- Patients without membership send nothing. Fix: check membership at enrollment.
- Single-use refresh tokens break under retries. Fix: one refresh per user, saved before use.
- 72-hour deletion versus EHR rules. Fix: decide with counsel which copy is yours to keep.
Employer or payer wellness
A member links Oura. A daily job reads activity and readiness summaries to check a reward goal. The result goes to the rewards system.
- 10-user cap at launch. Fix: request approval before the rollout date.
- Advertising ban. Fix: keep Oura data out of marketing lists.
Research study
Participants consent in the study app and connect Oura. Webhooks and a nightly pull collect sleep periods, heart rate time series and daily SpO2. Data lands in the study dataset under participant IDs.
- Storage ban conflicts with study retention. Fix: Oura's written agreement before enrollment.
- Rate limits on bulk heart rate pulls. Fix: read the X-RateLimit headers and back off on 429 using Retry-After.
Fitness or training app
A user connects Oura to see readiness next to their training plan. Workout and readiness webhooks update the plan screen.
- Competing-product clause if you show your own readiness score. Fix: show Oura's score or get written approval.
- Branding. Fix: keep Oura marks out of your app name and icon.
Oura data in an EHR or remote monitoring program
Most healthcare teams want Oura readings next to clinical data, not in a separate app. The usual pattern is to turn each reading into a FHIR Observation, the standard record for a measurement, and send it to the EHR or the remote monitoring platform. Read the storage clause first, because it decides whether you may keep the readings at all.
| Oura value | FHIR Observation | Code |
|---|---|---|
| Heart rate sample (heartrate) | Heart rate, beats per minute | LOINC 8867-4 |
| Average SpO2 during sleep (daily_spo2) | Oxygen saturation by pulse oximetry, percent | LOINC 2708-6, plus 59408-5 for pulse oximetry |
| Total sleep time (sleep) | Sleep duration | LOINC 93832-4 |
| HRV, readiness score, temperature deviation | Device-specific Observation | Your own code system. Oura does not say which HRV method it uses, and the scores are Oura's own, so no standard code fits exactly. |
Keep the Oura record id on each Observation so a webhook update or a deletion can find it again. Oura's agreement asks for deletion requests within 72 hours, so build that path before launch.
Known blockers and gotchas
- Membership gate. A 403 can mean the user's subscription expired. Show the user a message and pause their data, and do not page your on-call team.
- Single-use refresh tokens. Refresh tokens rotate. Save the new one before you use the new access token, and never refresh twice in parallel.
- Personal access tokens are gone. They were deprecated in December 2025. Any script that still uses one will fail. Move it to OAuth.
- User-Agent header required. Every request must send one.
- Webhook subscriptions need renewing. The API has a renew operation for subscriptions. Schedule renewals and alert when one fails.
- Two rate limit layers. Per token and per application. Read the X-RateLimit-Limit, -Window, -Reset and -Tier headers.
- Client-side flow has no refresh. Tokens last 30 days and then the user signs in again. Use the server flow for anything ongoing.
- Agreement scope. The agreement now covers an MCP Server and some clauses name only it. Get counsel to read which apply to the REST API.
Delivery timeline
Our estimate. Steps marked "vendor" depend on Oura.
| Week | Work | Depends on vendor? |
|---|---|---|
| 1 | Register app, server OAuth with PKCE and rotating refresh, sandbox endpoints | No |
| 2 to 3 | Endpoints, webhook subscriptions and renewal, 403 handling, deletion path, FHIR mapping | No |
| In parallel | Legal review of storage, competing-product and MCP clauses | No, counsel |
| 3 onward | Approval request to lift the 10-user cap | Vendor, no published wait |
Questions to ask Oura before you sign
- Does section 3(m) on storage apply to REST API data, or only to the MCP Server?
- Can we keep Oura readings in an EHR or study database, and for how long?
- Would our own score or dashboard count as competitive under 4(a)(ix)?
- Will you sign a BAA, or give written approval for PHI use?
- What do you check in approval, and how long does it take?
- What are our numeric rate limits?
- How far back does the API return history for a new user?
- Can an organization pay for members' Oura Membership so data keeps flowing?
Other device integration guides
Oura is often one device among several. Each guide below uses the same layout, so you can compare access, data and terms side by side. For the full service, see medical device integration.
- WHOOP API integration guide
- Garmin API integration guide
- Ultrahuman API integration guide
- Eight Sleep API integration guide
- Fitbit and Google Health API integration guide
- Apple Health API integration guide
- Health Connect API integration guide
- Samsung Health API integration guide
- Withings API integration guide
- Dexcom API integration guide
- FreeStyle Libre API integration guide
- Polar API integration guide
- COROS API integration guide
- Suunto API integration guide
- Strava API integration guide
- Peloton API integration guide
- MyFitnessPal API integration guide
Ready to build with Oura?
We build device integrations into healthcare and wellness products, including FHIR mapping and EHR delivery. We have no partnership with Oura. Tell us your device, your users and your target date, and we will send back the route, the vendor approvals you need and a build plan. Book a call about your device integration.
For whoever builds this
- OAuth2. Authorize: https://cloud.ouraring.com/oauth/authorize. Token: https://api.ouraring.com/oauth/token. PKCE recommended (S256).
- Server-side flow: lifetime from expires_in. Refresh tokens single-use and rotating. Client-side flow: 30-day token, no refresh.
- Scopes: email, personal, daily, heartrate, workout, tag, session, spo2, heart_health.
- Endpoints: /v2/usercollection/ daily_activity, daily_cardiovascular_age, daily_readiness, daily_resilience, daily_sleep, daily_spo2, daily_stress, enhanced_tag, heartrate, personal_info, rest_mode_period, ring_battery_level, ring_configuration, session, sleep, sleep_time, tag, vO2_max, workout. Sandbox mirror at /v2/sandbox/usercollection/.
- Webhooks: /v2/webhook/subscription (create, list, renew, delete) with x-client-id and x-client-secret headers. Read the request body and signing details from the spec.
- Required header: User-Agent.
- Rate limits: per token and per app. 429 with Retry-After, X-RateLimit-Limit, -Window, -Reset, -Tier. Numbers not published.
- Errors: 403 can mean expired membership.
- FHIR (LOINC from the FHIR R4 vital signs profile): heart rate 8867-4, SpO2 2708-6, respiratory rate 9279-1, body weight 29463-7, body height 8302-2.
- Unverified codes: sleep stages, HRV, VO2 max, cardiovascular age. Readiness and resilience are Oura scores and need a local code system.
- Version: API 2.0, spec openapi-1.43. V1 removed 22 Jan 2024. PATs deprecated December 2025.
Sources
All read 10 Nov 2026.
- Oura Apple Health integration, https://support.ouraring.com/hc/en-us/articles/360025438734-Apple-Health-Integration, read 10 November 2026.
- Oura Health Connect integration, https://support.ouraring.com/hc/articles/10786105824531-Health-Connect-by-Android-Integration, read 10 November 2026.
- Terra supported integrations, https://docs.tryterra.co/reference/health-and-fitness-api/supported-integrations, read 10 November 2026.
- Junction providers list, https://docs.junction.com/wearables/providers/introduction, read 10 November 2026.
- Thryve data sources overview, https://docs.thryve.health/thryve-data-sources/overview, read 10 November 2026.
- ROOK data sources, https://docs.tryrook.io, read 10 November 2026.
- Sahha integrations, https://www.sahha.ai/docs/connect/integrations.md, read 10 November 2026.
- Spike integrations, https://www.spikeapi.com/integrations, read 10 November 2026.
- Validic supported devices and restricted vendor list, https://www.validic.com/features/supported-devices/, read 10 November 2026.
- https://cloud.ouraring.com/v2/docs
- https://cloud.ouraring.com/v2/static/json/openapi-1.43.json
- https://cloud.ouraring.com/docs/
- https://cloud.ouraring.com/docs/authentication
- https://cloud.ouraring.com/legal/api-agreement
- https://support.ouraring.com/hc/en-us/articles/4415266939155-The-Oura-API
- https://hl7.org/fhir/R4/observation-vitalsigns.html
Ready to scale?
Talk to our healthcare engineering team about building, integrating, and shipping faster.
Frequently Asked Questions
Does Oura have a public API?
Is the Oura API free?
Do Oura users need a membership for the API to work?
How many users can connect to an Oura API app?
What data can I get from the Oura API?
Can I get raw sensor or ECG data from Oura?
Does the Oura API support webhooks?
Can I store Oura data in an EHR?
Is the Oura API HIPAA compliant?
Are Oura personal access tokens still supported?
What are the Oura API rate limits?
Which OAuth scopes does the Oura API use?
How much history do I get when a user first connects?
Does the Oura API send heart rate by webhook?
What does Oura's temperature deviation mean?
Can I get heart rate during workouts?
Which Oura API version should I use?


