Flo Integration

Stream Flo data. No Flo API needed.

Flo writes menstrual flow, ovulation tests, and cervical mucus to Health Connect — and Sahha’s SDK reads them into your app as normalized reproductive tags, alongside every other source.

On-device
Health Connect
Android
HIPAA
GDPR

Start building Read the SDK docs

Free for 30 days · No credit card

Normalized Auto-synced

Menstrual flow: Light
Ovulation test: High
Cervical mucus: Watery

Identical schema across 500+ sources

How it works

Your users connect Flo. Sahha does the rest.

This is your user’s side of the story — one screen, once. Sahha ingests every Flo 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

Flo 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 — Flo today, a new watch next year — flows through the same SDK with no extra prompt and no new code.

Data coverage

What Flo syncs through Health Connect.

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
Flo, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Menstrual flow, ovulation tests, and cervical mucus pass through Health Connect; some app-exclusive metrics may not.

Cycle & reproductive

Health ConnectSahha

MenstruationFlowRecordmenstrual_flowlight–heavy
OvulationTestRecordovulation_testneg–positive
CervicalMucusRecordcervical_mucusdry–egg white
IntermenstrualBleedingRecordintermenstrual_bleedingevent
SexualActivityRecordsexual_activityprotected/unprotected

See a real payload

Health Connect · cycle

{
  "record": "MenstruationFlowRecord",
  "flow": "FLOW_LIGHT",
  "time": "2026-06-03T08:00:00Z",
  "metadata": { "dataOrigin": "flo.period.tracker.calendar" }
  // …ovulation test & cervical mucus records
}

Sahha · normalized

[
  {
    "category": "reproductive",
    "type": "menstrual_flow",
    "value": "light",
    "startDateTime": "2026-06-03T00:00:00Z",
    "endDateTime": "2026-06-03T23:59:59Z"
  }
  // …ovulation_test & cervical_mucus tags
]

Flo writes cycle-tracking entries to Health Connect, which Sahha delivers as reproductive tags (event values like menstrual_flow: light) via API and webhooks. Flo syncs to Health Connect on Android; its Apple Health sync has been discontinued, so it lands in Health Connect, not Apple Health.

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

Build it yourself

With Sahha

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 Flo developer account needed — Sahha reads what Flo already writes to Health Connect on Android.

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 Android app — or React Native or Flutter. The same SDK also covers Apple Health for your iOS sources.
A
Allow “your app”
Sleep
Activity
Heart rate
Connect
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.
Your app LIVE
Sleep7h 12m
Readiness82
Heart rate62 bpm
03
Sahha reads and delivers
Once permission is granted, the SDK reads Flo data from Health Connect 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 Flo data the same day they add the SDK. The only per-source prerequisite: your user has Flo’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

Flo integration questions

How does Sahha get Flo data?

Flo writes cycle-tracking entries to Health Connect, and Sahha reads them from there with its mobile SDK, delivering them as normalized reproductive tags — no Flo 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.

Does the Flo integration work on iOS?

Sahha reads Flo through Health Connect on Android — Flo’s Apple Health sync has been discontinued. The same Sahha SDK still reads Apple Health on iOS for your other sources, all normalized to one schema.

Do I need a mobile app to use the Flo integration?

Yes. Because Flo data lands in 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 Flo do.

Is the Flo integration HIPAA and GDPR compliant?

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