CONNECTIONS · OFFICIAL PATHS
Supported means verified.
A provider is shown as connected only after its official production path works end to end. Environment variables cannot replace native entitlements, user consent, provider review or commercial approval.
Apple Health
HealthKit on iOS; per-type permission and App Store review required. Official source ↗
Android Health
Health Connect on-device permissions and Google Play health policy apply. Official source ↗
Arboleaf CS20M
Direct native Bluetooth LE path for the QN-series FFE0 GATT scale; no cloud credentials. Requires a signed iOS/Android build, runtime BLE permission, a physical scale, and user confirmation before import. Official source ↗
Withings
Public OAuth application, scopes and provider terms required. Official source ↗
Fitbit
Public Web API; restricted scopes and intraday access rules apply. Official source ↗
Oura
Cloud API with OAuth, membership and scope limitations. Official source ↗
WHOOP
Registered OAuth client, review, scopes and platform terms required. Official source ↗
Polar
AccessLink registered client and user authorization required. Official source ↗
Strava
Athlete/activity API, not a complete health record. Official source ↗
Samsung Health
Mobile Health Data SDK; partnership and distribution approval required. Official source ↗
Xiaomi, Eufy and most RENPHO cloud flows
Aggregator route only when their companion app writes to HealthKit or Health Connect. Do not collect app credentials or scrape closed consumer APIs. Official source ↗
Tanita and OMRON
Direct access requires a supported regional vendor or commercial program. Official source ↗
Implementation boundary
PULSE normalizes source IDs, measurement timestamps, ingestion time, units and device provenance. Closed APIs are fail-closed: no scraping, credential collection or simulated connection state.