Daily Heart Rate Zones: the Google Health API daily-heart-rate-zones 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
Daily Heart Rate Zones (daily-heart-rate-zones) is a Daily data type in the Google Health API. Google's data-types table lists list and reconcile for it under the .health_metrics_and_measurements.readonly and .health_metrics_and_measurements.writeonly scopes. The table marks it with webhook support. Google's Fitbit migration table names no Fitbit Web API predecessor for it.
Daily Heart Rate Zones at a glance
From the Daily Heart Rate Zones row of Google’s data-types table, joined to the discovery document’s DataPoint schema.
- Display name
- Daily Heart Rate Zones
- dataType (in endpoint URLs)
daily-heart-rate-zones- filter parameter
daily_heart_rate_zonesGoogle: “The identifier separated by underscores (for example,active_minutes) used as the value for thedataTypefilter parameter in daily rollup and rollup requests.”- Record type
- Daily — Google: “Represents measurements aggregated or recorded on a daily basis.”
- Storage resolution
- not stated in Google’s table
- Webhook support
- Yes · automatic-subscription token WEBHOOK_DATA_TYPE_DAILY_HEART_RATE_ZONES
- True zeros support
- Not marked in Google’s table
- Channel
- v4
- DataPoint field
DataPoint.dailyHeartRateZones→DailyHeartRateZonesIts description: “Optional. Data for points in thedaily-heart-rate-zonesdaily data type collection.”- Compatible devices
- 0 in Google’s table
Operations and request paths
The operations Google’s table lists for daily-heart-rate-zones, 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 daily-heart-rate-zones. 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/daily-heart-rate-zones/dataPoints |
reconcile | reconcile | GET https://health.googleapis.com/v4/users/{usersId}/dataTypes/daily-heart-rate-zones/dataPoints:reconcile |
Every method, and how many of the data types list it: the methods overview.
Scopes
The scopes Google’s table lists for daily-heart-rate-zones, 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.health_metrics_and_measurements.readonly | read | See your Google Health health metrics and measurement data. |
https://www.googleapis.com/auth/googlehealth.health_metrics_and_measurements.writeonly | write | Add health metric and measurements data to Google Health, and edit or delete the data it adds. |
Fields of Daily Heart Rate Zones
The schema the discovery document gives DataPoint.dailyHeartRateZones, 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.
DailyHeartRateZones — Google: “User's heart rate zone thresholds based on the Karvonen algorithm for a specific day.”
| Field | Type | Google’s description |
|---|---|---|
dateRequired | Date | Required. Date (in user's timezone) of the heart rate zones record. |
heartRateZonesRequired | array<HeartRateZone> | Required. The heart rate zones. |
Date
Google: “Represents a whole or partial calendar date, such as a birthday. The time of day and time zone are either specified elsewhere or are insignificant. The date is relative to the Gregorian Calendar. This can represent one of the following: * A full date, with non-zero year, month, and day values. * A month and day, with a zero year (for example, an anniversary). * A year on its own, with a zero month and a zero day. * A year and month, with a zero day (for example, a credit card expiration date). Related types: * google.type.TimeOfDay * google.type.DateTime * google.protobuf.Timestamp”
| Field | Type | Google’s description |
|---|---|---|
day | integer/int32 | Day of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn't significant. |
month | integer/int32 | Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day. |
year | integer/int32 | Year of the date. Must be from 1 to 9999, or 0 to specify a date without a year. |
HeartRateZone
Google: “The heart rate zone.”
| Field | Type | Google’s description |
|---|---|---|
heartRateZoneTypeRequired | string | Required. The heart rate zone type.
|
maxBeatsPerMinuteRequired | string/int64 | Required. Maximum heart rate for this zone in beats per minute. |
minBeatsPerMinuteRequired | string/int64 | Required. Minimum heart rate for this zone in beats per minute. |
Fitbit Web API predecessor
Google’s Fitbit Web API → Google Health API data-type table has no row for daily-heart-rate-zones, so it names no Fitbit Web API predecessor.
Fitbit Web API scopes Google maps to daily-heart-rate-zones’s scopes: blood_glucose, heartrate, oxygen_saturation, respiratory_rate, temperature, weight.
Google’s full Fitbit Web API mapping tables · the migration playbook
Google’s documentation
Related on this site
- 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 daily-heart-rate-zones data type need?
Google's data-types table (read 2026-10-17) lists https://www.googleapis.com/auth/googlehealth.health_metrics_and_measurements.readonly and https://www.googleapis.com/auth/googlehealth.health_metrics_and_measurements.writeonly for daily-heart-rate-zones. The Scopes page's consent text: .health_metrics_and_measurements.readonly, "See your Google Health health metrics and measurement data."; .health_metrics_and_measurements.writeonly, "Add health metric and measurements data to Google Health, and edit or delete the data it adds."
Can apps write daily heart rate zones data to the Google Health API?
Not according to Google's data-types table, read 2026-10-17: it lists only list and reconcile for daily-heart-rate-zones, and no create, update or batchDelete operation.
How do you aggregate daily-heart-rate-zones data with the Google Health API?
Not with rollUp or dailyRollUp, going by Google's data-types table: it lists only list and reconcile for daily-heart-rate-zones. Read the data points with list (or reconcile, where listed) and compute any summary yourself.
Does the Google Health API send webhooks for daily-heart-rate-zones?
Yes. Google's data-types table marks daily-heart-rate-zones with webhook support, the webhooks guide lists it, and automatic subscriptions name it with the token WEBHOOK_DATA_TYPE_DAILY_HEART_RATE_ZONES.
Other health metrics and measurements 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
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.