Google supports the Google Fit APIs, Android and REST, only until the end of 2026, and turned the legacy Fitbit Web API off on November 2, 2026. Who is affected, how Android apps move to Health Connect, where back ends and iOS apps go, and what to do first.
| Date | What happens |
|---|---|
| May 1, 2024 | No new sign-ups for the Google Fit APIs. |
| September 30, 2026 | Support for the legacy Fitbit Web API ended. |
| November 2, 2026 | Fitbit Web API and Fitbit OAuth endpoints turned off; Google says requests to them fail with HTTP 410 Gone. |
| End of 2026 | Google Fit APIs, REST included, supported until then (no exact day given). Google's FAQ says that after the migration period they will no longer be available for use. |
The dev.fitbit.com banner still says October 30; the Google Health API About page, updated November 16, says November 2.
com.google.android.gms.fitness): step counters, workout and coaching apps, wellness and corporate-wellness challenges, insurance rewards, physiotherapy and research apps.https://www.googleapis.com/fitness/v1/users).health package dropped Google Fit in 11.0.0; react-native-google-fit, a Google Fit bridge, is archived on GitHub.| You use | Google's recommended path |
|---|---|
| Recording API (steps) | Health Connect, whose step total includes on-device steps on Android 14 and higher (with SDK extension 20 or higher); with many users on Android 13 or lower, add the Recording API on mobile. |
| History API, Sessions API | Google Health API. For Wear OS apps, Google says to start and stop sessions with Health Services (ExerciseClient) and to read and write through Health Connect in the mobile app, inserting sessions as ExerciseSessionRecord or SleepSessionRecord. |
| Sensors API, BLE API | Android sensors, the Fused Location Provider, Bluetooth APIs. |
| Goals API | No replacement. |
| Fit API on Wear OS | Health Services. |
| Fit REST API, Fitbit Web API | Google Health API. The FAQ says the Fit REST API has no alternative and also lists Health Connect. |
androidx.health.connect:connect-client:1.1.0 (Google's guides use 1.2.0-alpha06). 1.1.0 and later need compileSdk = 36 and Android Gradle plugin 8.9.1 or higher.<manifest ...>
<uses-permission android:name="android.permission.health.READ_STEPS" />
<queries>
<package android:name="com.google.android.apps.healthdata" />
</queries>
<application ...>
<!-- Android 13 and lower -->
<activity android:name=".PermissionsRationaleActivity" android:exported="true">
<intent-filter>
<action android:name="androidx.health.ACTION_SHOW_PERMISSIONS_RATIONALE" />
</intent-filter>
</activity>
<!-- Android 14 and higher -->
<activity-alias android:name="ViewPermissionUsageActivity" android:exported="true"
android:targetActivity=".PermissionsRationaleActivity"
android:permission="android.permission.START_VIEW_PERMISSION_USAGE">
<intent-filter>
<action android:name="android.intent.action.VIEW_PERMISSION_USAGE" />
<category android:name="android.intent.category.HEALTH_PERMISSIONS" />
</intent-filter>
</activity-alias>
</application>
</manifest>
Google maps APIs, not data types; this table is ours. Check units and mandatory fields first.
| Google Fit data type | Health Connect record | Permission |
|---|---|---|
com.google.step_count.delta | StepsRecord | READ_STEPS |
com.google.distance.delta | DistanceRecord | READ_DISTANCE |
com.google.calories.expended (includes BMR) | TotalCaloriesBurnedRecord | READ_TOTAL_CALORIES_BURNED |
com.google.heart_rate.bpm | HeartRateRecord (series of samples) | READ_HEART_RATE |
com.google.activity.segment, sessions | ExerciseSessionRecord | READ_EXERCISE |
com.google.sleep.segment | SleepSessionRecord (with stages) | READ_SLEEP |
com.google.weight | WeightRecord | READ_WEIGHT |
com.google.blood_pressure | BloodPressureRecord | READ_BLOOD_PRESSURE |
com.google.heart_minutes, com.google.active_minutes | No record of that name; nearest: ActivityIntensityRecord (1.2.0-alpha06) | READ_ACTIVITY_INTENSITY |
Full names start with android.permission.health.; writes need the matching WRITE_ permission.
if (HealthConnectClient.getSdkStatus(context) != HealthConnectClient.SDK_AVAILABLE) return
val client = HealthConnectClient.getOrCreate(context)
val permissions = setOf(
HealthPermission.getReadPermission(StepsRecord::class),
HealthPermission.getWritePermission(StepsRecord::class)
)
val request = registerForActivityResult(
PermissionController.createRequestPermissionResultContract()
) { granted -> /* keep working with what was granted */ }
request.launch(permissions)
// In a coroutine; aggregate avoids double counting across sources
val steps = client.aggregate(
AggregateRequest(
metrics = setOf(StepsRecord.COUNT_TOTAL),
timeRangeFilter = TimeRangeFilter.between(start, end)
)
)[StepsRecord.COUNT_TOTAL] ?: 0L
// A recording method is mandatory; clientRecordId enables upserts
client.insertRecords(listOf(StepsRecord(
count = 120, startTime = start, endTime = end,
startZoneOffset = offset, endZoneOffset = offset,
metadata = Metadata.autoRecorded(
clientRecordId = row.id, // your own database ID
device = Device(type = Device.TYPE_PHONE)
)
)))
readRecords() pages at 1,000 records by default; follow pageToken.Metadata comes from autoRecorded(), activelyRecorded(), manualEntry() or unknownRecordingMethod(). With clientRecordId set, insertRecords upserts; with clientRecordVersion, only a higher version overwrites.getChangesToken), call getChanges until hasMore is false, skip your own package's writes, upload. Background rate limits are stricter.android.permission.health.READ_HEALTH_DATA_HISTORY; background reads need android.permission.health.READ_HEALTH_DATA_IN_BACKGROUND (Google's example schedules them with WorkManager).getFeatureStatus() with FEATURE_READ_HEALTH_DATA_HISTORY or FEATURE_READ_HEALTH_DATA_IN_BACKGROUND.For web platforms and server-to-server integrations, Google's migration guide points to the Google Health API, the Fitbit Web API's successor. Unlike device-centric Health Connect, it is account-centric and platform-agnostic, so iOS apps can use it too: Google OAuth 2.0, REST or gRPC, stable base URI https://health.googleapis.com/v4.
https://www.googleapis.com/auth/googlehealth, such as .activity_and_fitness.readonly.ACCOUNT_NOT_LINKED. Call users.getIdentity right after consent.Fitbit Web API users: tokens can't be carried over, so every user re-consents. users.getIdentity returns legacyUserId and healthUserId to map your records; backfill the gap once they reconnect. Above 10,000 sign-ups or re-authentications in a 24-hour window, request a higher OAuth token grant quota first.
com.google.android.gms.fitness, googleapis.com/fitness/v1 and api.fitbit.com, and pick a path per call from Google's table.compileSdk = 36.play-services-fitness only for the Recording API on mobile.