Skip to main content
This page lists all supported data types, units, and formats. For provider-specific availability, see the Provider Coverage Matrix.
Not all providers support all data types. Check the Provider Coverage Matrix to see which metrics are available from each wearable device.

​
Timeseries Types

The types parameter in the timeseries endpoint accepts the following values:

​
Heart & Cardiovascular

​
Blood & Respiratory

​
Body Composition

​
Fitness Metrics

​
Activity - Basic

​
Activity - Distance

​
Activity - Walking Metrics

​
Activity - Running Metrics

​
Activity - Swimming

​
Activity - Generic

​
Environmental

Additional environmental types (environmental_sound_reduction, time_in_daylight, water_temperature) are defined but not currently supported by any provider.

​
Garmin-Specific

​
Other

​
Workout Types

Common workout types returned by the events/workouts endpoint. This is not an exhaustive list - the API supports 100+ workout types:
Workout types are normalized from provider-specific values. The original provider type is preserved in the raw data.
Filter the list by exact type with ?type=running. The older record_type parameter matches a substring, so record_type=running also returns trail_running; it is kept for backwards compatibility. To offer only the types a user actually has, read them from GET /api/v1/users/{user_id}/events/workouts/types, which returns a sorted list such as ["cycling", "running", "trail_running"]. Heart-rate zones, power zones and lap segments are omitted by default because they multiply the payload size. Request them explicitly with ?include=zones and ?include=segments (repeat the parameter to ask for both). Sleep sessions follow the same rule: sleep_stage_intervals is omitted unless you pass ?include=stages on /events/sleep.

​
Resolution Options

The resolution parameter for timeseries aggregation: Buckets are grouped per data source, so two devices reporting the same minute stay two points. Rate metrics (heart rate, power) are averaged and counters (steps, energy) are summed. A provider’s own daily total is skipped, since it is not a point in an intraday series — use /summaries for per-day figures.

​
Example: Fetching Multiple Types

Leave types empty to fetch all available data types for the user.

​
Provider Support

Data availability varies by provider. Here’s a quick summary:
  • ✅ Full support — Fully implemented
  • ◐ Partial — Limited data (e.g., workouts only)
  • 🔜 Coming soon — API supports, processing not yet implemented
  • ❌ Not available — Not supported

Full Provider Coverage Matrix

See detailed breakdown of which data types each provider supports, including provider-specific quirks and normalization details.