IntermenstrualBleedingRecord: Health Connect intermenstrual bleeding data
Read from Google’s documentation on 2026-10-03 · Google’s reference page last updated 2026-06-24
IntermenstrualBleedingRecord is Health Connect's intermenstrual bleeding record — an Instantaneous record in Google's Cycle Tracking category. Its read permission is android.permission.health.READ_INTERMENSTRUAL_BLEEDING; its write permission is android.permission.health.WRITE_INTERMENSTRUAL_BLEEDING. Google's reference defines no aggregate metrics on it, so it is read with readRecords rather than aggregate. Mandatory fields per Google's table: metadata and time.
What Google says IntermenstrualBleedingRecord is
Captures an instance of user's intermenstrual bleeding, also known as spotting.
Quoted from Google’s IntermenstrualBleedingRecord Jetpack reference, last updated 2026-06-24, read 2026-10-03.
- Class
androidx.health.connect.client.records.IntermenstrualBleedingRecord- Google's category
- Cycle Tracking
- Record type
- Instantaneous
- Unit class
- none named in Google's table
- Mandatory fields
metadatatime- Added in (Jetpack)
1.1.0
Permissions
The exact strings Google’s data-types table declares for IntermenstrualBleedingRecord. Google’s page: “Before requesting any permissions, your app must declare them in the manifest.”
| Access | Permission string | Framework reference |
|---|---|---|
| Read | android.permission.health.READ_INTERMENSTRUAL_BLEEDING | API 34 · U Ext 7 |
| Write | android.permission.health.WRITE_INTERMENSTRUAL_BLEEDING | API 34 · U Ext 7 |
<uses-permission android:name="android.permission.health.READ_INTERMENSTRUAL_BLEEDING" />
<uses-permission android:name="android.permission.health.WRITE_INTERMENSTRUAL_BLEEDING" />import androidx.health.connect.client.permission.HealthPermission
import androidx.health.connect.client.records.IntermenstrualBleedingRecord
val permissions = setOf(
HealthPermission.getReadPermission(IntermenstrualBleedingRecord::class),
HealthPermission.getWritePermission(IntermenstrualBleedingRecord::class),
)The 3 fields of IntermenstrualBleedingRecord
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.
| Field | Type | Allowed range | Google’s description |
|---|---|---|---|
metadatamandatory | Metadata | — | Set of common metadata associated with the written record. |
timemandatory | Instant | — | Time the record happened. |
zoneOffset | ZoneOffset? | — | 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 IntermenstrualBleedingRecord in Kotlin
The shape of Google’s own read example, with IntermenstrualBleedingRecord 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.IntermenstrualBleedingRecord
import androidx.health.connect.client.request.ReadRecordsRequest
import androidx.health.connect.client.time.TimeRangeFilter
import java.time.Instant
suspend fun readIntermenstrualBleeding(
client: HealthConnectClient,
startTime: Instant,
endTime: Instant,
): List<IntermenstrualBleedingRecord> {
val response = client.readRecords(
ReadRecordsRequest(
IntermenstrualBleedingRecord::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 IntermenstrualBleedingRecord 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 IntermenstrualBleedingRecord 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 IntermenstrualBleedingRecord need?
- Google's Health Connect data-types table (read 2026-10-03) declares android.permission.health.READ_INTERMENSTRUAL_BLEEDING for reading IntermenstrualBleedingRecord and android.permission.health.WRITE_INTERMENSTRUAL_BLEEDING for writing it, and says apps must declare permissions in the manifest before requesting them.
- Can you aggregate IntermenstrualBleedingRecord with AggregateRequest?
- Not directly. As read on 2026-10-03, Google's Jetpack reference defines no AggregateMetric constants on IntermenstrualBleedingRecord, so there is no metric to put in an AggregateRequest. Read the records with readRecords and a ReadRecordsRequest, and compute any summary yourself.
- Is IntermenstrualBleedingRecord an interval, instantaneous or series record?
- Google's data-types table lists IntermenstrualBleedingRecord 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 metadata and time.
Other Cycle Tracking records
Sources checked
- Google — IntermenstrualBleedingRecord (Jetpack reference) — last updated 2026-06-24 · read 2026-10-03
- Google — Health Connect data types · read 2026-10-03
- Google — HealthPermissions (framework reference) · read 2026-10-03
- Google — Read raw data (Health Connect guide) · read 2026-10-03
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.