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.
Panduan ini menjelaskan cara memulai pengembangan dengan Google Fit di Android.
Penyiapan
Sebelum Anda mulai membangun aplikasi, selesaikan langkah-langkah di bagian berikut.
Membuat Akun Google
Untuk menggunakan Google Fit API, Anda memerlukan Akun Google. Anda dapat membuat akun baru atau
menggunakan akun yang ada. Sebaiknya buat akun terpisah untuk menguji aplikasi Anda dari perspektif pengguna.
Dapatkan layanan Google Play
Dapatkan library klien terbaru untuk layanan Google Play di host pengembangan Anda:
Hal ini memastikan bahwa Gradle otomatis mendownload SDK kebugaran saat membangun aplikasi Anda.
Membangun dan menguji aplikasi Anda
Setelah menyelesaikan langkah-langkah penyiapan, Anda dapat mulai mem-build aplikasi. Untuk memulai, pelajari jenis data yang dapat disimpan dan dibaca oleh aplikasi Anda. Pelajari lebih lanjut cara menggunakan data di Google Fit.
Jenis data yang izin aksesnya dimiliki aplikasi Anda sesuai dengan
cakupan otorisasi. Untuk meminta
izin ini, Anda perlu menambahkan
jenis data yang perlu diakses aplikasi Anda dalam instance FitnessOptions. Saat aplikasi Anda meminta untuk menggunakan jenis data Google Fit, Android SDK akan otomatis memeriksa cakupan yang terkait dengan jenis data tersebut dan meminta otorisasi pengguna untuk cakupan tersebut.
Membuat klien API
Buat klien API dan tambahkan jenis data yang perlu diakses aplikasi Anda untuk
menulis atau membaca data. Endpoint berikut tersedia:
SensorsClient: Akses berbagai sumber data kesehatan dan kebugaran dari sensor hardware di perangkat lokal dan di perangkat pendamping.
RecordingClient: Untuk pengumpulan data sensor di latar belakang yang selalu aktif dan berdaya rendah.
HistoryClient: Menyisipkan, menghapus, dan membaca data historis di
Google Fit.
Berikut adalah alur otorisasi yang dialami pengguna saat mereka diminta izin:
Gambar 1.Alur otorisasi untuk pengguna.
Izin Android: Pengguna melihat izin Android yang telah diminta aplikasi Anda sebelum mendownloadnya. Setelah didownload, aplikasi Anda akan meminta izin runtime yang diperlukan, dan pengguna akan memberikan atau menolak izin ini.
Periksa dan hubungkan: Aplikasi Anda memeriksa apakah izin telah diberikan sebelum meminta akses ke jenis data lain.
Permintaan cakupan OAuth: Google akan meminta pengguna untuk memberikan cakupan OAuth yang diperlukan aplikasi Anda untuk mengakses jenis data yang diinginkannya.
Akses diterapkan: Setelah pengguna memberikan izin, aplikasi Anda dapat
mengakses jenis data yang termasuk dalam cakupan yang telah diberi izin
oleh pengguna.
[null,null,["Terakhir diperbarui pada 2025-09-03 UTC."],[[["\u003cp\u003eThis guide provides instructions for Android developers to integrate Google Fit into their applications.\u003c/p\u003e\n"],["\u003cp\u003eIt outlines the necessary setup steps, including obtaining a Google account, setting up Google Play services, and acquiring OAuth 2.0 client ID.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers are guided through the process of creating an API client and implementing data access functionalities.\u003c/p\u003e\n"],["\u003cp\u003eBefore publishing, developers need to apply for verification to ensure data security and compliance.\u003c/p\u003e\n"],["\u003cp\u003eThe guide also explains the authorization flow users will experience when granting data access permissions to the app.\u003c/p\u003e\n"]]],[],null,["# Get started on Android\n\nThis guide explains how to start development with Google Fit on Android.\n| **Note:** Google Fit is part of Google Play services. [Learn about the\n| benefits your app gets from using Google Play\n| Services](/android/guides/overview).\n\nSetup\n-----\n\nBefore you start to build your app, complete the steps in the following\nsections.\n\n### Get a Google Account\n\nTo use the Google Fit APIs, you need a Google Account. You can [create a new account](https://www.google.com/accounts/NewAccount) or\nuse an existing account. You might want to create a separate account to test your app from a user's perspective.\n\n### Get Google Play services\n\nGet the latest client library for Google Play services on your development\nhost:\n\n1. Open the [Android SDK Manager](https://developer.android.com/studio/intro/update#sdk-manager).\n2. Under **SDK Tools** , find **Google Play services**.\n3. If the status for these packages isn't *Installed* , select them both and click **Install Packages**.\n\n### Get an OAuth 2.0 client ID\n\nTo enable the Fitness API, [get an OAuth 2.0 client ID](/fit/android/get-api-key).\n\n### Create and configure your project\n\nWe recommend using the [Android Studio development environment](https://developer.android.com/studio) to build an app with the Fitness API. For\ndetails on how to make a new project and configure it in Android Studio, see\n[Create a project](https://developer.android.com/studio/projects/create-project).\n\n### Add the Google Play services client library\n\nIn Android Studio, open the `build.gradle` file for your module and add the Google Play services client library as a dependency: \n\n### Kotlin DSL\n\n```kotlin\nplugin {\n id(\"com.android.application\")\n}\n\n...\n\ndependencies {\n implementation(\"com.google.android.gms:play-services-fitness:21.3.0\")\n implementation(\"com.google.android.gms:play-services-auth:21.4.0\")\n}\n```\n\n### Groovy DSL\n\n```carbon\napply plugin: 'com.android.application'\n\n...\n\ndependencies {\n implementation 'com.google.android.gms:play-services-fitness:21.3.0'\n implementation 'com.google.android.gms:play-services-auth:21.4.0'\n}\n```\n\nThis makes sure that Gradle automatically downloads the fitness SDK when it\nbuilds your app.\n\nBuild and test your app\n-----------------------\n\nAfter you finish the setup steps, you can start to build your app. To get\nstarted, learn about the [types of data](/fit/datatypes) your app can [store and\nread](/fit/datatypes#using_data_types). Learn more about [working with\ndata](/fit/android/history) in Google Fit.\n\n### Get the necessary Android permissions\n\nTo read and write [some types of data](/fit/android/authorization#data_types_that_ne\ned_android_permissions), your app needs to [request Android permissions](/fit/android/authorization#android_permission\ns).\n\n### Get OAuth permissions\n\nThe data types that your app has permission to access correspond to\n[authorization scopes](/fit/datatypes#authorization_scopes). To ask\nfor these permissions, you need to [add\nwhich data types your app needs access to in a `FitnessOptions`\ninstance](/fit/android/api-client-example). When your app asks to use any of the Google Fit data\ntypes, the Android SDK automatically checks which scopes they belong to and asks\nthe user for authorization to those scopes.\n\n### Create an API client\n\nCreate an API client and add the data types that your app needs to access to\nwrite or read data. The following endpoints are available:\n\n- [`SensorsClient`](/android/reference/com/google/android/gms/fitness/SensorsClient): Access different sources of health and wellness data from hardware sensors in the local device and in companion devices.\n- [`RecordingClient`](/android/reference/com/google/android/gms/fitness/RecordingClient): For low-power, always-on background collection of sensor data.\n- [`HistoryClient`](/android/reference/com/google/android/gms/fitness/HistoryClient): Insert, delete, and read historical data in Google Fit.\n- [`SessionsClient`](/android/reference/com/google/android/gms/fitness/SessionsClient): Create and manage [Sessions](/fit/sessions) of user activity.\n- [`GoalsClient`](/android/reference/com/google/android/gms/fitness/GoalsClient): Read Heart Point and Steps goals created by users in Google Fit.\n- [`ConfigClient`](/android/reference/com/google/android/gms/fitness/ConfigClient): Access custom data types and settings in the Google Fit platform.\n\n[See an example of how to build a Fitness API client.](/fit/android/api-client-example)\n\n### Resulting user authorization flow\n\nThe following shows the resulting authorization flow that users experience\nwhen they're asked for permissions:\n**Figure 1.**The authorization flow for users.\n\n1. **Android permissions**: Users see what Android permissions your app has requested before downloading it. After your app is downloaded, it requests any runtime permissions that it needs, and users grant or deny these permissions.\n2. **Check and connect**: Your app checks whether permissions were granted before it requests access to other data types.\n3. **OAuth scopes request**: Google prompts the user to grant your app the OAuth scopes needed for the data types that it wants to access.\n4. **Access applied**: After the user grants permissions, your app can access the data types that belong to the scopes that the user has granted permission for.\n\nApply for verification\n----------------------\n\nAfter you build and test your app, you need to [apply for\nverification](/fit/verification) with different\nlevels of justification needed for\n[sensitive and restricted scopes](/fit/datatypes#authorization_scopes)."]]
