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.

Note

Coverage reflects what is implemented in this repository today — not every data type a vendor exposes in their public API. Green ticks mean implemented, warning signs mean conditional or partial support, and red crosses mean no adapter path yet.

Streams All

Session Snapshot Timeseries Aggregate Profile

Trackers All

Fitbit Garmin Google Health Polar Mock Provider

Required events None

activity — Activity sleep — Sleep body_measurement — Body measurement blood_pressure — Blood pressure blood_glucose — Blood glucose blood_work — Blood work temperature — Temperature nutrition — Nutrition hydration — Hydration heart_rate_series — Heart rate series location_series — Location series spo2_series — SpO2 series stress_series — Stress series daily_summary — Daily summary user_profile — User profile

Hide unsupported rows Hide partial-only rows

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	✓ Supported	✓ Supported	✓ Supported Exercise data points, including the steps/distance fallback fetch path.	✓ Supported	✓ Supported
Sleep sleep	Session	✓ Supported	✓ Supported	✓ Supported	✓ Supported	✕ Not supported
Body measurement body_measurement	Snapshot	✓ Supported	✓ Supported	✓ Supported Weight, height, and body fat via separate webhook data types.	✕ Not supported	✓ Supported
Blood pressure blood_pressure	Snapshot	✕ Not supported	✓ Supported	✕ Not supported	✕ Not supported	✕ Not supported
Blood glucose blood_glucose	Snapshot	✕ Not supported	✕ Not supported	✓ Supported Blood glucose webhook data type maps directly to the canonical snapshot.	✕ Not supported	✕ Not supported
Blood work blood_work	Snapshot	✕ Not supported	✕ Not supported	✕ Not supported	✕ Not supported	✕ Not supported
Temperature temperature	Snapshot	✕ Not supported	✕ Not supported	✕ Not supported	✕ Not supported	✕ Not supported
Nutrition nutrition	Snapshot	✓ Supported	✕ Not supported	✕ Not supported	✕ Not supported	✕ Not supported
Hydration hydration	Snapshot	✓ Supported	✕ Not supported	✕ Not supported	✕ Not supported	✕ Not supported
Heart rate series heart_rate_series	Timeseries	✓ Supported Enqueued from the activities subscriber collection.	✕ Not supported Heart rate appears inside activity/sleep/daily summaries, not as a standalone series event.	✓ Supported	✓ Supported	✓ Supported
Location series location_series	Timeseries	✕ Not supported	⚠ Partial coverage Emitted when an activity payload includes GPS samples.	⚠ Partial coverage Emitted from exercise payloads when TCX export returns GPS samples.	⚠ Partial coverage Emitted when an exercise payload includes route coordinates.	✕ Not supported
SpO2 series spo2_series	Timeseries	✕ Not supported	✕ Not supported	✓ Supported Oxygen saturation and daily oxygen saturation webhook data types.	✕ Not supported	✕ Not supported
Stress series stress_series	Timeseries	✕ Not supported	✕ Not supported	✕ Not supported	✕ Not supported	✕ Not supported
Daily summary daily_summary	Aggregate	✓ Supported	✓ Supported	✓ Supported Steps, distance, floors, and active energy map into daily summary fields.	✓ Supported	✓ Supported
User profile user_profile	Profile	✓ Supported Fetched automatically after connect.	✕ Not supported	⚠ Partial coverage Fetch path exists; not auto-enqueued on connect today.	⚠ Partial coverage Fetch path exists; not auto-enqueued on connect today.	✓ Supported

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.

Related docs

• Provider metadata API — discover available providers and their datapoints from your backend
• Streams & event types — definitions for all 15 canonical event types
• Connecting users — OAuth connect flow for end users
• Daily summary — common aggregate shape across activity trackers