We're making some changes to the Google Fit APIs. Learn about how these changes might affect your app. Read our new policy.

Release Notes

This page contains information about Google Fit REST API releases. The changelog lists releases by date and includes any new features, bug fixes or significant performance improvements.

October 19, 2020

As part of our ongoing efforts to enhance the security and privacy of Google Fit for developers and users, we've made some changes to the Google Fit policies and APIs:

  • There is a new Google Fit Developer and User Data Policy. Please review the policy, and if relevant, make appropriate changes to your apps and services.
  • Write-access will now only let our app read data it has written. To continue reading data written by other apps from the Google Fit platform, update your code to request read-access scopes for the relevant data types.
  • Heart rate data has its own scopes.
  • Sleep data has its own scopes and a new data type.

These changes to the API will be available for developers to use from 19 October 2020 and become enforceable on 27 April 2021.

See here for more details and instructions on these changes.

December 10, 2019

Due to low usage of this feature, the Google Fit REST API will stop issuing or processing ETag HTTP headers from February 2020 onwards.

March 21, 2019

The Google Fit app now displays sleep sessions written to the REST API. Learn more about writing and reading sleep data.

March 18, 2019

The following changes have been made to the Google Fit REST API:

  • For all new Google Cloud projects created from March 2019, read and write access to restricted data types now require your app to be verified by Google. Learn more.

March 15, 2019

The following changes have been made to the Google Fit REST API:

  • If none of start time, end time and pageToken are specified in a User.sessions: list request, sessions modified in the last 30 days are now returned. (Previously, only sessions modified in the last 7 days were returned).