API Google Fit, включая REST API Google Fit, прекратят поддержку в 2026 году . С 1 мая 2024 г. разработчики не смогут зарегистрироваться для использования этих API .
Оптимизируйте свои подборки
Сохраняйте и классифицируйте контент в соответствии со своими настройками.
Каждый запрос, который ваше приложение отправляет в Fitness API, должен включать токен авторизации. Токен также идентифицирует ваше приложение для Google.
Протокол авторизации
Ваше приложение должно использовать OAuth 2.0 для авторизации запросов. Другие протоколы авторизации не поддерживаются. Если ваше приложение использует Google Sign-In , некоторые аспекты авторизации выполняются за вас.
Все запросы к Fitness API должны быть авторизованы авторизованным пользователем.
Детали процесса авторизации или «потока» для OAuth 2.0 будут зависеть от типа приложения, которое вы пишете. Этот общий процесс применим ко всем типам приложений:
Когда вы создадите свое приложение, зарегистрируйте его с помощью консоли Google API . Затем Google предоставляет информацию, которая понадобится вам позже, например идентификатор клиента и секрет клиента.
Активируйте Fitness API в консоли Google API. (Если API не указан в консоли API, пропустите этот шаг.)
[null,null,["Последнее обновление: 2025-08-29 UTC."],[[["\u003cp\u003eAll requests to the Google Fitness API require an OAuth 2.0 authorization token to identify your application and grant access.\u003c/p\u003e\n"],["\u003cp\u003eApplications need to be registered using the Google API Console, activate the Fitness API, and potentially undergo a verification process depending on the requested data types and their sensitivity.\u003c/p\u003e\n"],["\u003cp\u003eAccess to user data is granted through a user consent screen, providing your application with a short-lived access token upon approval.\u003c/p\u003e\n"],["\u003cp\u003eData type access corresponds to specific scopes, necessitating review of scope requirements for your application's desired functionalities.\u003c/p\u003e\n"]]],[],null,["# Authorizing Requests\n\nEvery request your application sends to the Fitness API must include an\nauthorization token. The token also identifies your application to Google.\n\nAuthorization protocol\n----------------------\n\nYour application must use [OAuth\n2.0](https://developers.google.com/identity/protocols/oauth2) to authorize\nrequests. No other authorization protocols are supported. If your application\nuses [Google Sign-In](https://developers.google.com/identity/#google-sign-in),\nsome aspects of authorization are handled for you.\n\nThe [data types](/fit/datatypes) your app wants to access correspond to\n[scopes](/fit/datatypes#authorization_scopes). Before you can access data types,\nyou'll need to identify if their corresponding scopes are [sensitive or\nrestricted](/fit/datatypes#authorization_scopes) and follow the relevant steps\nwhen [applying for verification](/fit/verification).\nSee step 3 of [authorizing requests](#authorizing_requests_with_oauth_20) below.\n\nAuthorizing requests with OAuth 2.0\n-----------------------------------\n\nAll requests to the Fitness API must be authorized by an authenticated user.\n\nThe details of the authorization process, or \"flow,\" for OAuth 2.0 will\ndepend on the kind of app you're writing. This general process applies to all\napp types:\n\n1. When you create your application, register it using the [Google API\n Console](https://console.developers.google.com/). Google then provides information you'll need later, such as a client ID and a client secret.\n2. Activate the Fitness API in the Google API Console. (If the API isn't listed in the API Console, then skip this step.)\n3. [Apply for verification](/fit/verification) and submit the relevant supporting information for why your app needs certain scopes. The [data types](/fit/datatypes) your app needs to access correspond to [scopes your app needs to request](/fit/datatypes#authorization_scopes).\n4. If your app is verified, Google displays a consent screen to the user, asking them to authorize your app to access their data.\n5. If the user approves, then Google gives your application a short-lived access token.\n6. Your application requests user data, attaching the access token to the request.\n7. If Google determines that your request and the token are valid, it returns the requested data.\n\n| **Note:** Some flows include additional steps, such as using refresh tokens to acquire new access tokens. For detailed information about flows for various types of applications, see Google's [OAuth 2.0\n| documentation](https://developers.google.com/identity/protocols/oauth2).\n\nRead about the OAuth scopes for the Fitness API\n[here](https://developers.google.com/identity/protocols/oauth2/scopes#fitness).\nLook up [which scope is needed for each data type](/fit/datatypes)."]]
