This endpoint returns statistics calculated based on the data available for a specific time period. The data is aggregated according to the time interval specified in your request, allowing you to see trends and patterns over time.
Refer to the different statistics types in the Statistics Types section for more information on how the data is aggregated for each type.
The /statistics/interval endpoint uses Coordinated Universal Time (UTC) for all its calculations. This standardization ensures that data is consistent and comparable across different time zones. By using UTC, the API provides a global view of the data, which is crucial for applications that require a uniform time reference. This approach contrasts with the /statistics/daily endpoint, which uses the user’s local timezone for calculations, offering a more personalized view.
Within a single statistics interval there can be data aggregated from one provider source only.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Start time of the query range in UTC, inclusive
End time of the query range in UTC, non-inclusive
Interval of the query
1h Exclude manual metrics from the statistics
1steps, distance_total, distance_walking, distance_cycling, distance_running, calories_burned_basal, calories_burned_active, calories_burned_total, heartrate, heartrate_max, heartrate_min, heartrate_resting, sleep_skin_temperature_deviation, hrv_rmssd, hrv_sdnn strava, health_connect, fitbit, garmin, huawei, dexcom, whoop, withings, suunto, apple, freestyle_libre, oura, polar, coros, ultrahuman, samsung_health_data, luna Whether to include the record IDs in the response
Device types to include in the statistics
unknown, phone, watch, scale, ring, head_mounted, fitness_band, chest_strap, smart_display, accessory