Skip to content
Wearable Integrations

Devices & platforms

Supported Wearable Devices and Health Data Platforms

Each guide explains how a platform can be integrated, which data types are available, what users and vendors must authorize, and where developer approval or a commercial agreement may be required. Product names are trademarks of their owners; we do not claim partnerships or privileged API access.

Integration methods compared

A quick reference for planning. Requirements change, so treat this as a starting point for feasibility rather than a final answer.

Wearable platforms by integration method and access requirement
PlatformPrimary methodAccess note
Apple HealthKitOn-device · iOS appUser permission per data type; App Store review
Google Health ConnectOn-device · Android appPlay Console health permissions declaration
Fitbit APICloud API · OAuth 2.0Intraday data requires Fitbit approval
Garmin Health APICloud API · push/pullApproved business developers only
Oura Ring APICloud API · OAuth 2.0Data can depend on member status
Samsung HealthAndroid SDK / Health ConnectPartner approval for SDK distribution
Withings APICloud API · webhooksClinical services by commercial agreement
Polar APICloud API · BLE SDKAccessLink client registration
CGM IntegrationVendor APIs · partnershipsProduction access typically gated
Bluetooth DevicesBLE GATT · gatewaysProprietary protocols need vendor docs

Checking a device that is not listed?

Many devices can be reached through Apple Health, Health Connect, a vendor cloud or standard Bluetooth profiles. Tell us the make and model and we will check what is possible.