API Google Fit, termasuk Google Fit REST API, tidak akan digunakan lagi pada tahun 2026. Mulai 1 Mei 2024, developer tidak dapat mendaftar untuk menggunakan API ini.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Setiap permintaan yang dikirimkan aplikasi Anda ke Fitness API harus menyertakan
token otorisasi. Token ini juga mengidentifikasi aplikasi Anda ke Google.
Protokol otorisasi
Aplikasi Anda harus menggunakan OAuth
2.0 untuk mengizinkan
permintaan. Tidak ada protokol otorisasi lain yang didukung. Jika aplikasi Anda
menggunakan Login dengan Google,
beberapa aspek otorisasi akan ditangani untuk Anda.
Semua permintaan ke Fitness API harus diizinkan oleh pengguna yang diautentikasi.
Detail proses otorisasi, atau "flow", untuk OAuth 2.0 akan
bergantung pada jenis aplikasi yang Anda tulis. Proses umum ini berlaku untuk semua
jenis aplikasi:
Saat membuat aplikasi, daftarkan aplikasi menggunakan Konsol
Google API. Selanjutnya, Google memberikan informasi yang akan Anda perlukan nanti, seperti client ID dan rahasia klien.
Aktifkan Kebugaran API di Konsol API Google. (Jika API tidak tercantum di Konsol API, lewati langkah ini.)
Jika aplikasi Anda sudah diverifikasi, Google akan menampilkan layar izin kepada pengguna, yang meminta mereka untuk mengizinkan aplikasi Anda mengakses data mereka.
Jika pengguna menyetujui, Google akan memberikan token akses berumur singkat ke aplikasi Anda.
Aplikasi Anda meminta data pengguna, dengan menambahkan token akses ke permintaan.
Jika Google menentukan bahwa permintaan dan token Anda valid, data yang diminta akan ditampilkan.
[null,null,["Terakhir diperbarui pada 2025-08-31 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)."]]
