OHealth Integration

Stream OHealth data. Straight from the phone.

OHealth is the companion app for OPPO and OnePlus wearables — it uploads steps, heart rate, and sleep to Health Connect on Android, where Sahha’s SDK reads them into your app as normalized biomarkers, alongside every other source.

  • On-device
  • Health Connect
  • Android
  • HIPAA
  • GDPR

Free for 30 days · No credit card

OHealth logo
Normalized Auto-synced
Sleep duration
7:02 h
Heart rate
65 bpm
Steps
8,410

Identical schema across 500+ sources

How it works

Your users connect OHealth. Sahha does the rest.

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

Health Connect A

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

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

One integration, every source

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

Data coverage

What OHealth syncs through Health Connect.

Works with OPPO WatchOnePlus Watch 2OPPO Band
  • Request only what you need

    You choose exactly which of these signals to request from Health Connect — users are only ever prompted for those, which keeps opt-in rates high.

  • One schema, every source

    OHealth, Apple Watch, and Oura all return the same fields and units.

  • What crosses the bridge

    Sleep, heart rate, and steps pass through Health Connect; some app-exclusive metrics may not.

Sleep

1
Health ConnectHealth ConnectSahha
  • SleepSessionRecordsleep_durationmin

Heart & vitals

1
Health ConnectHealth ConnectSahha
  • HeartRateRecordheart_ratebpm

Activity & exercise

1
Health ConnectHealth ConnectSahha
  • StepsRecordstepscount
See a real payload
Health Connect · sleep
{
  "record": "SleepSessionRecord",
  "startTime": "2026-06-02T23:32:00Z",
  "endTime": "2026-06-03T06:34:00Z",
  "metadata": { "dataOrigin": "com.heytap.health.international" }
  // …heart rate & steps records
}
Sahha · normalized
[
  {
    "category": "sleep",
    "type": "sleep_duration",
    "value": 422,
    "unit": "minute",
    "periodicity": "daily",
    "aggregation": "total",
    "startDateTime": "2026-06-02T23:32:00Z",
    "endDateTime": "2026-06-03T06:34:00Z"
  },
  {
    "category": "activity",
    "type": "steps",
    "value": 8410,
    "unit": "count",
    "periodicity": "daily",
    "aggregation": "total",
    "startDateTime": "2026-06-02T00:00:00Z",
    "endDateTime": "2026-06-02T23:59:59Z"
  }
  // …heart rate record
]

OHealth (the OPPO/OnePlus companion app, formerly HeyTap Health) is an Android, Health-Connect-only integration — it uploads steps, heart rate, and sleep one-way to Health Connect. On iOS it writes steps only, so Sahha reads it through Health Connect on Android. Coverage is narrow and syncs can be slow, and OHealth keeps data on-device with no cloud backup.

Missing a metric you need? Talk to us in the Sahha Slack — if OHealth 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.

Build vs. buy

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

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

Every device
Build it yourself
  • Integrate Health Connect.
  • Handle Android version differences.
  • Add Apple Health separately for iOS.
With Sahha

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

Getting the data
Build it yourself
  • Write the Health Connect 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 Health Connect record types.
  • Reconcile against your iOS 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
  • Google changes a Health Connect API.
  • You find out in production.
With Sahha

We version the SDK. You never notice.

No OHealth developer account needed — Sahha reads what OHealth already writes to Health Connect on Android.

Setup

Live in an afternoon, not a sprint.

  1. # Add the Sahha SDKnpm install sahha-react-native
    01

    Add the Sahha SDK

    Drop the Sahha SDK into your Android app — or React Native or Flutter. The same SDK also covers Apple Health for your iOS sources.

  2. 02

    Prompt for Health Connect permissions

    Call the SDK to show the native Health Connect 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.

  3. Your app LIVE
    Sleep7h 12m
    Readiness82
    Heart rate62 bpm
    03

    Sahha reads and delivers

    Once permission is granted, the SDK reads OHealth data from Health Connect in the background, normalizes it to one schema, and streams it to your app by webhook or API.

Most teams read live OHealth data the same day they add the SDK. The only per-source prerequisite: your user has OHealth’s Health Connect 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

OHealth integration questions

How does Sahha get OHealth data?

OHealth uploads your OPPO or OnePlus wearable data to Health Connect on Android, and Sahha reads it from there with its mobile SDK — no OHealth API to integrate.

Which OHealth metrics does Sahha provide?

Steps, heart rate, and sleep — normalized into Sahha’s schema. OHealth’s Health Connect write is a one-way upload, and coverage is narrower than a full-featured wearable app.

Does the OHealth integration work on iOS?

OHealth writes only steps to Apple Health on iOS, so it’s effectively an Android, Health-Connect-only integration. On Android, Sahha reads the steps, heart rate, and sleep OHealth uploads to Health Connect.

Is the OHealth integration HIPAA and GDPR compliant?

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

More integrations

One API for every other source, too.

Add another wearable or app and the schema, webhooks, and scores are identical — no new pipeline to build.

Start streaming OHealth data today.

Connect once. Sahha handles consent, normalization, and real-time delivery — for OHealth and every other source.

Free for 30 days · No credit card

  • One API for OHealth and every other source
  • Real-time webhooks + on-demand REST, one normalized schema
  • Scores, archetypes & insights — no modeling required
  • HIPAA, GDPR & SOC 2 · your brand on the consent screen