MyNetDiary Integration

Stream MyNetDiary data. No MyNetDiary API needed.

MyNetDiary writes your logged meals — calories, protein, carbs, fat, and water — to Apple Health, and Sahha’s SDK reads them into your app as normalized nutrition biomarkers, alongside every other source.

  • On-device
  • Apple Health
  • iOS
  • HIPAA
  • GDPR

Free for 30 days · No credit card

MyNetDiary logo
Normalized Auto-synced
Energy
2,060 kcal
Protein
141 g
Water
2.3 L

Identical schema across 500+ sources

How it works

Your users connect MyNetDiary. Sahha does the rest.

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

Apple Health 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

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

Data coverage

What MyNetDiary 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

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

  • What crosses the bridge

    Calories, macros, water, and micronutrients pass through Apple Health; some app-exclusive metrics may not.

Nutrition

5
HealthKitHealthKitSahha
  • dietaryEnergyConsumedenergy_intakekcal
  • dietaryProteinprotein_intakeg
  • dietaryCarbohydratescarbohydrate_intakeg
  • dietaryFatTotalfat_intakeg
  • dietaryWaterwater_intakeL
See a real payload
HealthKit · nutrition
{
  "type": "HKQuantityTypeIdentifierDietaryEnergyConsumed",
  "value": 2060,
  "unit": "kcal",
  "startDate": "2026-06-02T00:00:00Z",
  "endDate": "2026-06-02T23:59:59Z",
  "sourceRevision": { "source": { "name": "MyNetDiary" } }
  // …protein, carbs, fat, water & micronutrient samples
}
Sahha · normalized
[
  {
    "category": "nutrition",
    "type": "energy_intake",
    "value": 2060,
    "unit": "kcal",
    "periodicity": "daily",
    "aggregation": "total",
    "startDateTime": "2026-06-02T00:00:00Z",
    "endDateTime": "2026-06-02T23:59:59Z"
  },
  {
    "category": "nutrition",
    "type": "protein_intake",
    "value": 141,
    "unit": "gram",
    "periodicity": "daily",
    "aggregation": "total",
    "startDateTime": "2026-06-02T00:00:00Z",
    "endDateTime": "2026-06-02T23:59:59Z"
  }
  // …3 more normalized logs
]

MyNetDiary writes calories, macros, and water to Apple Health — plus a range of micronutrients where logged. It’s an iOS integration, so its data lands in Apple Health; on Android its nutrition export goes to Samsung Health rather than Health Connect.

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

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 MyNetDiary developer account needed — Sahha reads what MyNetDiary already writes to Apple Health on iOS.

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 iOS app — or React Native or Flutter. The same SDK also covers Health Connect for your Android sources.

  2. 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.

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

    Sahha reads and delivers

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

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

MyNetDiary integration questions

How does Sahha get MyNetDiary data?

MyNetDiary writes your logged calories, macros, and water to Apple Health, and Sahha reads them from there with its mobile SDK — no MyNetDiary API to integrate.

Which MyNetDiary metrics does Sahha provide?

Calories, protein, carbohydrates, fat, and water — plus the micronutrients MyNetDiary logs — normalized into Sahha’s Nutrition biomarker category.

Does the MyNetDiary integration work on Android?

MyNetDiary writes nutrition to Apple Health on iOS, which is where Sahha reads it. On Android its nutrition export targets Samsung Health rather than Health Connect. The same Sahha SDK also reads Health Connect for your other sources.

Is the MyNetDiary integration HIPAA and GDPR compliant?

Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and MyNetDiary 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 MyNetDiary data today.

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

Free for 30 days · No credit card

  • One API for MyNetDiary 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