Active Zone Minutes: the Google Health API active-zone-minutes data type
Read from Google’s documentation on 2026-10-17 · discovery document revision 20261014 · Google’s data-types page last updated 2026-10-06
Active Zone Minutes (active-zone-minutes) is an Interval data type in the Google Health API. Google's data-types table lists list, reconcile, rollup and dailyRollup for it under the .activity_and_fitness.readonly and .activity_and_fitness.writeonly scopes, with a storage resolution of 1 minute. The table marks it with webhook support. Google's Fitbit migration table maps the Fitbit Web API's Active Zone Minutes data to it.
Active Zone Minutes at a glance
From the Active Zone Minutes row of Google’s data-types table, joined to the discovery document’s DataPoint schema.
- Display name
- Active Zone Minutes
- dataType (in endpoint URLs)
active-zone-minutes- filter parameter
active_zone_minutesGoogle: “The identifier separated by underscores (for example,active_minutes) used as the value for thedataTypefilter parameter in daily rollup and rollup requests.”- Record type
- Interval — Google: “Represents measurements recorded over a duration.”
- Storage resolution
- 1 minute
- Webhook support
- Yes · automatic-subscription token WEBHOOK_DATA_TYPE_ACTIVE_ZONE_MINUTES
- True zeros support
- Not marked in Google’s table
- Channel
- v4
- DataPoint field
DataPoint.activeZoneMinutes→ActiveZoneMinutesIts description: “Optional. Data for points in theactive-zone-minutesinterval data type collection, measured in minutes.”- Compatible devices
- 19 in Google’s table
Operations and request paths
The operations Google’s table lists for active-zone-minutes, each matched to its users.dataTypes.dataPoints method in the discovery document. The path is the documented path template (the method’s flatPath on https://health.googleapis.com/) with {dataTypesId} filled in as active-zone-minutes. Google on {user}: “The {user} can be either the alias me or the authenticated user's numeric Health User ID (retrieved via GetIdentity).”
| Table lists | Method | Documented path template |
|---|---|---|
list | list | GET https://health.googleapis.com/v4/users/{usersId}/dataTypes/active-zone-minutes/dataPoints |
reconcile | reconcile | GET https://health.googleapis.com/v4/users/{usersId}/dataTypes/active-zone-minutes/dataPoints:reconcile |
rollup | rollUpsame name, different case | POST https://health.googleapis.com/v4/users/{usersId}/dataTypes/active-zone-minutes/dataPoints:rollUp |
dailyRollup | dailyRollUpsame name, different case | POST https://health.googleapis.com/v4/users/{usersId}/dataTypes/active-zone-minutes/dataPoints:dailyRollUp |
Every method, and how many of the data types list it: the methods overview.
Scopes
The scopes Google’s table lists for active-zone-minutes, as full URLs, with the consent text Google’s Scopes page gives each. Every Google Health API scope.
| Scope | Access | Google’s permission text |
|---|---|---|
https://www.googleapis.com/auth/googlehealth.activity_and_fitness.readonly | read | See your Google Health activity and fitness data. |
https://www.googleapis.com/auth/googlehealth.activity_and_fitness.writeonly | write | Add activity and fitness data to Google Health, and edit or delete the data it adds. |
Fields of Active Zone Minutes
The schema the discovery document gives DataPoint.activeZoneMinutes, required fields first. Types are as the discovery document states them; the label is the word Google’s description opens with. The schemas its fields refer to follow, one level deep.
ActiveZoneMinutes — Google: “Record of active zone minutes in a given time interval.”
| Field | Type | Google’s description |
|---|---|---|
activeZoneMinutesRequired | string/int64 | Required. Number of Active Zone Minutes earned in the given time interval. Note: active_zone_minutes equals to 1 for low intensity (fat burn) zones or 2 for high intensity zones (cardio, peak). |
heartRateZoneRequired | string | Required. Heart rate zone in which the active zone minutes have been earned, in the given time interval.
|
intervalRequired | ObservationTimeInterval | Required. Observed interval. |
ObservationTimeInterval
Google: “Represents a time interval of an observed data point.”
| Field | Type | Google’s description |
|---|---|---|
endTimeRequired | string/google-datetime | Required. Observed interval end time. |
endUtcOffsetRequired | string/google-duration | Required. The offset of the user's local time at the end of the observation relative to the Coordinated Universal Time (UTC). |
startTimeRequired | string/google-datetime | Required. Observed interval start time. |
startUtcOffsetRequired | string/google-duration | Required. The offset of the user's local time at the start of the observation relative to the Coordinated Universal Time (UTC). |
civilEndTimeOutput only | CivilDateTime | Output only. Observed interval end time in civil time in the timezone the subject is in at the end of the observed interval |
civilStartTimeOutput only | CivilDateTime | Output only. Observed interval start time in civil time in the timezone the subject is in at the start of the observed interval |
Rollup fields
rollUp returns RollupDataPoint.activeZoneMinutes
The discovery document: “Returned by default when rolling up data points from the active-zone-minutes data type, or when requested explicitly using the active-zone-minutes rollup type identifier.”
ActiveZoneMinutesRollupValue — Google: “Represents the result of the rollup of the active zone minutes data type.”
| Field | Type | Google’s description |
|---|---|---|
sumInCardioHeartZone | string/int64 | Active zone minutes in HeartRateZone.CARDIO. |
sumInFatBurnHeartZone | string/int64 | Active zone minutes in HeartRateZone.FAT_BURN. |
sumInPeakHeartZone | string/int64 | Active zone minutes in HeartRateZone.PEAK. |
dailyRollUp returns DailyRollupDataPoint.activeZoneMinutes
The discovery document: “Returned by default when rolling up data points from the active-zone-minutes data type, or when requested explicitly using the active-zone-minutes rollup type identifier.”
The same ActiveZoneMinutesRollupValue as the rollUp result above.
Fitbit Web API predecessor
Google’s Fitbit Web API → Google Health API data-type table maps Active Zone Minutes to active-zone-minutes.
Fitbit Web API scopes Google maps to active-zone-minutes’s scopes: activity, cardio_fitness.
Google’s full Fitbit Web API mapping tables · the migration playbook
Compatible devices
The 19 devices Google’s table lists as able to record and sync active-zone-minutes.
- Fitbit Air
- Fitbit Charge 4
- Fitbit Charge 5
- Fitbit Charge 6
- Fitbit Inspire 2
- Fitbit Inspire 3
- Fitbit Ionic
- Fitbit Luxe
- Pixel Watch
- Pixel Watch 2
- Pixel Watch 3
- Pixel Watch 4
- Fitbit Sense
- Fitbit Sense 2
- Fitbit Versa
- Fitbit Versa 2
- Fitbit Versa 3
- Fitbit Versa 4
- Fitbit Versa Lite
Google’s documentation
Related on this site
- Active Minutes API: Activity Intensity, Exercise Time and Sedentary Time — the metric on every platform this site covers, each type quoted in its platform's own words
- Heart Rate Zones API: Zone Thresholds and Time in Zone — the metric on every platform this site covers, each type quoted in its platform's own words
- Google Health API webhooks
- Verification and rate limits
- The Fitbit Web API turn-off
Questions
Which OAuth scopes does the Google Health API active-zone-minutes data type need?
Google's data-types table (read 2026-10-17) lists https://www.googleapis.com/auth/googlehealth.activity_and_fitness.readonly and https://www.googleapis.com/auth/googlehealth.activity_and_fitness.writeonly for active-zone-minutes. The Scopes page's consent text: .activity_and_fitness.readonly, "See your Google Health activity and fitness data."; .activity_and_fitness.writeonly, "Add activity and fitness data to Google Health, and edit or delete the data it adds."
Can apps write active zone minutes data to the Google Health API?
Not according to Google's data-types table, read 2026-10-17: it lists only list, reconcile, rollup and dailyRollup for active-zone-minutes, and no create, update or batchDelete operation.
How do you aggregate active-zone-minutes data with the Google Health API?
With the rollup methods Google's table lists for it. rollUp (POST https://health.googleapis.com/v4/users/{usersId}/dataTypes/active-zone-minutes/dataPoints:rollUp) returns RollupDataPoint.activeZoneMinutes, a ActiveZoneMinutesRollupValue with sumInCardioHeartZone, sumInFatBurnHeartZone and sumInPeakHeartZone; dailyRollUp (POST https://health.googleapis.com/v4/users/{usersId}/dataTypes/active-zone-minutes/dataPoints:dailyRollUp) returns DailyRollupDataPoint.activeZoneMinutes, a ActiveZoneMinutesRollupValue with sumInCardioHeartZone, sumInFatBurnHeartZone and sumInPeakHeartZone. Each field is described on this page as the discovery document describes it.
What did the Google Health API active-zone-minutes data type replace in the Fitbit Web API?
Google's Fitbit Web API migration table maps the Fitbit Web API's "Active Zone Minutes" to active-zone-minutes. The Fitbit Web API scopes Google maps to its scopes: activity and cardio_fitness.
Other activity and fitness data types
Sources checked
- Google Health API data types — last updated 2026-10-06 · read 2026-10-17
- Google Health API discovery document (v4) — revision 20261014 · read 2026-10-17
- Scopes — last updated 2026-10-09 · read 2026-10-17
- API specifications — last updated 2026-09-22 · read 2026-10-17
Google’s text is quoted for identification; each guide page’s footer reads: “Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License.”. Generated from Google’s pages by scripts/fetch-google-health-api.mjs, not typed by hand; Google’s documentation remains the authority.