TempoLife › Features › Integrations › oura

Oura

No Oura API integration. On Android, Oura data can arrive through Health Connect.

Not builtSmart ringSource label: com.ouraring.ouraChecked 2026-09-02

TempoLife does not connect to Oura. Everything below describes what would arrive by another route, and what would not arrive at all.

The honest status

Oura is a sleep and recovery device, and sleep is one of the four things TempoLife tracks closely — so this is a genuinely useful pairing. It just is not a built one. Everything below is the Android route.

Concretely: a repository-wide search for Oura finds no client id, no token exchange, no API endpoint and no scheduled job. The only matches are a display label that turns the vendor's Android package name into a readable source name, and a registry entry for this very page. A label is not an integration.

Data types, one by one

The route that works today (Android only)

1. Install the TempoLife Android app. The website cannot read Health Connect; only the installed app can. Get the app.
2. Install Health Connect if your phone does not already have it. On Android 14 and later it is part of the system.
3. Open the Oura app and turn on its Health Connect sharing. This step happens entirely inside Oura. Which data types it offers to share — and whether it offers any — is decided by Oura, not by TempoLife. If the option is missing there, nothing on the TempoLife side can create it.
4. In TempoLife, tap Connect Google Health and grant the permissions you want to share. The prompt is Android's, not ours, and you can change it later in Health Connect settings.
5. Check the attribution. Once data flows, TempoLife labels its origin from the writing app's package name — com.ouraring.oura is recognised and shown as "Oura". If you see that label, the chain is working end to end.

Two limits of this route are worth knowing before you rely on it. First, it is a copy, not a live link: TempoLife reads what is in Health Connect at sync time, so if Oura writes late, TempoLife reads late. Second, only today's step total is refreshed by the background worker — sleep, weight, heart rate and any history are read when the app is open. Opening TempoLife once a day is enough; never opening it is not.

What does not work, so you do not waste an evening

• There is no file import. Exporting your history from Oura and uploading it to TempoLife is not possible. The server contains a weight-only CSV parser, but nothing in the app can reach it: there is no file picker, no upload screen and no route to it. Treat it as absent.
• There is no public write API. No endpoint accepts a meal, a weight or a step count from a third party, so an Apple Shortcut, a Tasker task, a Zapier action or a script of your own has nothing to post to. The public API is read-only food data.
• There is no email or webhook inbound path. Sending your Oura export to an address, or pointing a vendor webhook at TempoLife, does nothing.
• iOS has no automatic path at all. Health Connect is Android-only, and there is no published TempoLife iOS app to read Apple Health with.

What is left, and it is not nothing: manual entry. Weight takes about four seconds to type, and a weight chart built from three entries a week is more useful than an automatic one you never look at. Steps can be entered by hand too.

What TempoLife does with the data once it has it

Steps land on the daily total and the hourly curve, and feed the activity-energy estimate that sits beside the day's food. Sleep becomes a length, a stage breakdown and a wake time — and note that TempoLife dates a sleep record by the wake date, so a night that starts on Friday appears on Saturday. Weight becomes a point on the trend line and, where a goal is set, the input to the projection. Heart rate, resting heart rate and HRV are stored as their own series and are only ever shown, never interpreted — there is no diagnosis anywhere in the product.

None of these numbers are medical measurements and nothing here is a diagnosis. Consumer wearables estimate; they do not measure the way clinical equipment does. Talk to a clinician about anything that concerns you.

Privacy of the connection

Every permission is granted by you on the device and can be withdrawn on the device. TempoLife holds no credential for Oura — no OAuth token, no password, no account link — because it never talks to Oura at all. Deleting your TempoLife account deletes the imported records with it, and leaves whatever is in Health Connect and in the vendor's own app untouched.

Frequently asked questions

Source: TempoLife application source — assets/js/health-connect.js, api/health_connect.php, api/sync.php, api/fitbit.php, apple/ios/App/App/TempoLifeHealthPlugin.swift · checked 2026-09-02

Other integrations

All integrations · Developer API