Stream asken nutrition data. Straight from the phone.
asken (あすけん) is Japan’s largest nutrition and diet-logging app, and it writes logged calories, macros, weight, and body fat to Apple Health — Sahha’s SDK reads them into your app as normalized biomarkers, alongside every other source.
- On-device
- Apple Health
- iOS
- HIPAA
- GDPR
Free for 30 days · No credit card
- Energy
- 1,740 kcal
- Protein
- 78 g
- Weight
- 61.4 kg
Identical schema across 500+ sources
Your users connect asken. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every asken 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
asken 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 — asken today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What asken 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
asken, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Logged calories and macros, plus weight and body fat pass through Apple Health; some app-exclusive metrics may not.
Nutrition
4
HealthKitSahha- dietaryEnergyConsumedenergy_intakekcal
- dietaryProteinprotein_intakeg
- dietaryFatTotalfat_intakeg
- dietaryCarbohydratescarbohydrate_intakeg
Body
2
HealthKitSahha- bodyMassweightkg
- bodyFatPercentagebody_fat%
See a real payload
{
"type": "HKQuantityTypeIdentifierDietaryEnergyConsumed",
"value": 1740,
"unit": "kcal",
"startDate": "2026-06-02T00:00:00Z",
"endDate": "2026-06-02T23:59:59Z",
"sourceRevision": { "source": { "name": "あすけん" } }
// …protein, fat, carbohydrate, weight & body fat samples
}[
{
"category": "nutrition",
"type": "energy_intake",
"value": 1740,
"unit": "kcal",
"periodicity": "daily",
"aggregation": "total",
"startDateTime": "2026-06-02T00:00:00Z",
"endDateTime": "2026-06-02T23:59:59Z"
}
// …5 more normalized logs
]asken data is only as complete as the user’s logging — a skipped meal is a gap in the day, not a zero, so treat coverage as self-reported. asken’s registered-dietitian scoring and advice stay inside its own app; what crosses to Apple Health is the underlying energy, macros, weight, and body fat. If you’re building for a Japanese user base, asken is a strong nutrition source — it’s the largest diet-logging app in the market.
Missing a metric you need? Talk to us in the Sahha Slack — if asken 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 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.
- Integrate Apple Health.
- Handle iOS version differences.
- Add Health Connect separately for Android.
One SDK covers Apple Health, Health Connect, and every cloud source.
- Write the HealthKit queries.
- Request the right permissions.
- Wire up background delivery.
The SDK handles queries, permissions, and background sync.
- Dedupe apps writing the same metric.
- Map dozens of HealthKit types.
- Reconcile against your Android sources.
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 changes a HealthKit API.
- You find out in production.
We version the SDK. You never notice.
No asken developer account needed — Sahha reads what asken already writes to Apple Health on iOS.
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 app — or React Native or Flutter. The same SDK also covers Health Connect for your Android sources.
- A
Allow “your app”
ConnectSleepActivityHeart rate02Prompt 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 LIVESleep7h 12mReadiness82Heart rate62 bpm03
Sahha reads and delivers
Once permission is granted, the SDK reads asken 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 asken data the same day they add the SDK. The only per-source prerequisite: your user has asken’s Apple Health 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.
asken integration questions
How does Sahha get asken data?
asken writes logged calories, macros, weight, and body fat to Apple Health, and Sahha reads them from there with its mobile SDK, delivering them as normalized biomarkers — no asken API to integrate.
Why is asken a good source for Japanese users?
asken (あすけん) is the largest nutrition and diet-logging app in Japan, built around meal photo logging with dietitian feedback. If your user base is Japanese, it’s the nutrition source they’re most likely to already be using — and it lands in the same normalized schema as every other source you read.
How complete is the nutrition data?
As complete as the user’s logging. Nutrition biomarkers reflect what someone recorded, so an unlogged meal shows up as a missing entry rather than a zero. Build for gaps — trend over days rather than treating any single day as a full intake picture.
Does the asken integration work on Android?
Not today. There’s no confirmed Health Connect write path from asken, so Sahha reads asken through Apple Health on iOS. Your users’ other Android sources still flow through the same Sahha SDK.
Is the asken integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and asken 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 asken data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for asken and every other source.
Free for 30 days · No credit card
- One API for asken 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