Skip to content
AF
Google Health API reference

Run VO2 Max: the Google Health API run-vo2-max 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

Run VO2 Max (run-vo2-max) is a Sample data type in the Google Health API. Google's data-types table lists list, reconcile, rollup and dailyRollup for it under the .activity_and_fitness.readonly and .activity_and_fitness.writeonly scopes. The table marks it with webhook support. Google's Fitbit migration table maps the Fitbit Web API's VO2 Max value when the user runs data to it.

Run VO2 Max at a glance

From the Run VO2 Max row of Google’s data-types table, joined to the discovery document’s DataPoint schema.

Display name
Run VO2 Max
dataType (in endpoint URLs)
run-vo2-max
filter parameter
run_vo2_maxGoogle: “The identifier separated by underscores (for example, active_minutes) used as the value for the dataType filter parameter in daily rollup and rollup requests.”
Record type
Sample — Google: “Represents instantaneous measurements.”
Storage resolution
not stated in Google’s table
Webhook support
Yes · automatic-subscription token WEBHOOK_DATA_TYPE_RUN_VO2_MAX
True zeros support
Not marked in Google’s table
Channel
v4
DataPoint field
DataPoint.runVo2Max → RunVO2MaxIts description: “Optional. Data for points in the run-vo2-max sample data type collection.”
Compatible devices
23 in Google’s table

Operations and request paths

The operations Google’s table lists for run-vo2-max, 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 run-vo2-max. Google on {user}: “The {user} can be either the alias me or the authenticated user's numeric Health User ID (retrieved via GetIdentity).”

Table listsMethodDocumented path template
listlistGET https://health.googleapis.com/v4/users/{usersId}/dataTypes/run-vo2-max/dataPoints
reconcilereconcileGET https://health.googleapis.com/v4/users/{usersId}/dataTypes/run-vo2-max/dataPoints:reconcile
rolluprollUpsame name, different casePOST https://health.googleapis.com/v4/users/{usersId}/dataTypes/run-vo2-max/dataPoints:rollUp
dailyRollupdailyRollUpsame name, different casePOST https://health.googleapis.com/v4/users/{usersId}/dataTypes/run-vo2-max/dataPoints:dailyRollUp

Every method, and how many of the data types list it: the methods overview.

Scopes

The scopes Google’s table lists for run-vo2-max, as full URLs, with the consent text Google’s Scopes page gives each. Every Google Health API scope.

ScopeAccessGoogle’s permission text
https://www.googleapis.com/auth/googlehealth.activity_and_fitness.readonlyreadSee your Google Health activity and fitness data.
https://www.googleapis.com/auth/googlehealth.activity_and_fitness.writeonlywriteAdd activity and fitness data to Google Health, and edit or delete the data it adds.

Fields of Run VO2 Max

The schema the discovery document gives DataPoint.runVo2Max, 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.

RunVO2Max — Google: “VO2 max value calculated based on the user's running activity. Value stored in ml/kg/min.”

FieldTypeGoogle’s description
runVo2MaxRequirednumber/doubleRequired. Run VO2 max value in ml/kg/min. Must be in the range [0, 100].
sampleTimeRequiredObservationSampleTimeRequired. The time at which the metric was measured.

ObservationSampleTime

Google: “Represents a sample time of an observed data point.”

FieldTypeGoogle’s description
physicalTimeRequiredstring/google-datetimeRequired. The time of the observation.
utcOffsetRequiredstring/google-durationRequired. The offset of the user's local time during the observation relative to the Coordinated Universal Time (UTC).
civilTimeOutput onlyCivilDateTimeOutput only. The civil time in the timezone the subject is in at the time of the observation.

Rollup fields

rollUp returns RollupDataPoint.runVo2Max

The discovery document: “Returned by default when rolling up data points from the run-vo2-max data type, or when requested explicitly using the run-vo2-max rollup type identifier.”

RunVO2MaxRollupValue — Google: “Represents the result of the rollup of the user's daily heart rate variability personal range.”

FieldTypeGoogle’s description
rateAvgnumber/doubleAverage value of run VO2 max in the interval.
rateMaxnumber/doubleMaximum value of run VO2 max in the interval.
rateMinnumber/doubleMinimum value of run VO2 max in the interval..

dailyRollUp returns DailyRollupDataPoint.runVo2Max

The discovery document: “Returned by default when rolling up data points from the run-vo2-max data type, or when requested explicitly using the run-vo2-max rollup type identifier.”

The same RunVO2MaxRollupValue as the rollUp result above.

Fitbit Web API predecessor

Google’s Fitbit Web API → Google Health API data-type table maps VO2 Max value when the user runs to run-vo2-max.

Fitbit Web API scopes Google maps to run-vo2-max’s scopes: activity, cardio_fitness.

Google’s full Fitbit Web API mapping tables · the migration playbook

Compatible devices

The 23 devices Google’s table lists as able to record and sync run-vo2-max.

  • Fitbit Air
  • Fitbit Alta HR
  • Fitbit Blaze
  • Fitbit Charge 2
  • Fitbit Charge 3
  • Fitbit Charge 4
  • Fitbit Charge 5
  • Fitbit Charge 6
  • Fitbit Inspire 2
  • Fitbit Inspire 3
  • Fitbit Ionic
  • Fitbit Luxe
  • Pixel Watch
  • Pixel Watch 2
  • Pixel Watch 3
  • Pixel Watch 4
  • Fitbit Sense
  • Fitbit Sense 2
  • Fitbit Versa
  • Fitbit Versa 2
  • Fitbit Versa 3
  • Fitbit Versa 4
  • Fitbit Versa Lite

Google’s documentation

Related on this site

Questions

Which OAuth scopes does the Google Health API run-vo2-max data type need?

Google's data-types table (read 2026-10-17) lists https://www.googleapis.com/auth/googlehealth.activity_and_fitness.readonly and https://www.googleapis.com/auth/googlehealth.activity_and_fitness.writeonly for run-vo2-max. The Scopes page's consent text: .activity_and_fitness.readonly, "See your Google Health activity and fitness data."; .activity_and_fitness.writeonly, "Add activity and fitness data to Google Health, and edit or delete the data it adds."

Can apps write run VO2 max data to the Google Health API?

Not according to Google's data-types table, read 2026-10-17: it lists only list, reconcile, rollup and dailyRollup for run-vo2-max, and no create, update or batchDelete operation.

How do you aggregate run-vo2-max 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/run-vo2-max/dataPoints:rollUp) returns RollupDataPoint.runVo2Max, a RunVO2MaxRollupValue with rateAvg, rateMax and rateMin; dailyRollUp (POST https://health.googleapis.com/v4/users/{usersId}/dataTypes/run-vo2-max/dataPoints:dailyRollUp) returns DailyRollupDataPoint.runVo2Max, a RunVO2MaxRollupValue with rateAvg, rateMax and rateMin. Each field is described on this page as the discovery document describes it.

What did the Google Health API run-vo2-max data type replace in the Fitbit Web API?

Google's Fitbit Web API migration table maps the Fitbit Web API's "VO2 Max value when the user runs" to run-vo2-max. The Fitbit Web API scopes Google maps to its scopes: activity and cardio_fitness.

Other activity and fitness data types

All activity and fitness data types →

Sources checked

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.

← All Google Health API data types