Active Energy Burned: the Google Health API active-energy-burned 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 Energy Burned (active-energy-burned) 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 neither webhook nor true-zeros support. Google's Fitbit migration table maps the Fitbit Web API's Activity Calories data to it.
Active Energy Burned at a glance
From the Active Energy Burned row of Google’s data-types table, joined to the discovery document’s DataPoint schema.
- Display name
- Active Energy Burned
- dataType (in endpoint URLs)
active-energy-burned- filter parameter
active_energy_burnedGoogle: “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
- Not marked in Google’s table
- True zeros support
- Not marked in Google’s table
- Channel
- v4
- DataPoint field
DataPoint.activeEnergyBurned→ActiveEnergyBurnedIts description: “Optional. Data for points in theactive-energy-burnedinterval data type collection.”- Compatible devices
- 0 in Google’s table
Operations and request paths
The operations Google’s table lists for active-energy-burned, 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-energy-burned. 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-energy-burned/dataPoints |
reconcile | reconcile | GET https://health.googleapis.com/v4/users/{usersId}/dataTypes/active-energy-burned/dataPoints:reconcile |
rollup | rollUpsame name, different case | POST https://health.googleapis.com/v4/users/{usersId}/dataTypes/active-energy-burned/dataPoints:rollUp |
dailyRollup | dailyRollUpsame name, different case | POST https://health.googleapis.com/v4/users/{usersId}/dataTypes/active-energy-burned/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-energy-burned, 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 Energy Burned
The schema the discovery document gives DataPoint.activeEnergyBurned, 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.
ActiveEnergyBurned — Google: “Energy burned as part of an activity, excluding the basal energy burn.”
| Field | Type | Google’s description |
|---|---|---|
intervalRequired | ObservationTimeInterval | Required. Observed interval |
kcalRequired | number/double | Required. Energy burned during an activity, measured in kilocalories. Must be in the range [0, 1000000]. |
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.activeEnergyBurned
The discovery document: “Returned by default when rolling up data points from the active-energy-burned data type.”
ActiveEnergyBurnedRollupValue — Google: “Represents the result of the rollup of active energy burned.”
| Field | Type | Google’s description |
|---|---|---|
kcalSumOutput only | number/double | Output only. Sum of the active energy burned in kilocalories. |
dailyRollUp returns DailyRollupDataPoint.activeEnergyBurned
The discovery document: “Returned by default when rolling up data points from the active-energy-burned data type.”
The same ActiveEnergyBurnedRollupValue as the rollUp result above.
Fitbit Web API predecessor
Google’s Fitbit Web API → Google Health API data-type table maps Activity Calories to active-energy-burned. Google’s note: “Represents the calories burned during active periods, inclusive of BMR for those periods. In the Google Health API, this can be reconstructed by adding BMR to the active-energy-burned data type (which tracks activity-only burn, excluding basal rate).”
Fitbit Web API scopes Google maps to active-energy-burned’s scopes: activity, cardio_fitness.
Google’s full Fitbit Web API mapping tables · the migration playbook
Google’s documentation
Related on this site
- Calorie Tracking API: How to Get Calorie Data — the metric on every platform this site covers, each type quoted in its platform's own words
- Verification and rate limits
- The Fitbit Web API turn-off
Questions
Which OAuth scopes does the Google Health API active-energy-burned 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-energy-burned. 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 energy burned 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-energy-burned, and no create, update or batchDelete operation.
How do you aggregate active-energy-burned 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-energy-burned/dataPoints:rollUp) returns RollupDataPoint.activeEnergyBurned, a ActiveEnergyBurnedRollupValue with kcalSum; dailyRollUp (POST https://health.googleapis.com/v4/users/{usersId}/dataTypes/active-energy-burned/dataPoints:dailyRollUp) returns DailyRollupDataPoint.activeEnergyBurned, a ActiveEnergyBurnedRollupValue with kcalSum. Each field is described on this page as the discovery document describes it.
What did the Google Health API active-energy-burned data type replace in the Fitbit Web API?
Google's Fitbit Web API migration table maps the Fitbit Web API's "Activity Calories" to active-energy-burned. Google's note on the row: "Represents the calories burned during active periods, inclusive of BMR for those periods. In the Google Health API, this can be reconstructed by adding BMR to the active-energy-burned data type (which tracks activity-only burn, excluding basal rate)." 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.