Core Body Temperature: the Google Health API core-body-temperature 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
Core Body Temperature (core-body-temperature) is a Sample data type in the Google Health API. Google's data-types table lists list, get, reconcile, rollup and dailyRollup for it under the .health_metrics_and_measurements.readonly and .health_metrics_and_measurements.writeonly scopes. The table marks it with neither webhook nor true-zeros support. Google's Fitbit migration table maps the Fitbit Web API's Temperature (Core) data to it.
Core Body Temperature at a glance
From the Core Body Temperature row of Google’s data-types table, joined to the discovery document’s DataPoint schema.
- Display name
- Core Body Temperature
- dataType (in endpoint URLs)
core-body-temperature- filter parameter
core_body_temperatureGoogle: “The identifier separated by underscores (for example,active_minutes) used as the value for thedataTypefilter parameter in daily rollup and rollup requests.”- Record type
- Sample — Google: “Represents instantaneous measurements.”
- Storage resolution
- not stated in Google’s table
- Webhook support
- Not marked in Google’s table
- True zeros support
- Not marked in Google’s table
- Channel
- v4
- DataPoint field
DataPoint.coreBodyTemperature→CoreBodyTemperatureIts description: “Optional. Data for points in thecore-body-temperaturesample data type collection.”- Compatible devices
- 0 in Google’s table
Operations and request paths
The operations Google’s table lists for core-body-temperature, 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 core-body-temperature. 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/core-body-temperature/dataPoints |
get | get | GET https://health.googleapis.com/v4/users/{usersId}/dataTypes/core-body-temperature/dataPoints/{dataPointsId} |
reconcile | reconcile | GET https://health.googleapis.com/v4/users/{usersId}/dataTypes/core-body-temperature/dataPoints:reconcile |
rollup | rollUpsame name, different case | POST https://health.googleapis.com/v4/users/{usersId}/dataTypes/core-body-temperature/dataPoints:rollUp |
dailyRollup | dailyRollUpsame name, different case | POST https://health.googleapis.com/v4/users/{usersId}/dataTypes/core-body-temperature/dataPoints:dailyRollUp |
Every method, and how many of the data types list it: the methods overview.
Scopes
The scopes Google’s table lists for core-body-temperature, 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 Core Body Temperature
The schema the discovery document gives DataPoint.coreBodyTemperature, 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.
CoreBodyTemperature — Google: “Core body temperature measurement, distinct from peripheral body temperature, reflects the temperature of the body's internal organs.”
| Field | Type | Google’s description |
|---|---|---|
sampleTimeRequired | ObservationSampleTime | Required. The time at which core body temperature was measured. |
temperatureCelsiusRequired | number/double | Required. The core body temperature in Celsius. Must be in the range [0, 100]. |
idOptional | string | Optional. The unique identifier of the core body temperature measurement. |
measurementLocationOptional | string | Optional. The location of the core body temperature measurement.
|
ObservationSampleTime
Google: “Represents a sample time of an observed data point.”
| Field | Type | Google’s description |
|---|---|---|
physicalTimeRequired | string/google-datetime | Required. The time of the observation. |
utcOffsetRequired | string/google-duration | Required. The offset of the user's local time during the observation relative to the Coordinated Universal Time (UTC). |
civilTimeOutput only | CivilDateTime | Output only. The civil time in the timezone the subject is in at the time of the observation. |
Rollup fields
rollUp returns RollupDataPoint.coreBodyTemperature
The discovery document: “Returned by default when rolling up data points from the core-body-temperature data type, or when requested explicitly using the core-body-temperature rollup type identifier.”
CoreBodyTemperatureRollupValue — Google: “Represents the result of the rollup of the core body temperature data type.”
| Field | Type | Google’s description |
|---|---|---|
temperatureCelsiusAvg | number/double | Average core body temperature in Celsius. |
temperatureCelsiusMax | number/double | Maximum core body temperature in Celsius. |
temperatureCelsiusMin | number/double | Minimum core body temperature in Celsius. |
dailyRollUp returns DailyRollupDataPoint.coreBodyTemperature
The discovery document: “Returned by default when rolling up data points from the core-body-temperature data type, or when requested explicitly using the core-body-temperature rollup type identifier.”
The same CoreBodyTemperatureRollupValue as the rollUp result above.
Fitbit Web API predecessor
Google’s Fitbit Web API → Google Health API data-type table maps Temperature (Core) to core-body-temperature.
Fitbit Web API scopes Google maps to core-body-temperature’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
- Body Temperature API: Core, Skin and Wrist Temperature 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 core-body-temperature 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 core-body-temperature. 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 core body temperature data to the Google Health API?
Not according to Google's data-types table, read 2026-10-17: it lists only list, get, reconcile, rollup and dailyRollup for core-body-temperature, and no create, update or batchDelete operation.
How do you aggregate core-body-temperature 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/core-body-temperature/dataPoints:rollUp) returns RollupDataPoint.coreBodyTemperature, a CoreBodyTemperatureRollupValue with temperatureCelsiusAvg, temperatureCelsiusMax and temperatureCelsiusMin; dailyRollUp (POST https://health.googleapis.com/v4/users/{usersId}/dataTypes/core-body-temperature/dataPoints:dailyRollUp) returns DailyRollupDataPoint.coreBodyTemperature, a CoreBodyTemperatureRollupValue with temperatureCelsiusAvg, temperatureCelsiusMax and temperatureCelsiusMin. Each field is described on this page as the discovery document describes it.
What did the Google Health API core-body-temperature data type replace in the Fitbit Web API?
Google's Fitbit Web API migration table maps the Fitbit Web API's "Temperature (Core)" to core-body-temperature. The Fitbit Web API scopes Google maps to its scopes: blood_glucose, heartrate, oxygen_saturation, respiratory_rate, temperature and weight.
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
- 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.