Skip to content
AF
Health Connect reference

BodyTemperatureRecord: Health Connect body temperature data

Read from Google’s documentation on 2026-10-03 · Google’s reference page last updated 2026-06-24

BodyTemperatureRecord is Health Connect's body temperature record — an Instantaneous record in Google's Vitals category. Its read permission is android.permission.health.READ_BODY_TEMPERATURE; its write permission is android.permission.health.WRITE_BODY_TEMPERATURE. Google's reference defines no aggregate metrics on it, so it is read with readRecords rather than aggregate. Mandatory fields per Google's table: temperature, measurementLocation, metadata and time.

What Google says BodyTemperatureRecord is

Captures the body temperature of a user. Each record represents a single instantaneous body temperature measurement.

Quoted from Google’s BodyTemperatureRecord Jetpack reference, last updated 2026-06-24, read 2026-10-03.

Class
androidx.health.connect.client.records.BodyTemperatureRecord
Google's category
Vitals
Record type
Instantaneous
Unit class
androidx.health.connect.client.units.Temperature
Mandatory fields
temperaturemeasurementLocationmetadatatime
Added in (Jetpack)
1.1.0

Permissions

The exact strings Google’s data-types table declares for BodyTemperatureRecord. Google’s page: “Before requesting any permissions, your app must declare them in the manifest.”

AccessPermission stringFramework reference
Readandroid.permission.health.READ_BODY_TEMPERATUREAPI 34 · U Ext 7
Writeandroid.permission.health.WRITE_BODY_TEMPERATUREAPI 34 · U Ext 7
AndroidManifest.xml
<uses-permission android:name="android.permission.health.READ_BODY_TEMPERATURE" />
<uses-permission android:name="android.permission.health.WRITE_BODY_TEMPERATURE" />
Kotlin — the same strings from the Jetpack helper
import androidx.health.connect.client.permission.HealthPermission
import androidx.health.connect.client.records.BodyTemperatureRecord

val permissions = setOf(
    HealthPermission.getReadPermission(BodyTemperatureRecord::class),
    HealthPermission.getWritePermission(BodyTemperatureRecord::class),
)

The 5 fields of BodyTemperatureRecord

Types and descriptions as Google’s reference prints them. The range column quotes Google’s own range annotation or sentence; a dash means Google states none, which is not the same as no validation.

FieldTypeAllowed rangeGoogle’s description
measurementLocationmandatory= BodyTemperatureMeasurementLocation.MEASUREMENT_LOCATION_UNKNOWNInt—Where on the user's body the temperature measurement was taken from. Optional field. Allowed values: BodyTemperatureMeasurementLocation.
metadatamandatoryMetadata—Set of common metadata associated with the written record.
temperaturemandatoryTemperatureValid range: 0-100 Celsius degrees.Temperature in Temperature unit. Required field. Valid range: 0-100 Celsius degrees.
timemandatoryInstant—Time the record happened.
zoneOffsetZoneOffset?—User experienced zone offset at time, or null if unknown. Providing these will help history aggregations results stay consistent should user travel. Queries with user experienced time filters will assume system current zone offset if the information is absent.

Read BodyTemperatureRecord in Kotlin

The shape of Google’s own read example, with BodyTemperatureRecord and its names filled in. Get the client with HealthConnectClient.getOrCreate(context) after checking getSdkStatus.

readRecords
import androidx.health.connect.client.HealthConnectClient
import androidx.health.connect.client.records.BodyTemperatureRecord
import androidx.health.connect.client.request.ReadRecordsRequest
import androidx.health.connect.client.time.TimeRangeFilter
import java.time.Instant

suspend fun readBodyTemperature(
    client: HealthConnectClient,
    startTime: Instant,
    endTime: Instant,
): List<BodyTemperatureRecord> {
    val response = client.readRecords(
        ReadRecordsRequest(
            BodyTemperatureRecord::class,
            timeRangeFilter = TimeRangeFilter.between(startTime, endTime),
        )
    )
    // One page of up to pageSize records (default 1000); follow
    // response.pageToken for the rest.
    return response.records
}

Setting up the client, the permission flow and Play Console declaration: integrating Health Connect step by step.

HealthKit counterpart

No verified HealthKit counterpart. The cross-platform matrix only pairs metrics checked against both Apple’s and Google’s documentation, and BodyTemperatureRecord is not among them yet. A similarly named Apple type may exist on the HealthKit reference, but a name match is not a verified mapping.

The metric on other platforms

This guide lists BodyTemperatureRecord beside the types on the other platforms this site covers whose own descriptions name the same metric, each quoted, with how each one is read.

Questions

What permission does BodyTemperatureRecord need?
Google's Health Connect data-types table (read 2026-10-03) declares android.permission.health.READ_BODY_TEMPERATURE for reading BodyTemperatureRecord and android.permission.health.WRITE_BODY_TEMPERATURE for writing it, and says apps must declare permissions in the manifest before requesting them.
Can you aggregate BodyTemperatureRecord with AggregateRequest?
Not directly. As read on 2026-10-03, Google's Jetpack reference defines no AggregateMetric constants on BodyTemperatureRecord, so there is no metric to put in an AggregateRequest. Read the records with readRecords and a ReadRecordsRequest, and compute any summary yourself.
What values does BodyTemperatureRecord.temperature accept?
Google's reference types temperature as Temperature. Its description reads: "Temperature in Temperature unit. Required field. Valid range: 0-100 Celsius degrees."
Is BodyTemperatureRecord an interval, instantaneous or series record?
Google's data-types table lists BodyTemperatureRecord as Instantaneous, and defines that column as indicating "whether the data is recorded at an instant in time or over an interval". Its mandatory fields are temperature, measurementLocation, metadata and time.

Other Vitals records

All Vitals records →

Sources checked

Google’s descriptions are quoted for identification; the page layout, the capsule and the cross-platform pairing are AIFitnessAPI’s. Generated from Google’s pages by a script, not typed by hand — the same data is behind every page in the Health Connect reference.

← All Health Connect records · Every permission string