ActiveCaloriesBurnedRecord: Health Connect active calories burned data

What Google says ActiveCaloriesBurnedRecord is

Captures the estimated active energy burned by the user (in kilocalories), excluding basal metabolic rate (BMR). Each record represents the total kilocalories burned over a time interval, so both the start and end times should be set.

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

Class

androidx.health.connect.client.records.ActiveCaloriesBurnedRecord

Google's category

Activity

Record type

Interval

Unit class

androidx.health.connect.client.units.Energy

Mandatory fields

endTimeenergymetadatastartTime

Added in (Jetpack)

1.1.0

Permissions

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

<uses-permission android:name="android.permission.health.READ_ACTIVE_CALORIES_BURNED" />
<uses-permission android:name="android.permission.health.WRITE_ACTIVE_CALORIES_BURNED" />

import androidx.health.connect.client.permission.HealthPermission
import androidx.health.connect.client.records.ActiveCaloriesBurnedRecord

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

The 6 fields of ActiveCaloriesBurnedRecord

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.

Aggregate metrics

The AggregateMetric constants Google defines on ActiveCaloriesBurnedRecord. The value type is the T in Google’s AggregateMetric<T> signature. Every aggregate metric across all records.

Google’s read-data guide: “For cumulative types like StepsRecord, use aggregate() instead of readRecords() to avoid double counting from multiple sources and improve accuracy.” and “The aggregation API also contains logic to handle duplicate records, and lessens the chances of rate limiting.”

Read ActiveCaloriesBurnedRecord in Kotlin

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

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

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

import androidx.health.connect.client.HealthConnectClient
import androidx.health.connect.client.records.ActiveCaloriesBurnedRecord
import androidx.health.connect.client.request.AggregateRequest
import androidx.health.connect.client.time.TimeRangeFilter
import java.time.Instant
import androidx.health.connect.client.units.Energy

suspend fun aggregateActiveCaloriesBurned(
    client: HealthConnectClient,
    startTime: Instant,
    endTime: Instant,
): Energy? {
    val response = client.aggregate(
        AggregateRequest(
            metrics = setOf(ActiveCaloriesBurnedRecord.ACTIVE_CALORIES_TOTAL),
            timeRangeFilter = TimeRangeFilter.between(startTime, endTime),
        )
    )
    // get() is declared as returning a nullable value.
    return response[ActiveCaloriesBurnedRecord.ACTIVE_CALORIES_TOTAL]
}

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

HealthKit counterpart

The metric on other platforms

This guide lists ActiveCaloriesBurnedRecord 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.

• Calorie Tracking API: How to Get Calorie Data

Questions

What permission does ActiveCaloriesBurnedRecord need?

Google's Health Connect data-types table (read 2026-10-03) declares android.permission.health.READ_ACTIVE_CALORIES_BURNED for reading ActiveCaloriesBurnedRecord and android.permission.health.WRITE_ACTIVE_CALORIES_BURNED for writing it, and says apps must declare permissions in the manifest before requesting them.

Which aggregate metrics does ActiveCaloriesBurnedRecord support?

Google's Jetpack reference defines 1 on ActiveCaloriesBurnedRecord: ACTIVE_CALORIES_TOTAL (AggregateMetric<Energy>). Pass it in the metrics set of an AggregateRequest and read it back from the AggregationResult.

What values does ActiveCaloriesBurnedRecord.energy accept?

Google's reference types energy as Energy. Its description reads: "Energy in Energy unit. Required field. Valid range: 0-1000000 kcal."

Is ActiveCaloriesBurnedRecord an interval, instantaneous or series record?

Google's data-types table lists ActiveCaloriesBurnedRecord as Interval, and defines that column as indicating "whether the data is recorded at an instant in time or over an interval". Its mandatory fields are endTime, energy, metadata and startTime.