Oura | Sahha Docs

Overview

Connect Oura Ring data to Sahha via the Oura Cloud API. You register an app with Oura, add it to Sahha as an integration, then connect end users. The connection flow itself is shared across providers — see Integrations for the concepts and Connect a user for the full round-trip.

Status	Beta self sign-up
API slug	`oura`
Device	Ring
Connection	Cloud OAuth
Live sync	Push (subscriptions)
Backfill on connect	30 days

Before you start

Examples use the sandbox environment. Replace sandbox-api.sahha.ai with api.sahha.ai for production — see API Environments .

Oura uses self sign-up — no approval step is required to create an app.

1. Register your Oura app

This gives Sahha the OAuth credentials it uses to request data on your users' behalf.

Sign in to the Oura Cloud Developer Portal .
Create a new OAuth2 Application .
Configure the application's name, description, and logo — these are shown to end users during the connection flow.
Add the Sahha OAuth redirect URL to the allowed redirect URIs:
```
https://sandbox-api.sahha.ai/api/v1/integration/oauth/oura/callback
```
https://sandbox-api.sahha.ai/api/v1/integration/oauth/oura/callback
Select the scopes you want Sahha to ingest. Available scopes: email, personal, daily, heartrate, workout, tag, session, spo2, ring_configuration, stress, heart_health.
Save, then copy your Client ID and Client Secret for the next step.

2. Create the integration in Sahha

Go to the Sahha Dashboard .
Navigate to Integrations → Integrations in the sidebar.
Click Add integration and select Oura from the Provider dropdown.
Paste in your Oura Client ID and Client Secret .
In the Scopes dropdown, select the same scopes you enabled on your Oura app in step 1 — these are what Sahha requests when a user connects.
Add one or more entries to the Redirect URL Whitelist — the URLs in your own app that Sahha may redirect users back to after OAuth.
Save the integration.

Match your scopes

By default all provider-supported scopes are selected — not just the ones enabled on your app. Deselect any scopes your Oura app doesn't have access to, otherwise the OAuth flow will fail.

About the Redirect URL Whitelist

When you start the OAuth flow you may optionally pass a redirectUrl — it must match a whitelisted entry. If omitted, Sahha uses the first URL in the whitelist.

3. Connect a user

Start the OAuth flow with the user's profile token. Oura's slug is oura:

curl -X GET "https://sandbox-api.sahha.ai/api/v1/integration/oauth/oura/authorize?redirectUrl=https://yourapp.com/integrations/callback" \
  -H "Authorization: profile {your-profile-token}"

{
	"authorizationUrl": "https://cloud.ouraring.com/oauth/authorize?..."
}

Redirect the user to authorizationUrl to complete authorization. For the full round-trip, prerequisites, language-specific snippets, and the SDK option, see Connect a user .

Oura-specific notes

Scopes must match. A scope selected in Sahha but not enabled on your Oura app will fail the OAuth flow (see step 2).
Subscriptions are automatic. Sahha manages Oura webhook subscriptions for you — there's no separate webhook step to configure.

For data freshness, the connection lifecycle, and disconnecting a user, see Managing connections on the Integrations page.

Support

Need help? Contact support@sahha.ai or join the Slack Community .