Total Calories: the Google Health API total-calories data type

Total Calories at a glance

From the Total Calories row of Google’s data-types table, joined to the discovery document’s DataPoint schema.

Display name

Total Calories

dataType (in endpoint URLs)

total-calories

filter parameter

total_caloriesGoogle: “The identifier separated by underscores (for example, active_minutes) used as the value for the dataType filter 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

Yes

Channel

v4

DataPoint field

none in the discovery documents — see the flags below

Compatible devices

28 in Google’s table

Operations and request paths

The operations Google’s table lists for total-calories, 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 total-calories. Google on {user}: “The {user} can be either the alias me or the authenticated user's numeric Health User ID (retrieved via GetIdentity).”

Every method, and how many of the data types list it: the methods overview.

Scopes

The scopes Google’s table lists for total-calories, as full URLs, with the consent text Google’s Scopes page gives each. Every Google Health API scope.

Rollup fields

Fitbit Web API predecessor

Fitbit Web API scopes Google maps to total-calories’s scopes: activity, cardio_fitness.

Google’s full Fitbit Web API mapping tables · the migration playbook

Where Google’s guides name total-calories

• “Filter requirements: Some read-only derived data types, such as total-calories, require a filter specifying an interval start time (using physical or civil time).”Google's data-types page, “Query constraints”
• “A maximum query range of 14 days for calories-in-heart-rate-zone, heart-rate, active-minutes, and total-calories.”Google's data-types page, “Query constraints”
• “A maximum range of 14 days for calories-in-heart-rate-zone, heart-rate, active-minutes, and total-calories.”Google's endpoints guide, “Query historical data”

Where Google’s pages disagree

Published as found, with the texts that disagree; nothing here is corrected by us.

• No v4 DataPoint field

  Neither discovery document has a DataPoint property for total-calories; it exists only as a rollup (totalCalories), matching the table's operations (rollup, dailyRollup).

  • Google's data-types page: “Total Calories”
  • Google's data-types page: “rollup, dailyRollup”
  • the v4 discovery document: “Returned by default when rolling up data points from the total-calories data type, or when requested explicitly using the total-calories rollup type identifier.”

• Release note and webhook pages differ

  Google's release notes for April 14, 2026 list totalCalories under webhook notification support; the data-types table and the webhooks page do not list total-calories as webhook-supported.

  • Google's release notes: “Notification support for the data types activeZoneMinutes, altitude, bodyFat, caloriesInHeartRateZone, dailyHeartRateVariability, dailyHeartRateZones, dailyOxygenSaturation, dailyRestingHeartRate, dailySleepTemperatureDerivations, distance, exercise, floors, heartRate, sleep, steps, totalCalories, and weight.”

Compatible devices

The 28 devices Google’s table lists as able to record and sync total-calories.

• Fitbit Air
• Fitbit Alta
• Fitbit Alta HR
• Fitbit Blaze
• Fitbit Charge 2
• Fitbit Charge 3
• Fitbit Charge 4
• Fitbit Charge 5
• Fitbit Charge 6
• Fitbit Flex 2
• Fitbit Inspire
• Fitbit Inspire 2
• Fitbit Inspire 3
• Fitbit Inspire HR
• Fitbit Ionic
• Fitbit Luxe
• Fitbit MobileTrack
• 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