Stay organized with collections
Save and categorize content based on your preferences.
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.
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.
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:
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).
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[[["\u003cp\u003eThe Google Fit REST API changelog lists releases by date with details on new features, bug fixes, and performance improvements.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Fit API introduced changes to authorization scopes, data access, and security policies, including a new developer policy effective May 4, 2021.\u003c/p\u003e\n"],["\u003cp\u003eHeart rate and sleep data now have dedicated scopes for improved data privacy and control.\u003c/p\u003e\n"],["\u003cp\u003eThe Google Fit REST API no longer processes ETag HTTP headers due to low usage.\u003c/p\u003e\n"],["\u003cp\u003eThe Google Fit app displays sleep sessions written to the REST API, and access to restricted data types for new Google Cloud projects requires app verification.\u003c/p\u003e\n"]]],[],null,["# Release Notes\n\nThis page contains information about Google Fit REST API releases.\nThe changelog lists releases by date and includes any new\nfeatures, bug fixes or significant performance improvements.\n\nAugust 2, 2021\n--------------\n\nWriting to [Health data types](/fit/datatypes/health) is now generally available\nto developers. Authorization to access Health data types is consistent with all\nother data types. More details [here](/fit/datatypes#authorization_scopes).\n\nApril 27, 2021\n--------------\n\nThere has been a small delay to enforcement of the [authorization changes](/fit/improvements#what_are_the_authorization_changes)\nannounced on October 10, 2020. The authorization changes will now be enforced\nfrom May 4, 2021.\n\nThe [Google Fit Developer and User Data Policy](/fit/policy) will also become\nenforceable on May 4, 2021. [App verification](/fit/improvements#strengthening_the_review_system_for_apps_using_google_fit)\n, as part of enforcement of the Fit developer policy, will start start in due\ncourse.\n\nOctober 19, 2020\n----------------\n\nAs part of our ongoing efforts to enhance the security and privacy of Google Fit\nfor developers and users, we've made some changes to the Google Fit policies and\nAPIs:\n\n- There is a new [Google Fit Developer and User Data Policy](/fit/policy). Please review the policy, and if relevant, make appropriate changes to your apps and services.\n- 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.\n- Heart rate data has its own scopes.\n- Sleep data has its own scopes and a new data type.\n\nThese changes to the API will be available for developers to use from 19 October\n2020 and become enforceable on 27 April 2021.\n\nSee [here](/fit/improvements) for more details and instructions on these\nchanges.\n\nDecember 10, 2019\n-----------------\n\nDue to low usage of this feature, the Google Fit REST API will stop issuing\nor processing ETag HTTP headers from February 2020 onwards.\n\nMarch 21, 2019\n--------------\n\nThe Google Fit app now displays sleep sessions written to the REST API.\nLearn more about [writing](/fit/scenarios/write-sleep-data) and [reading](/fit/scenarios/read-sleep-data) sleep data.\n\nMarch 18, 2019\n--------------\n\nThe following changes have been made to the Google Fit REST API:\n\n- 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](/fit/rest/v1/data-types#restricted_data_types).\n\nMarch 15, 2019\n--------------\n\nThe following changes have been made to the Google Fit REST API:\n\n- If none of start time, end time and pageToken are specified in a [User.sessions: list request](https://developers.google.com/fit/rest/v1/reference/users/sessions/list), sessions modified in the last 30 days are now returned. (Previously, only sessions modified in the last 7 days were returned)."]]
