Stream Ovia data. Straight from the phone.
Ovia writes menstrual flow, ovulation, and cervical mucus to Apple Health and Health Connect — and Sahha’s SDK reads them into your app as normalized reproductive tags, alongside every other source.
- On-device
- Apple Health + Health Connect
- HIPAA
- GDPR
Free for 30 days · No credit card
- Menstrual flow
- Medium
- Ovulation test
- Positive
- Cervical mucus
- Egg white
Identical schema across 500+ sources
Your users connect Ovia. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every Ovia signal, normalizes, deduplicates, and delivers it to your service — raw, or as refined intelligence your product can act on.
A Allow "your app"
On-device and permissioned
Ovia data is read on the user’s own device, only after they grant Apple Health or Health Connect permission — nothing syncs without consent.
One integration, every source
Permission is per data type, not per brand. Anything that writes to Apple Health or Health Connect — Ovia today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What Ovia syncs through Apple Health and Health Connect.
Request only what you need
You choose exactly which of these signals to request from Apple Health / Health Connect — users are only ever prompted for those, which keeps opt-in rates high.
One schema, every source
Ovia, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Menstrual flow, ovulation, and cervical mucus pass through the platform; some device-exclusive metrics may not.
Cycle & reproductive
4
HealthKit / Health ConnectSahha- menstrualFlowmenstrual_flowlight–heavy
- ovulationTestResultovulation_testneg–positive
- cervicalMucusQualitycervical_mucusdry–egg white
- sexualActivitysexual_activityprotected/unprotected
Body
1
HealthKit / Health ConnectSahha- bodyMassweightkg
See a real payload
{
"type": "HKCategoryTypeIdentifierMenstrualFlow",
"value": "HKCategoryValueMenstrualFlowMedium",
"startDate": "2026-06-03T00:00:00Z",
"endDate": "2026-06-03T23:59:59Z",
"sourceRevision": { "source": { "name": "Ovia" } }
// …ovulation test & cervical mucus samples
}[
{
"category": "reproductive",
"type": "menstrual_flow",
"value": "medium",
"startDateTime": "2026-06-03T00:00:00Z",
"endDateTime": "2026-06-03T23:59:59Z"
}
// …ovulation_test & cervical_mucus tags
]Ovia writes cycle-tracking entries and pregnancy weight to Apple Health on iOS and Health Connect on Android — one of the few cycle apps that covers both platforms. Sahha delivers them as reproductive tags and biomarkers via API and webhooks; predictions and articles stay in the Ovia app.
Missing a metric you need? Talk to us in the Sahha Slack — if Ovia 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.
Reading Apple Health and Health Connect yourself? Here’s the to-do list.
Everything on the left is yours to write, test, and maintain across two platforms. Everything on the right, Sahha already did.
- Integrate Apple Health.
- Then Health Connect, separately.
- Then reconcile the two.
One SDK covers Apple Health, Health Connect, and every cloud source.
- Write the HealthKit queries.
- Write the Health Connect queries.
- Wire up background delivery.
The SDK handles queries, permissions, and background sync.
- Dedupe apps writing the same metric.
- Map dozens of platform types.
- Normalize iOS against Android.
Deduped, typed, one schema — one stream per user.
- Build a sleep model.
- Build an activity model.
- Hire a data scientist.
Scores, archetypes, and insights — built in.
- Apple or Google changes an API.
- You find out in production.
We version the SDK. You never notice.
No Ovia developer account needed — Sahha reads what Ovia already writes to Apple Health and Health Connect.
Live in an afternoon, not a sprint.
- # Add the Sahha SDKnpm install sahha-react-native01
Add the Sahha SDK
Drop the Sahha SDK into your iOS or Android app — or React Native or Flutter. One dependency covers both Apple Health and Health Connect.
- A
Allow “your app”
ConnectSleepActivityHeart rate02Prompt for health permissions
Call the SDK to show the native Apple Health or 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.
- Your app LIVESleep7h 12mReadiness82Heart rate62 bpm03
Sahha reads and delivers
Once permission is granted, the SDK reads Ovia data from Apple Health / Health Connect in the background, normalizes it to one schema, and streams it to your app by webhook or API.
Most teams read live Ovia data the same day they add the SDK. The only per-source prerequisite: your user has Ovia’s Apple Health / Health Connect sync switched on — most source apps enable it by default.
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.
Ovia integration questions
How does Sahha get Ovia data?
Ovia writes cycle-tracking entries and pregnancy weight to Apple Health on iOS and Health Connect on Android, and Sahha reads them from there with its mobile SDK, delivering them as normalized reproductive tags and biomarkers — no Ovia API to integrate.
How is cycle data delivered — as biomarkers or tags?
As reproductive tags. Cycle entries are categorical events (menstrual_flow: light/medium/heavy, ovulation_test: negative/high/positive, cervical_mucus: dry/sticky/creamy/watery/egg_white), delivered through Sahha’s API and webhooks alongside biomarkers and scores.
Do I need a mobile app to use the Ovia integration?
Yes. Because Ovia data lands in Apple Health or Health Connect on the user’s device, you embed the Sahha mobile SDK to read it. Cloud-only sources like Oura don’t need the SDK, but on-device sources like Ovia do.
Is the Ovia integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and Ovia data flows through the same compliant pipeline as every other source.
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 Ovia data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for Ovia and every other source.
Free for 30 days · No credit card
- One API for Ovia 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