Restricted health data types

Google Fit defines the following data types for instantaneous readings and data types for aggregate data:

Data Type Name Description Permission Fields (Format—Unit) Blood glucose concentration, temporal relationships to meals and sleep, and the source of the specimen which was measured. Blood Glucose blood glucose level (float—mmol/L)
temporal relation to meal (int—enum)
specimen source (int—enum)
temporal relation to meal (int—enum) The instantaneous blood pressure of the user. Blood Pressure systolic (float—mmHg)
diastolic (float—mmHg)
body position (int—enum) The instantaneous body temperature of the user. Body Temperature body temperature (float—celsius)
measurement location (int—enum) A report of the user's menstrual flow. Reproductive Health menstrual flow (int—enum) The instantaneous blood oxygen saturation of the user. Oxygen Saturation administration mode (int—enum)
system (int—enum)
measurement method (int—enum) Occurrence of vaginal spotting. Reproductive Health occurrences (int—count)

Read and write access

To read and write to restricted data types, you first need to verify your app through Google's OAuth Application Verification process. Learn more

If your app isn't verified, when it requests access to a sensitive OAuth scope certain request quotas will be applied and users may see warnings. The quotas are there to allow you to conduct testing. Learn more

Once your app is verified, it can read restricted data types. To write to restricted data types, there's a second application process.

Because health data is potentially sensitive, Google Fit restricts write access for the data types in HealthDataTypes to only certain developers. Apps need user permission to read and write data of a restricted type. Any application can read fitness data of a restricted data type, but only Google-approved applications can write data of this type.