We currently Support over 300+ devices, a full list can be seen below.
Cloud Based Providers
Some Oauth providers are unavailable unless you can
— you will have to apply directly to the provider for an OAuth application, and provide Vital your assigned credentials once the application is accepted.
|Beurer||Beurer Blood Pressure monitors||Password authentication|
|Dexcom||Dexcom CGM Glucose monitors||BYOO only|
|Dexcom (G6 And Older)||Dexcom CGM Glucose monitors||Password authentication|
|8Sleep||Smart Mattress||Password authentication|
|Freestyle||Abbott CGM Glucose monitor||LibreView practice connection|
|Fitbit||Activity Trackers (all devices)||Vital branded OAuth, or BYOO|
|Garmin||Fitness watches (all devices)||Vital branded OAuth, or BYOO|
|Google Fit||Activity Trackers (all devices)||Vital branded OAuth, or BYOO|
|Hammerhead||Cycling computers||Password authentication|
|iHealth||Blood pressure, Fitness scales, Glucometers & Fitness watches||BYOO only|
|MyFitnessPal||Nutrition data||MyFitnessPal Diary Sharing Key|
|Oura||Smart Sleep tracking ring||Vital branded OAuth, or BYOO|
|Peloton||Popular Indoor Exercise bike||Password authentication|
|Renpho||Fitness Scales||Password authentication|
|Strava||Running & Cycling Social Network||Vital branded OAuth, or BYOO|
|Wahoo||Cycling Equipment||Vital branded OAuth, or BYOO|
|Whoop||Your Personal Digital Fitness and Health Coach||Password authentication|
|Withings||Fitness scales, watches and health monitors||Vital branded OAuth, or BYOO|
|Zwift||Virtual cycling and running||Password authentication|
|Polar||Finnish sports tech pioneer||Vital branded OAuth, or BYOO|
|Cronometer||Nutrition data||Vital branded OAuth, or BYOO|
SDK Based Providers
|Accu-Chek (Bluetooth)||Glucose Strips/MySugr App|
|Apple HealthKit||Health and fitness data on iPhone and Apple Watch|
|Beurer (Bluetooth)||Beurer Blood Pressure monitors|
|Freestyle Libre BLE (NFC)||Abbott CGM Glucose monitor readings via SDK|
|Omron (Bluetooth)||Blood Pressure monitors and scales|
Providers under active development
Beta: Currently under development. All providers here are available in sandbox and production, any feedback you have is greatly appreciated!
|Android Health Connect||Health and fitness data on Android devices|
|Omron (Cloud)||Blood Pressure monitors and scales|
Planned: On our roadmap
|KetoMojo||TBD||Glucose, Ketones and more||Planned|
Full Device Support List
Whenever Vital detects that new data is available, data events are always sent to your configured endpoints, regardless of the provider being push-based or polling-based.
Cloud Based Providers
Cloud Based Providers can be divided in two main categories:
- When a cloud-based provider supports a push notify mechanism (typically webhooks), Vital would prefer to use it to drive data fetches. In other words, as soon as the provider notifies Vital of new data through the said mechanism, Vital fetches the latest data.
- For providers and/or resources without any push notify mechanism, Vital polls these resources at a regular schedule, typically every 15 minutes or so.
|Freestyle(API + SDK)||Polling|
SDK Based Providers
SDK Based Providers are all push-based, where data are pushed from the Vital SDK embedded inside your Android or iOS app.
|Apple HealthKit||Sync on OS notification, variable frequency |
|Android Health Connect||Sync On App Launch |
 Notes on Sync on OS notification:
Apple HealthKit notifies new data immediately only when your iOS app is in the foreground with visible UI.
Meanwhile, properly configured HealthKit apps in background with no visible UI are notified on an OS-throttled, opportunistic schedule that can dynamically change based on factors like CPU usage, battery usage, connectivity, Low Power Mode, and delivery history.
The Vital SDK — or any third-party HealthKit apps — has no control over this, other than suggesting a background delivery frequency to the OS as the lower bound. The actual delivery frequency remains at full discretion of the OS, and can range from hourly, to once a day, or when certain opportunity arises (e.g., when Sleep Mode ends, or when the phone starts charging).
Therefore, it is not recommended to base your UX around immediate availability of HealthKit data. The only exception is if your UX do involve the user actively using your iOS app. For example, iOS 17+ supports third-party apps initiating an Apple Watch workout session that would be live synced with your iPhone app.
 Notes on Sync On App Launch:
Because Android Health Connect disallowes any data access when the app is in background, your app must be regularly opened by the end user for data to be synchronized. Hence, the Vital SDK can only provide Sync On App Launch as the default automatic behaviour.
If automatic background monitoring is desired, your app would have to implement one of the Android Foreground Service — e.g. high priority push from Firebase Cloud Messaging — during which your service manually initiate a Vital SDK sync.
Historical Days Retrieved
When a new provider is connected to a user, Vital retrieves the historical data for this user from the connected provider. The following number of historical days of data are retrieved for each provider:
|Apple HealthKit (SDK)|
|Android Health Connect (SDK)|
|Freestyle Libre BLE (SDK)|
|Dexcom (G6 And Older)|
* Polar only supports historical backfill for Sleep and Sleep Stream resources.