Ctrlk
Dashboard
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Per-user OAuth apps

Some providers let each of your end-users connect through their own OAuth app, instead of through a shared app you manage. This is useful when your users are themselves developers — they register their own app with the provider, and they bring its credentials when they connect through Terra.

You enable this per-(provider, dev_id) from your dashboard: open the connection's settings and turn on Per-user apps. Once it's on, every new connection for that provider goes through a Terra-hosted page where the user enters their own client_id and client_secret. Those credentials are pinned to that one connection and aren't shared.

This page lists what each user needs to do at the provider's developer portal. Share the relevant link with your users.

Existing connections aren't affected. Turning the toggle on changes the routing only for connections created from that point on. Users already connected through your previous setup keep working.

Strava

Each user registers their own Strava OAuth app and enters its credentials on the Terra-hosted connect page.

  1. Sign in to https://www.strava.com/settings/api.

  2. Create an application. The Application Name, Website, and Application Description can be anything.

  3. Set the Authorization Callback Domain to:

    access.tryterra.co

  4. Save the application. Copy the Client ID and Client Secret.

  5. When prompted on the Terra-hosted connect page, paste the Client ID and Client Secret to complete the connection.

Callback domain only — no path. Strava's field accepts a domain, not a full URL. Use exactly access.tryterra.co.

Oura

Each user registers their own Oura OAuth application and enters its credentials on the Terra-hosted connect page.

  1. Sign in to https://cloud.ouraring.com/oauth/applications.

  2. Create a new application. The Application Name and Application Description can be anything.

  3. Set the Redirect URI to:

  4. Make sure the application is allowed the scopes Terra requests: email, personal, daily, heartrate, workout, tag, session, spo2Daily.

  5. Save the application. Copy the Client ID and Client Secret.

  6. When prompted on the Terra-hosted connect page, paste the Client ID and Client Secret to complete the connection.

WHOOP

Each user registers their own WHOOP OAuth application and enters its credentials on the Terra-hosted connect page.

  1. Sign in to https://developer-dashboard.whoop.com/ (a WHOOP account is required).

  2. Create a new application.

  3. Set the Redirect URL to:

  4. Set the Webhook URL to:

  5. Save the application. Copy the Client ID and Client Secret.

  6. When prompted on the Terra-hosted connect page, paste the Client ID and Client Secret to complete the connection.

Webhook URL is required. Without it, real-time updates from WHOOP won't reach Terra and the user's data will only refresh on poll.

Last updated

Was this helpful?