❓ Frequently Asked Questions
Everything you need to know about biomarkers, health data APIs, and integration
Everything you need to know about biomarkers, health data APIs, and integration
This FAQ covers common questions about biomarkers, health data APIs, wearable integration, intelligence layers, and choosing the right platform for your application. Jump to a specific topic or browse all questions below.
Biomarkers are measurable indicators of health status. They include:
Biomarkers transform raw sensor data into actionable health insights.
The comprehensive biomarker table includes 54 distinct biomarkers across five categories:
View the complete biomarker table for details on each metric.
Biomarkers are raw measurements (e.g., "7,500 steps", "7 hours sleep"). Intelligence layers transform biomarkers into actionable insights:
Intelligence layers enable personalization, churn prediction, and automated interventions. Learn more about intelligence layers and scores.
No. Many biomarkers can be collected from smartphones without any wearable device:
Smartphone-only biomarkers (no wearable needed):
Wearable-required biomarkers:
Using smartphone data alone provides ~40% coverage, while adding wearables increases coverage to 100%.
Smartphone-based sleep tracking (using accelerometer and usage patterns) can accurately detect:
Smartphones cannot accurately detect:
For basic sleep insights, smartphones work well. For clinical-grade sleep analysis, wearables are recommended.
Major health data API platforms support 300+ wearable devices through platform integrations:
Using HealthKit + Health Connect provides maximum coverage without needing individual device integrations.
The five core health scores (range 0.0-1.0) are:
All scores can be calculated from smartphone data alone (no wearable required). See the complete scores breakdown.
Behavioral archetypes are labels that classify users based on patterns. The 14 archetypes include:
Archetypes enable user segmentation, personalized content, and churn prediction. Example: "Highly Irregular Sleeper" with "Poor Mental Wellness" = high churn risk.
Trends analyze the last 4 complete weeks of data on a rolling basis. For each metric, the system:
Why trends matter:
Trends are available for 5 scores + 17 factors. Learn more about trend analysis.
Comparisons provide three reference points to contextualize metrics:
Example use cases:
Comparisons enable social motivation, personalized goal-setting, and progress celebration.
There are three primary ways to access health data:
1. Direct Device OAuth
Connect directly to device APIs (Fitbit, Garmin, Oura, etc.)
2. Platform APIs (Unified Health Data)
Use aggregation platforms (Sahha, Terra, Vital, Rook) that connect to HealthKit/Health Connect
3. Smartphone Monitoring
Collect data from smartphone sensors (accelerometer, screen time, location)
Best approach: Platform API + smartphone monitoring for maximum coverage.
Integration timelines vary by approach:
For reference: Building direct integrations with 10 wearable devices = 5-10 years of engineering time vs 2-4 weeks with a platform API.
Platform API pricing typically follows these models:
Cost comparison: Platform API ($1-2/user/month) vs direct integration ($500K-$2M engineering + maintenance).
For most applications, platform APIs are 10-100x more cost-effective than building direct integrations.
Platform selection depends on your needs:
Key decision factors:
See the detailed platform comparison on the homepage.
You need intelligence layers if you want to:
You don't need intelligence layers if you:
For most applications, intelligence layers dramatically reduce engineering complexity and time-to-market.
Health data APIs typically provide data via:
Recommended architecture: Webhooks for real-time updates + REST API for historical data retrieval.
Data refresh rates vary by source:
Most platforms support near-real-time delivery via webhooks within minutes of device sync.
Health data APIs typically use:
User flow: User authorizes via OAuth → receives token → your backend uses token to fetch data via API.
Health data APIs are used across 9+ industries:
See detailed industry use cases on the homepage.
Declining health metrics correlate strongly with membership cancellation. Churn prediction models use:
Example model: Users showing declining sleep quality + reduced activity + poor mental wellness archetype have 3.2x higher churn risk in next 30 days.
Early detection enables proactive interventions 2-3 weeks before cancellation.
Reputable health data API platforms implement:
Key principle: Users own their data and can revoke access at any time.
Health data is subject to multiple regulations:
Important: Consumer wellness apps (non-diagnostic) typically don't require HIPAA compliance, but must follow GDPR/CCPA. Consult legal counsel for your specific use case.
Yes. GDPR and CCPA require data deletion upon request. Health data platforms must provide:
Your application must implement similar user data controls to comply with privacy regulations.