ASUS VivoWatch Integration

Stream ASUS VivoWatch data. No ASUS API needed.

ASUS VivoWatch writes steps, active energy, heart rate, and total sleep to Apple Health on iOS — ASUS describes it as a one-way share, and Sahha’s SDK reads what lands there into your app as normalized biomarkers, alongside every other source.

On-device
Apple Health
iOS
HIPAA
GDPR

Start building Read the SDK docs

Free for 30 days · No credit card

Normalized Auto-synced

Steps: 7,860
Heart rate: 68 bpm
Sleep duration: 6:55 h

Identical schema across 500+ sources

How it works

Your users connect ASUS VivoWatch. Sahha does the rest.

This is your user’s side of the story — one screen, once. Sahha ingests every ASUS VivoWatch signal, normalizes, deduplicates, and delivers it to your service — raw, or as refined intelligence your product can act on.

Allow "your app"

Sleep

Activity

Heart rate

Connect

9:41LIVE

82READY

Sleep7h 12m

Steps5,993

Heart rate62 bpm

Your early-riser reward

20% off açaí bowls — today only.

Sahha

Permissions handled

Encrypted in transit

History backfilled

Background sync enabled

Cleaning · deduping · scoring

Raw data logs Biomarkers Scores Insights Archetypes Tags

Real-time webhooks

Always in sync

Query via API

Access controlled

Your service

Waiting for data…

On-device and permissioned

ASUS VivoWatch data is read on the user’s own device, only after they grant Apple Health permission — nothing syncs without consent.

One integration, every source

Permission is per data type, not per brand. Anything that writes to Apple Health — ASUS VivoWatch today, a new watch next year — flows through the same SDK with no extra prompt and no new code.

Data coverage

What ASUS VivoWatch syncs through Apple Health.

Request only what you need
You choose exactly which of these signals to request from Apple Health — users are only ever prompted for those, which keeps opt-in rates high.
One schema, every source
ASUS VivoWatch, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Steps, active energy, heart rate, and total sleep pass through Apple Health; some app-exclusive metrics may not.

Activity & exercise

HealthKitSahha

stepCountstepscount
activeEnergyBurnedactive_energy_burnedkcal

Heart & vitals

HealthKitSahha

heartRateheart_ratebpm

Sleep

HealthKitSahha

sleepAnalysis · asleepsleep_durationmin

See a real payload

HealthKit · daily

{
  "type": "HKQuantityTypeIdentifierStepCount",
  "value": 7860,
  "unit": "count",
  "startDate": "2026-06-03T00:00:00Z",
  "endDate": "2026-06-03T23:59:59Z",
  "sourceRevision": { "source": { "name": "ASUS VivoWatch" } }
  // …heart rate, active energy & sleep samples
}

Sahha · normalized

[
  {
    "category": "activity",
    "type": "steps",
    "value": 7860,
    "unit": "count",
    "periodicity": "daily",
    "aggregation": "total",
    "startDateTime": "2026-06-03T00:00:00Z",
    "endDateTime": "2026-06-03T23:59:59Z"
  }
  // …3 more normalized logs
]

ASUS is explicit that the integration is one-way: the app will “share healthdata … to HealthKit, and won’t get any data from HealthKit.” One naming caveat worth stating plainly — ASUS ships a feature called “ASUS HealthConnect”, which is ASUS’s own app name and has nothing to do with Google Health Connect; it doesn’t imply Android support. This is an OEM companion app, so what crosses depends on the VivoWatch model the user owns, sync happens when the app is open and the watch is in range, and ASUS’s own proprietary indices stay in its app.

Missing a metric you need? Talk to us in the Sahha Slack — if ASUS VivoWatch captures it, we can usually add support.

Get more than just raw data

Sahha turns these signals into biomarkers, scores, archetypes, and insights — the modeling done for you.

Biomarkers

Scores

Archetypes

Insights

Reading Apple Health yourself? Here’s the to-do list.

Everything on the left is yours to write, test, and maintain on iOS. Everything on the right, Sahha already did.

Build it yourself

With Sahha

Every device

Build it yourself

Integrate Apple Health.
Handle iOS version differences.
Add Health Connect separately for Android.

With Sahha

One SDK covers Apple Health, Health Connect, and every cloud source.

Getting the data

Build it yourself

Write the HealthKit queries.
Request the right permissions.
Wire up background delivery.

With Sahha

The SDK handles queries, permissions, and background sync.

Keeping it clean

Build it yourself

Dedupe apps writing the same metric.
Map dozens of HealthKit types.
Reconcile against your Android sources.

With Sahha

Deduped, typed, one schema — one stream per user.

Turning it into insight

Build it yourself

Build a sleep model.
Build an activity model.
Hire a data scientist.

With Sahha

Scores, archetypes, and insights — built in.

Keeping it alive

Build it yourself

Apple changes a HealthKit API.
You find out in production.

With Sahha

We version the SDK. You never notice.

No ASUS VivoWatch developer account needed — Sahha reads what ASUS VivoWatch already writes to Apple Health on iOS.

Setup

Live in an afternoon, not a sprint.

# Add the Sahha SDKnpm install sahha-react-native
01
Add the Sahha SDK
Drop the Sahha SDK into your iOS app — or React Native or Flutter. The same SDK also covers Health Connect for your Android sources.
A
Allow “your app”
Sleep
Activity
Heart rate
Connect
02
Prompt for Apple Health permissions
Call the SDK to show the native Apple Health consent sheet. The user chooses what to share — under your brand. It’s one prompt, ever: permission is per data type, not per brand, so every future source is already covered.
Your app LIVE
Sleep7h 12m
Readiness82
Heart rate62 bpm
03
Sahha reads and delivers
Once permission is granted, the SDK reads ASUS VivoWatch data from Apple Health in the background, normalizes it to one schema, and streams it to your app by webhook or API.

Start building Read the SDK docs

Most teams read live ASUS VivoWatch data the same day they add the SDK. The only per-source prerequisite: your user has ASUS VivoWatch’s Apple Health sync switched on — most source apps enable it by default.

Destinations

Route it into your stack.

Sahha streams every update to your webhook — and a step-by-step guide takes it the rest of the way into your database, CDP, or messaging tool.

FAQ

ASUS VivoWatch integration questions

How does Sahha get ASUS VivoWatch data?

The VivoWatch app writes steps, active energy, heart rate, and sleep to Apple Health on iOS, and Sahha reads them from there with its mobile SDK — no ASUS API to integrate.

Does data flow back into the VivoWatch app?

No. ASUS states the app will “share healthdata … to HealthKit, and won’t get any data from HealthKit.” It’s an outbound, one-way integration, which is exactly what Sahha needs — the data lands in Apple Health and Sahha reads it from there.

Is “ASUS HealthConnect” the same as Google Health Connect?

No — and the names are close enough to cause trouble. “ASUS HealthConnect” is ASUS’s own app feature name. It is unrelated to Google Health Connect, the Android health data store, and it doesn’t imply an Android read path for Sahha.

Does the ASUS VivoWatch integration work on Android?

Not today. There’s no confirmed Health Connect write path from the VivoWatch app, so Sahha reads VivoWatch through Apple Health on iOS. Your users’ other Android sources still flow through the same Sahha SDK.

Is the ASUS VivoWatch integration HIPAA and GDPR compliant?

Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and ASUS VivoWatch data flows through the same compliant pipeline as every other source.