For available integrations, please refer to the integrations page
Currently the integrations mentioned above go through the newly developed Health Connect platform, which is an on-device storage system developed by Google. This platform however is still in its infancy, and comes with a number of issues.
Health connect known issues
We have seen numerous cases of apps not being able to sync into Health Connect due to bugs in the HC platform itself. This could be, for example, Samsung Health not being able to send steps into HC.
We've also seen cases where HC data simply could not be accessed, for no apparent reason, leading to limited or no syncing of data possible.
Before going LIVE (release), you will ALSO need to apply for permissions to access the Health Connect API with Google. Use this application form.
In the form, you will need to specify which data types you intend to read from Health Connect.
For the reasons mentioned above, we highly recommend using the Google Fit integration through the API instead (resource name/enum
Some of our integration partners require us to have our customers establish direct partnerships with them. These integrations are:
You may see guides below in the appropriate section, and for any ones which are not outlined at the bottom of this page, please contact us for a step-by-step walkthrough
Some of the integrations provided are developed on agreements subject to be updated by the integration providers. their APIs can be modified without notifying Terra, which could cause disruption in the service beyond our control.
Those integrations are:
- Bryton Sport
- Clue app
- Hammerhead Karoo
- Tempo Fit
- Train Xhale
- Velo Hero
For some providers such as Google Fit, you are advised to have your own application keys either because the provider requires it in there terms, or to simply avoid rate limits and separate your environment from the shared Terra keys.
- Log in to https://strava.com/settings/api
- Create an application
- Set the Authorization callback domain to api.tryterra.co, and save the client ID and client secret obtained
- In your Terra dashboard, add Strava to your connections under API > Connections > Add more
- Fill in the obtained client_id and client secret on that connection's settings
- Request an API key from https://virtuagym.com/public-api
- In you Terra dashboard, add Virtuagym to your connections under API > Connections > Add more
- After adding Virtuagym, go the Virtuagym options
- Fill your portal name in the client id, and your API Key in the client secret
This can be achieved by following the Registration & Verification guide
Through the Huawei ID Registration process, you will be asked to verify your identity.
This is separate from the Huawei ID registration - the service is what will allow you to then access various Huawei APIs). Follow the guide here for a step-by-step explanation on how to achieve that
|Redirect URL||This should be set to "https://api.tryterra.co/v2/auth/huawei/oauth2"|
|App access URL||https://api.tryterra.co/|
|Callback URL||This should be set to|
Please follow the guide Health Kit access here for an in-depth explanation of how to gain access to users' health data through Huawei Health Kit
Make sure to register for notifications (webhooks) by following these steps:
Creating Google Fit keys is not necessary, but an optional step in order to display your own name & logo in the authentication page, and to have separate rate limits for your users.
Create keys on https://developers.google.com/identity/protocols/oauth2#basicsteps and fill the client id and client secret you get in the Terra dashboard.
The default scopes Terra uses are:
calendar.settings.readonlyis used for getting time zone information from users in order to properly localize their daily payloads
userinfo.profileis necessary in order to appropriately store Google user IDs on Terra's end
Requesting fewer scopes
You may select a subset of the rest of the scopes according to your application's needs, and let us know which ones you have selected so we can make the necessary adjustments on our end.
fitness.activity.read fitness.heart_rate.read fitness.location.read fitness.nutrition.read fitness.blood_pressure.read fitness.blood_glucose.read fitness.body.read fitness.oxygen_saturation.read fitness.body_temperature.read fitness.reproductive_health.read fitness.sleep.read user.birthday.read user.gender.read userinfo.email userinfo.profile calendar.settings.readonly
If any of the above do not show up when adding scopes to your application, make sure you have enabled the appropriate API in https://console.cloud.google.com/apis/library
Your app will need to be submitted for verification in order for these keys to be able to be used. The FAQs for this can be found here
You will need to create a video explaining how your app will use each of the scopes requested, and fill in some description information for it.
In Germany, Austria and France, it is necessary to have a doctors license to be able to access Freestylelibre of users residing in said regions. This would mean having a registered practice. Once you have a practice id for a practice on the Libreview web app, you then would need to let us know the details and we will be able to proceed as per the normal procedure.
Dexcom prefers to make partnerships directly with the end users of their API. You will need to set up your own Dexcom API account and let us know the credentials. Here are the steps you need to do to connect to Dexcom!
- first step would be to make an account here: https://developer.dexcom.com/user/login
- you'd then create an app here: https://developer.dexcom.com/account/apps
- set up a redirect rule on a URL of your choice on your server, having it it redirect to https://api.tryterra.co/v2/auth/dexcom/oauth2 (make sure all query params are forwarded through as well). For example, if your domain for your server is https://yourserver.com, you could pick https://yourserver.com/auth/dexcom and make sure any request to it, e.g. https://yourserver.com/auth/dexcom?foo=bar is redirected to https://api.tryterra.co/v2/auth/dexcom/oauth2?foo=bar
- set that redirect URL in the app created in step 2
- share credentials (client ID & secret) from step 2 with us
- authenticate a test account through Terra (same way as with every other provider)
- apply for production access to Dexcom through the "apply for upgrade" button on the app created in step 2
Updated 24 days ago