Terra

Integration

API
Unified API
SDK
SDK
Authentication
Authentication
Streaming
Streaming
Blood
Blood Report API
Planned Workout
Planned Workout
AI Interface
AI Interface

User engagement

Graph API
Graph API
Scores
Health Scores
Rewards
Health Rewards

Use cases

Enterprise
Enterprise
Insurance
Insurance

Developers

Wearable Data
Wearable Data
Community
Community
Documentation
Documentation

Learn

Blog
Blog
Podcast
Podcast
Events
Events
Reports
Reports

Company

Customers
Customers
Careers
Careers
Partners
Partners
Support
Support
Become an integration
Become an integration


Cookie Preferences

Essential CookiesAlways On
Advertisement Cookies
Analytics Cookies

Crunch Time: Embrace the Cookie Monster Within!

We use cookies to enhance your browsing experience and analyse our traffic. By clicking “Accept All”, you consent to our use of cookies according to our Cookie Policy. You can change your mind any time by visiting out cookie policy.

zap

Latest

zap

Popular

API

Unified API

SDK

Phone SDK

Authentication

Widget

Streaming

Streaming

Graph API

Graph API

Can 2 Terra subscriptions have the same user as individual connection?

All

MinimumChameleon6 months ago

I'm wondering what happens in the following scenario:

2 companies, A and B both use Terra for reading out wearable data from the same end user. The end user can link their Fitbit|Garmin|whatever account to Terra for company A as usual. Now the same user also want to link their wearable to the service from company B. Does this works?

And what if the user decides to withdraw their permissions. Does this mean both A and B are disconnected? Or are they seen as individual connections from Fitbit|Garmin to Terra?

terra

Vanessaadmin5 months ago

Hey there,

in that case, each company (A and B) maintains separate, independent User connections:

When the same end user connects their Fitbit/Garmin account to both Company A and Company B through Terra, each company gets their own unique user_id for that wearable account. These are treated as completely separate connections.

In the following example, a connection made to one fitness wearable account (e.g. one Fitbit account, or one Garmin account) will be referred to as 'one User'. You can pass a reference_id to tie back your app user to this connection.

Multiple Users can be created for one individual, also referred to as an End User. Each company operates under their own dev-id (Developer ID), which is your unique identifier for access to the API. This is how Terra identifies you, and ties Users & their data back to you.

Regarding permission withdrawal:

The connections are managed independently per company. If the end user disconnects from Company A, it does not automatically affect Company B's connection.

However, if the user revokes access at the provider level (e.g., through their Fitbit app settings), this would trigger an access_revoked event for both companies since the revocation happens at the wearable provider's side, not Terra's side.


AppropriatePlatypus5 months ago

I am new customer plz saport