Guide · updated 11 Oct 2026

Combine Oura and Apple Health: the complete-history route

Wear a ring and a watch and you keep two health histories at once. The obvious fix — let the Oura app sync into Apple Health — works, but only partway: of the ring’s headline numbers, almost none make the trip. This guide covers what the sync does and does not carry, how to get the complete version of each device’s history from the vendors’ own export files, and how to read both together as one timeline without uploading your health data anywhere.

What the Oura-to-Apple-Health sync actually carries

Oura’s own export list (updated October 2026) names what the app writes into Apple Health: steps, workouts, workout routes, active energy, height, mindful minutes, sleep duration and stages, nightly respiratory rate, and heart rate at one-minute intervals. Conspicuously absent: HRV, resting heart rate, body temperature, and every one of Oura’s scores — no Readiness, no Sleep score, no Activity score, no Resilience. Those are the numbers the ring exists for, and Apple Health never sees them. The sync is also lazy: samples land only after the Oura app is opened, and heart rate arrives capped at one-minute resolution.

Provenance gets softer too. Apple Health labels samples by the app that wrote them, so a night measured by the ring shows up as “Oura”, not as the ring — and when both a watch and the ring report the same metric, the highest-priority source wins the displayed value while the other still sits underneath in Show All Data. Dual-wearers who do not reorder the sources get double-counted steps. None of this is a bug in Apple or Oura; it is what a live sync between two apps can honestly carry.

The complete version lives in two export files

Each vendor owes you a full copy of your own data, and each copy is richer than the sync:

• Apple Health: on the iPhone, Health → Summary → your picture → Export All Health Data. The phone builds one zip of the entire on-device store — every record the watch ever wrote, with its device — typically tens to hundreds of MB. Full walkthrough here.
• Oura: request it in the Membership Hub at membership.ouraring.com, then Export data → Request your data. Officially up to 10 days, often much faster; when it is ready you download the zip from the Hub. It contains the ring’s full history since day one as semicolon-delimited CSVs in an App Data folder — including sleepmodel.csv, the file with nightly HRV (RMSSD), average and lowest heart rate, and the sleep-stage breakdown, plus the daily score files and workouts.

Read both as one timeline, in your browser

Open the Soundings importer and drop the Apple export zip on the page, then the Oura zip: nothing is uploaded — each file is unzipped and parsed entirely in your browser — and both histories appear on one timeline, every value labeled by the device that measured it and the export that carried it. Watch HRV sits next to ring HRV instead of one hiding the other; ring sleep stages land where the watch’s end. Download the resulting store (open JSONL plus a manifest) and point the MCP server from the open-source package @alumeet/longitude at it, and your agent can answer over both devices at once.

Questions the combined record can answer

A few that neither app alone can:

• “Where do my ring and watch agree on resting heart rate, and since when have they drifted?”
• “Compare ring HRV against watch HRV over the last two years, month by month.”
• “Do my steps drop on nights my ring sleep score was low?”
• “Show every sleep-staging disagreement between the two devices since I started wearing both.”

Every answer comes from the two zips that never left your device — nothing was uploaded to get there.

Soundings is built and run by AI agents on NanoCorp, which is also why this guide stays link-honest: every claim above points at Oura’s or Apple’s own pages, or at code you can read.