Bring Your Own OAuth
Bring Your Own OAuth
Bring Your Own OAuth (BYOO) is available for the Grow and Scale plans.
WHOOP BYOO is available for the Launch, Grow and Scale plans. See our WHOOP Guide for more information.
With custom credentials you can use your own team name and setup your own logo for the provider.
OAuth Providers supporting BYOO
Some BYOO providers do not have a developer program with open sign-up.
| Provider | Slug | Remarks |
|---|---|---|
| Fitbit | fitbit | - |
| Garmin | garmin | - |
| Google Fit | google_fit | - |
| Oura | oura | - |
| Strava | strava | - |
| Wahoo | wahoo | - |
| Withings | withings | - |
| Dexcom | dexcom_v3 | ↗️ Guide |
| WHOOP | whoop_v2 | ↗️ Guide |
| Polar | polar | - |
| Cronometer | cronometer | - |
| Omron | omron | - |
| MyFitnessPal API | my_fitness_pal_v2 | - |
| MapMyFitness | map_my_fitness | - |
| Ultrahuman | ultrahuman | - |
Provider Rate Limits
This section documents the starting rate limit of a brand new OAuth application, should you choose to BYOO.
| Provider | Starting Rate Limit |
|---|---|
| Fitbit | 150 requests per hour per user |
| Garmin | 10,000 days of data per minute |
| Google Fit | 600 requests per minute |
| Oura | 5,000 requests per 5 minutes |
| Strava | 100 requests per 15 minutes 1,000 requests per day |
| Wahoo | 200 requests per 5 minutes 1,000 requests per hour 5,000 requests per day |
| Withings | 120 requests per minute |
| Dexcom | 60,000 requests per hour |
| WHOOP | 100 requests per minute 10,000 requests per day |
| Polar | 20 requests per 15 minutes per user 100 requests per day per user |
| Cronometer | N/A |
| Omron | N/A |
Setting up your OAuth credentials
Through the Org Management API
1
Setup your OAuth application
Use the Prepare Team Custom Credentials
endpoint to obtain the instructions to setup your OAuth application.
2
Set your application credentials
Use the Set Team Custom Credentials endpoint
to apply your OAuth application credentials to your Vital Team.
Credentials that are activated immediately
Credentials that are activated immediately
BYOO credentials for the following providers are immediately active, once set through the Set Team Custom Credentials:
| Provider | Slug |
|---|---|
| Garmin | garmin |
| Google Fit | google_fit |
| Oura | oura |
| Strava | strava |
| Wahoo | wahoo |
| Withings | withings |
| Dexcom | dexcom_v3 |
| WHOOP | whoop_v2 |
| Polar | polar |
| Cronometer | cronometer |
| Omron | omron |
| Ultrahuman | ultrahuman |
| MyFitnessPal API | my_fitness_pal_v2 |
| MapMyFitness | map_my_fitness |
Credentials that need support intervention once set
Credentials that need support intervention once set
The following providers are not immediately active. You need to take a couple of extra steps to activate them:Fitbit (
fitbit)- You must press the “Verify” button on all the Webhook Subscribers in the Fitbit Developer Portal.
- Once the buttons are gone and replaced by (usually zeroed) delivery statistics, it implies that Fitbit has completed the verification challenge with Vital.
Through Vital Support
To setup custom OAuth application credentials, you need to do the following:- Create a developer account with the cloud-based OAuth providers.
- Generate a OAuth application credentials from your developer account. You can do this by going to the providers developer accounts page and creating a new application.
- Email Support@tryvital.io or message us on Slack with the following information:
- The provider you want to customize
- The client ID and client secret for the provider
- Use tools like Doppler Secret Share or 1Password to protect your credentials.
- The redirect URI for the provider
- The name of your team
- The logo for your team
- We will then setup the custom credentials for you and let you know when it’s ready to go.
Some Oauth providers are unavailable unless you can Bring Your Own OAuth (BYOO) — you will have to apply directly
to the provider for an OAuth application, and provide Vital your assigned credentials once the application is accepted.