JSON Export Format
Complete documentation for the JSON export format structure
Last updated: October 31, 2026
On this page
JSON exports organize selected health data inside a data object. Main Manual Export combines selected data types into one JSON file; automations export the configured data type and date periods. Workout GPX routes, when requested through Manual Export, are separate files.
File structure
The following shows the available top-level arrays. An export may include only the selected data types that have data.
{
"data": {
"metrics": [],
"workouts": [],
"stateOfMind": [],
"medications": [],
"symptoms": [],
"cycleTracking": [],
"ecg": [],
"heartRateNotifications": []
}
}
Data types
| Array | Reference |
|---|---|
metrics |
Health Metrics, including sleep and basal body temperature |
workouts |
Workouts, with version-specific fields and optional routes |
stateOfMind |
State of Mind |
medications |
Medication dose events |
symptoms |
Symptoms |
cycleTracking |
Cycle Tracking |
ecg |
ECG |
heartRateNotifications |
Heart Rate Notifications |
Date formats
Most timestamps use yyyy-MM-dd HH:mm:ss Z, for example 2024-02-06 14:30:00 -0800. The offset identifies the time zone.
- State of Mind uses ISO 8601 timestamps.
- ECG voltage measurements and notification heart-rate measurements use Unix epoch seconds.
- Optional beat-to-beat HRV readings also include epoch timestamps; see Heart Rate Variability.
See each data type’s reference for its field formats and Workouts for the v1/v2 distinction.
Export data
Use Manual Export for a one-time export, or Automations for a configured destination.