The Google Fit APIs, including the Google Fit REST API, will no longer be available after June 30, 2025. As of May 1, 2024, developers cannot sign up to use these APIs.

For instructions on which API or platform to migrate to, visit the Health Connect migration guide. For a comparison of Health Connect with the Google Fit APIs and the Fitbit Web APIs, visit the Health Connect comparison guide.

Learn more about Health Connect and how to integrate with the API.

Release Notes

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

August 2, 2021

Writing to Health data types is now generally available to developers. Authorization to access Health data types is consistent with all other data types. More details here.

April 27, 2021

There has been a small delay to enforcement of the authorization changes announced on October 10, 2020. The authorization changes will now be enforced from May 4, 2021.

The Google Fit Developer and User Data Policy will also become enforceable on May 4, 2021. App verification , as part of enforcement of the Fit developer policy, will start start in due course.

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 an 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.
When working with the SessionsClient, you now need to specify what type of session your app needs to access, using the appropriate methods from FitnessOptions.

These changes to the API will be available for developers to use from 19 October 2020. Enforcement will start from 27 April 2021.

See here for more details and instructions on these changes.

March 21, 2019

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

November 19, 2018

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

Read requests for datatypes com.google.location.sample and com.google.location.bounding_box will only return data for the same app that has written the data.

September 26, 2018

Google Play services fitness 16.0.0 provides access to two new data types and their respective aggregates:

Artifacts released on maven.google.com

com.google.android.gms:play-services-fitness:16.0.0

November 2017

Google Play services 11.6.0 introduces the following new Google Fit features:

Updated the Fitness API for the new GoogleApi-based clients, which automatically manage connections to services and require less boilerplate code to use:
- Added the BleClient class and the Fitness.getBleClient() methods. BleClient provides the entry point for scanning, claiming, and using Bluetooth Low Energy devices in Google Fit.
- Added the ConfigClient class and the Fitness.getConfigClient() methods. ConfigClient provides the entry point for accessing custom data types and settings in Google Fit.
- Added the GoalsClient class and the Fitness.getGoalsClient() methods. GoalsClient provides the entry point for reading fitness Goals created by users in Google Fit.
- Added the HistoryClient class and the Fitness.getHistoryClient() methods. HistoryClient provides the entry point for inserting, deleting, and reading data in Google Fit.
- Added the RecordingClient class and the Fitness.getRecordingClient() methods. RecordingClient provides the entry point for enabling low-power, always-on background collection of sensor data in Google Fit.
- Added the SensorsClient class and the Fitness.getSensorsClient() methods. SensorsClient provides the entry point for exposing different sources of fitness data in local and connected devices, and delivering live events to listeners.
- Added the SessionsClient class and the getSessionsClient methods. SessionsClient provides the entry point for creating and managing Sessions of user activity in Google Fit.

May 2015

Google Play services 7.5 introduces the following new Google Fit features:

Distance traveled and calories expended computations are available for subscription.
- The Fit platform starts tracking distance and calorie data as soon as an app on the device subscribes to the data. For more information on how to subscribe to data types, see Record Fitness Data.
- The data is not available in real-time with the Sensors API.
The Fit platform can now store exercise routine data, such as bicep curls and squats, with the com.google.activity.exercise data type. For more information on the exercises Fit can store, see WorkoutExercises.

April 2015

Google Play services 7.3 introduces the following new Google Fit features:

The Fit platform can now track nutrition data with the com.google.fitness data type.
- The com.google.calories.consumed data type is now deprecated. Calorie consumption can be recorded with the com.google.fitness.item data type.
- For more information on data types, see Fitness Data Types.
Developers can retrieve daily aggregate step counts for use in areas such as Android Wear watch faces. For more information, see Read daily total data.

March 2015

Google Play services 7.0 introduces the following new Google Fit features:

The Google Fit API is now modularized so that you can choose which features to include in your app. This change significantly reduces the memory requirement for apps that enable Google Fit and affects how you access the APIs. For more information on how to update your code, see Connect to the fitness service.
The Fit platform now calculates distance. To access the data, use the com.google.distance.delta data type. For more information on data types, see Fitness Data Types.
Developers can now read and write granular sleep data. This includes light sleep, deep sleep, REM, and awake activities. These granular activity types have been added to the FitnessActivities enumerated type.
- To insert sleep data, create a session of type FitnessActivities.SLEEP.
- To detect granularity in your session, insert activity segments of types:
- To read sleep data, query the sleep sessions for sleep activity segments as you would do with normal fitness activities.