Question 1

How do I integrate Sahha into my app?

Accepted Answer

Sahha offers two integration paths: Mobile SDK: Passively collect and stream health data from the device. Use this for iOS, Android, Flutter, React Native, Expo, or Ionic Capacitor apps. REST API: Pull-style access for dashboards, admin workflows, or when you cannot receive inbound webhooks.

Question 2

What is the recommended Sahha integration architecture?

Accepted Answer

Mobile: Configure the SDK at startup → authenticate a user profile → request sensor permission → stream data. Backend: Receive webhook events → map users via X-External-Id → store with idempotency → trigger product logic (nudges, segmentation, analytics).

Question 3

What is the fastest way to test Sahha with real device data?

Accepted Answer

Use the Sahha Demo App and sync it to your dashboard via the QR flow. This validates end-to-end ingestion and dashboard visibility before you write any code.

Question 4

Can multiple team members test Sahha under one dashboard account?

Accepted Answer

Yes. Have multiple teammates sync the Sahha Demo App into the same dashboard account. This generates diverse real-world data quickly for QA and internal testing.

Question 5

Where can I find Sahha sample projects or example apps?

Accepted Answer

Use the Sahha Example Apps to bootstrap a working integration. Each platform (iOS, Android, Flutter, React Native, Expo, Ionic Capacitor) has its own setup guide.

Question 6

When should I use Sahha webhooks vs REST API polling?

Accepted Answer

Webhooks: Best for always-on pipelines and near real-time updates. Sahha pushes events to your endpoint. REST API polling: Best for dashboards, occasional sync jobs, or when you cannot receive inbound webhooks.

Question 7

What is the difference between Sahha sandbox and production?

Accepted Answer

Sandbox: For testing and demos. Uses test or simulated data. Safe to experiment without affecting real users. Production: The live environment. Uses real user data, powers actual health scores, and any changes impact end users directly.

Question 8

What are the minimum iOS requirements for the Sahha SDK?

Accepted Answer

iOS 14+ and Swift 5+. See the iOS setup guide for full installation steps.

Question 9

What are the minimum Android requirements for the Sahha SDK?

Accepted Answer

Android 14+. See the Android setup guide for full installation steps.

Question 10

Which mobile platforms does the Sahha SDK support?

Accepted Answer

The Sahha SDK supports iOS , Android , Flutter , React Native , Expo , and Ionic Capacitor . Install guides are available for each platform.

Question 11

When should the SDK be configured?

Accepted Answer

Configure once at app startup . Authenticate a profile per user . This avoids sensor/auth state issues and keeps environment routing consistent.

Question 12

How do I avoid sending Sahha data to the wrong environment?

Accepted Answer

Set SahhaEnvironment correctly. Sandbox for testing, production for release. Environment mismatch is a top “no data” cause.

Question 13

Why does getSensorStatus return pending on app launch?

Accepted Answer

Sensor status is pending until the SDK is configured. Call getSensorStatus after configure , typically in the configure callback.

Question 14

We’re seeing breaking changes between SDK versions—where do we check?

Accepted Answer

Check the Changelog / Updates for breaking changes, deprecations, and renamed methods. For platform-specific details, see the SDK GitHub repos for release notes.

Question 15

What is externalId in Sahha?

Accepted Answer

Your stable, unique user identifier (string). It’s the join key between your user and Sahha data delivery, and appears in webhooks via X-External-Id .

Question 16

Can I use email or username as Sahha externalId?

Accepted Answer

No. Use an anonymous stable ID (e.g. UUID). Emails and usernames can change and create privacy and lifecycle issues. Keep externalId immutable.

Question 17

What happens if a user externalId changes in Sahha?

Accepted Answer

Treat it as a new identity. Sahha will map data to a new profile. Best practice: keep externalId immutable. If you must change it, expect data to split across profiles.

Question 18

What are clientId and clientSecret used for in Sahha?

Accepted Answer

They mint an account token (server credential) for admin-style API actions, such as profile registration. Use them server-side only; never ship them in client code.

Question 19

What is a Sahha Account Token?

Accepted Answer

An account token is a server-side credential obtained by exchanging clientId and clientSecret. Use it for account-level actions like registering or authenticating profiles via the API.

Question 20

What is a Sahha Profile Token?

Accepted Answer

A user-scoped token returned when you authenticate/register a profile. Use it to access that user’s data.

Question 21

Can I authenticate Sahha profiles via API instead of SDK?

