BestPaid guides · Android · Health Connect

Google Fit APIs are supported only until the end of 2026 and the Fitbit Web API is already off: moving to Health Connect and the Google Health API

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.

Sources: Google's Fit migration guide (updated September 10, 2026), migration FAQ, REST API page, REST reference and data types (activity, location, health); the Google Health API About page, Fitbit migration guide, setup, scopes and endpoints pages; Health Connect's Get started, Read data, Write data, Data types, Metadata, Sync data, Rate limiting, Feature availability and Publish guides, the ActivityIntensityRecord reference, the Recording API on mobile guide and the release notes; Play Console Help on the Health apps declaration and health permissions; the dev.fitbit.com banner; the Flutter health changelog and the react-native-google-fit repository. Checked on November 21, 2026. This page is our own summary; follow the vendor's documentation for every detail.

What changes and when

DateWhat happens
May 1, 2024No new sign-ups for the Google Fit APIs.
September 30, 2026Support for the legacy Fitbit Web API ended.
November 2, 2026Fitbit Web API and Fitbit OAuth endpoints turned off; Google says requests to them fail with HTTP 410 Gone.
End of 2026Google 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.

Who is affected

Where each Fit API goes

You useGoogle'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 APIGoogle 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 APIAndroid sensors, the Fused Location Provider, Bluetooth APIs.
Goals APINo replacement.
Fit API on Wear OSHealth Services.
Fit REST API, Fitbit Web APIGoogle Health API. The FAQ says the Fit REST API has no alternative and also lists Health Connect.

Health Connect on Android: setup and permissions

<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>

Map Fit data types to Health Connect records

Google maps APIs, not data types; this table is ours. Check units and mandatory fields first.

Google Fit data typeHealth Connect recordPermission
com.google.step_count.deltaStepsRecordREAD_STEPS
com.google.distance.deltaDistanceRecordREAD_DISTANCE
com.google.calories.expended (includes BMR)TotalCaloriesBurnedRecordREAD_TOTAL_CALORIES_BURNED
com.google.heart_rate.bpmHeartRateRecord (series of samples)READ_HEART_RATE
com.google.activity.segment, sessionsExerciseSessionRecordREAD_EXERCISE
com.google.sleep.segmentSleepSessionRecord (with stages)READ_SLEEP
com.google.weightWeightRecordREAD_WEIGHT
com.google.blood_pressureBloodPressureRecordREAD_BLOOD_PRESSURE
com.google.heart_minutes, com.google.active_minutesNo 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.

Read and write records

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)
    )
)))

History and background access

Play Console: the health declarations

Back ends and iOS: the Google Health API

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.

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.

Order of work before the end of 2026

  1. Search code and servers for com.google.android.gms.fitness, googleapis.com/fitness/v1 and api.fitbit.com, and pick a path per call from Google's table.
  2. Fix Fitbit first: those calls already fail.
  3. Start the reviews now: the Play Console declaration and the Google Health API security review.
  4. Build Health Connect and the server sync on compileSdk = 36.
  5. Ship it next to Fit: Google says not to ask existing users to disconnect from Google Fit, and to put the new integration in new users' setup flow.
  6. Test on Android 13 and on 14 or higher with permissions denied, partly granted and revoked.
  7. Remove the Fit calls before the end of 2026; keep play-services-fitness only for the Recording API on mobile.
Still reading steps through Google Fit or Fitbit? We update native, Unity, Flutter, React Native and Xamarin apps to current SDKs and store rules at a fixed price. You keep your signing keys. It starts with a $290 check and a fixed quote within 2 business days.
See the app update offer