Skip to content
HealthSync Docs

Trackers & Data Coverage

This page maps each implemented tracker in HealthSync to the canonical event types it can produce after fetch and normalization. Use the filters to narrow by stream or tracker, then check the event types your product needs to see which integrations cover them.

Filter by stream

Filter by tracker

Highlight requirements

Check the event types your product needs. Trackers that cover every selected type are highlighted.

Event type Stream Fitbit OAuth + subscriber webhooks for activities, sleep, body, and nutrition collections. Garmin OAuth + ping/pull wellness summaries (callbackURL fetch pipeline). Google Health OAuth + signed webhook notifications with interval-scoped v4 data point fetches. Polar OAuth + AccessLink webhooks for exercise, sleep, heart rate, and daily summaries. Mock Provider Local development provider for end-to-end pipeline testing.
Activity activity Session
Sleep sleep Session
Body measurement body_measurement Snapshot Weight, height, and body fat via separate webhook data types.
Blood pressure blood_pressure Snapshot
Blood glucose blood_glucose Snapshot
Blood work blood_work Snapshot
Temperature temperature Snapshot
Nutrition nutrition Snapshot
Hydration hydration Snapshot
Heart rate series heart_rate_series Timeseries Enqueued from the activities subscriber collection. Heart rate appears inside activity/sleep/daily summaries, not as a standalone series event.
Location series location_series Timeseries Emitted when an activity payload includes GPS samples. Emitted when an exercise payload includes route coordinates.
SpO2 series spo2_series Timeseries
Stress series stress_series Timeseries
Daily summary daily_summary Aggregate Steps, distance, floors, and active energy map into daily summary fields.
User profile user_profile Profile Fetched automatically after connect. Fetch path exists; not auto-enqueued on connect today. Fetch path exists; not auto-enqueued on connect today.

Legend

  • Supported — fetch + normalization path is implemented for this canonical event type.
  • Partial — available only for some payloads, provider-specific data types, or manual fetch paths.
  • Not supported — no adapter path in this repository yet.
Section titled “Related docs”