Accepted Answer

Yes. Call POST /oauth/profile/register with Authorization: Account &#x3C;ACCOUNT_TOKEN> and a JSON body { externalId }. Store the returned profileToken and refreshToken.

Question 22

Should I store Sahha credentials in the mobile app?

Accepted Answer

No. Never ship clientId, clientSecret, or tokens in client code. Fetch credentials or tokens from your server on app launch.

Question 23

How do I request Apple Health (HealthKit) permissions for Sahha?

Accepted Answer

Use enableSensors to trigger the HealthKit permission dialog. You should also provide an in-app explanation of “why” you’re requesting access and how scores work for transparency.

Question 24

How do we request Android Health Connect permissions?

Accepted Answer

Use enableSensors , and ensure Health Connect is available on-device. Provide a pathway to open settings so users can adjust permissions later.

Question 25

How do users re-enable health permissions after denying Sahha?

Accepted Answer

Route them to device settings. On Android, you can open Health Connect and instruct the user to enable data types for your app.

Question 26

Why do Android builds or Play Store reviews fail after adding Sahha sensors?

Accepted Answer

For Android, every sensor you request via getSensorStatus / enableSensors needs matching manifest permissions. Misalignment can cause build errors and review issues.

Question 27

What sensors does Sahha use and how do I manage them?

Accepted Answer

Sahha abstracts device sensors via the SDK (bridge to Apple HealthKit / Health Connect). You typically: configure → check sensor status → request via enableSensors .

Question 28

Why did my iOS app terminate after HealthKit permissions changed in Settings?

Accepted Answer

iOS may terminate apps if HealthKit permissions change while the app is in the background. Your UX should anticipate relaunch and re-check sensor status on next open.

Question 29

What is the difference between Sahha biomarkers and data logs?

Accepted Answer

Data Logs (raw intraday records): delivered in real time via webhooks as soon as a new record arrives. Ideal for custom time-series windows (e.g., 15-minute or hourly aggregations). Biomarkers (daily aggregates &#x26; summaries): delivered via webhook on your chosen cadence or available via API. Biomarkers provide daily totals directly (e.g., total calories, total steps).

Question 30

How do I fetch Sahha health scores via the SDK?

Accepted Answer

Call getScores for the authenticated profile. For server-side ingestion, use score webhook events instead of polling.

Question 31

How do I fetch Sahha biomarkers via the SDK?

Accepted Answer

Call getBiomarkers for the authenticated profile. For backend ingestion, subscribe to biomarker webhook events.

Question 32

What are “Stats” and when should we use them?

Accepted Answer

Stats are real-time rolling calculations over the current day (useful for “today so far” metrics like steps). They’re great for in-app live feedback.

Question 33

What data points does Sahha capture?

Accepted Answer

Use the Data Dictionary for the full, up-to-date list of data points Sahha passively collects from smartphones and wearables (Apple Watch, Garmin, Fitbit, Samsung, Oura, and more). It includes scores, biomarkers, archetypes, insights, and data logs, plus whether a smartwatch or wearable is required and how each metric is delivered.

Question 34

What non-wearable data can Sahha capture?

Accepted Answer

Any metric marked Requires Wearable = No in the Data Dictionary can be captured from phone-only sources. Scores also work with smartphone data alone ; wearables add additional factors.

Question 35

What exercise types does Sahha capture?

Accepted Answer

Sahha captures 50+ exercise types, including running, cycling, swimming, and strength training. See the Data Dictionary for the full list.

Question 36

How often does Sahha upload or deliver data?

Accepted Answer

Scores and biomarkers update throughout the day; webhooks let you control delivery frequency using the interval setting. Real-time is available, or you can batch updates (1–720 minutes). Data logs are always delivered in real time.

Question 37

What are Sahha Archetypes and Insights for developers?

Accepted Answer

Archetypes: segmentation labels derived from longer-term patterns. Insights: trends/comparisons over time. Both are available via webhooks/events for backend automation.

Question 38

How do Sahha webhooks work?

Accepted Answer

Sahha pushes events you subscribe to (scores, biomarkers, archetypes, insights, raw logs) so you don’t have to poll. This is the preferred approach for most production pipelines.

Question 39

What headers do Sahha webhooks send?

Accepted Answer

Sahha webhooks send at least two headers: X-Signature (for verifying the request came from Sahha) and X-External-Id (to map the event to your user).

Question 40

How do I verify a Sahha webhook signature?

Accepted Answer

Compute an HMAC over the raw request body bytes using your webhook secret and compare to X-Signature . Common failure: re-serializing JSON (whitespace/order changes) instead of hashing the raw payload.

Question 41

What’s the webhook “interval” and why don’t we get every update?

Accepted Answer

The interval is a deduplication/batching window for scores + biomarkers . Updates within the window are held; only the final value is delivered at interval end.

Question 42

Are Sahha data logs batched like scores and biomarkers?

Accepted Answer

No. Data log events (e.g., DataLogReceivedIntegrationEvent ) are always delivered immediately because each log is new raw data.

Question 43

Where do I find Sahha webhook event schemas?

Accepted Answer

Use the Sahha Event Reference in the webhooks docs for field-by-field payload structure and examples.

Question 44

How should I design Sahha webhook handlers?

Accepted Answer

Make handlers idempotent and fast: accept duplicates/retries, return 2xx quickly, and use event id (or a deterministic key) for de-duping in storage/queues.

Question 45

How do I quickly validate my Sahha webhook endpoint?

Accepted Answer

Log inbound headers ( X-External-Id , X-Signature ) + request body, validate signature logic, and confirm event parsing against the Event Reference.

Question 46

Sahha scores or biomarkers aren’t showing—what’s what should I check?

Accepted Answer

Check: (1) environment match (sandbox/prod), (2) profile authenticated, (3) permissions granted (Apple Health/Health Connect), (4) verify device actually has data, (5) if using webhooks, confirm interval expectations.

Question 47

Why do I see data in the Sahha dashboard but not in API or webhooks?

Accepted Answer

Classic environment mismatch: SDK sending to sandbox while backend/webhooks configured for production (or vice versa). Align environments and tokens across systems.

Question 48

How long until Sahha scores and biomarkers update after new data?

Accepted Answer

Often near real-time, but webhooks can be delayed by interval batching for scores/biomarkers. Raw logs remain immediate, so they’re a good signal for “data is flowing.”

Question 49

Why do I get Sahha webhooks but not for every score change?

Accepted Answer

Usually not a bug—your webhook interval is batching updates and delivering the final value at window end. If you need every update, set interval to real-time.

Question 50

Webhooks arrive, but we can’t map them to our users

Accepted Answer

Use X-External-Id header to map to your user record. This is why externalId must be stable and unique.

Question 51

Why does Sahha webhook signature verification fail intermittently?

Accepted Answer

Ensure you HMAC the raw request body exactly as received. Avoid parsing + re-stringifying JSON before hashing.

Question 52

Why am I getting 401 Unauthorized from the Sahha API?

Accepted Answer

Most common causes: wrong token type (Account vs Profile), expired/invalid token, or environment mismatch. Confirm you’re using the correct auth scheme for the endpoint.

Question 53

Android users can’t connect Health Connect

Accepted Answer

Confirm Health Connect is installed/available, permissions are granted for the requested data types, and your app provides a path to open Health Connect settings.

Question 54

We want “live” in-app metrics (e.g., steps today)

Accepted Answer

Use Stats (real-time daily rollups) and/or Samples (raw recent values). Use webhooks for backend automation, not for tight UI loops.

Question 55

What do I need for App Store and Play Store submission with Sahha?

Accepted Answer

Follow Sahha’s app submission guidance. Common requirements: clearly explain what health data you access and why, and provide transparency resources for displayed scores.

Question 56

What should my iOS App Store description include for Sahha health data?

Accepted Answer

Describe which health data you collect and why (purpose + benefit to user), and ensure App Privacy answers align with actual data usage.

Question 57

What should I prepare for Google Play review with Sahha?

Accepted Answer

Pay attention to permissions that require review (e.g., Foreground Service Health / Health Connect), and ensure requested permissions match your manifest + in-app behavior.

Question 58

Do I need scientific references when displaying Sahha scores in my app?

Accepted Answer

If you present health scores in a “medical-ish” context, include accessible scientific references/links for transparency (Sahha provides recommended references).

Question 59

What is required when displaying Garmin-sourced data from Sahha?

Accepted Answer

Garmin requires attribution (e.g., “Garmin [device model]”) next to Garmin-sourced data. Implement by storing device/source info from raw log events and showing it in UI/exports.

Developer FAQ

Getting started

Dashboard

SDK

Profiles

Permissions

Data

Webhooks

Troubleshooting

App Store