AI & TechnologyGoogle Fit API Deprecated: Moving to Health Connect in 2026

The Google Fit APIs are on their way out: Google says they, including the REST API, will only be supported until the end of 2026, and no new developers have been able to sign up since May 1, 2024. Google recommends Health Connect for step tracking and mobile-first Android apps, and the Google Health API for cloud-based integrations. Which one you need depends on which Fit APIs your app calls, and some features, such as Goals, have no replacement at all.

If you landed here from an old link to the Google Fit docs or a Fit tutorial, this is what changed and where each piece goes. The dates and mappings come from Google’s Fit and Health documentation and the Android Fit migration guide, as listed in the sources. I checked each page on October 24, 2026.

Disclosure: App369 is my studio. I build and fix mobile apps, including Flutter apps on Android and iOS, and the last section mentions what I sell. Google doesn’t pay me for anything on this page.

What happened to Google Fit, and when

Google hasn’t published an exact turn-off date for the Fit APIs. The migration guide says Google will keep its section on existing Fit app integrations updated with when to deprecate them.

What the old addresses do today

Checked on October 24, 2026:

• developers.google.com/fit still loads, with a banner saying the Fit APIs will be deprecated in 2026 and new sign-ups closed on May 1, 2024. The Android and REST getting-started pages still load too.
• developers.google.com/fit/migration returned 404.
• The old Health Connect migration guide address redirects to the new Fit migration guide on developer.android.com.
• A request to the Fit REST API at googleapis.com/fitness/v1 without sign-in returned 401, so the API still answers for now.

Which replacement fits your app

Google’s migration guide picks the path by app type:

And by which Fit API you call today:

Source: Fit migration guide, last updated September 10, 2026. Check the Health Connect docs for which Android versions have it built in and which need the separate app from Google Play. For inserting a workout or sleep session, the guide says to use Health Connect from the phone app with an ExerciseSessionRecord or SleepSessionRecord.

Health Connect is not a drop-in swap

The migration guide compares the two. The Fit API for Android is registered in Google Cloud Console, is cloud-centric and uses OAuth 2.0 with OAuth scopes. Health Connect is registered through your Play Store project and a health apps declaration, stores data on the device, needs no OAuth, and uses Android manifest permissions. My read: that means changes to your sign-in flow, your permission screens and your Play Console declaration, not just the API calls.

The Google Health API is the other way round: Google describes it as the next generation of the Fitbit Web API, with OAuth 2.0 access to data from Fitbit, Pixel Watch and other devices and apps. If your backend pulled Fit history through the REST API, this is the closer fit.

What to do now

This section is my advice, not Google’s.

1. List every Fit call. Search the app and backend for com.google.android.gms.fitness, Fitness.get, googleapis.com/fitness/v1 and any Fit OAuth scopes. Note which of the APIs in the table above each one uses. To scan pasted dependency files and code for Fit and legacy Fitbit calls, the free Fitbit and Google Fit shutdown checker runs in your browser.
2. Check your Flutter package, and any other health library you use. The Flutter health package says it removed Google Fit support in version 11.0.0 and now uses Health Connect on Android. If your app pins an older version, the upgrade and the Health Connect move are the same job.
3. Pick the path per feature, not per app. A step counter can move to Health Connect while a synced workout history moves to the Google Health API. Use the two tables above.
4. Plan the permission change. Health Connect asks users for on-device permissions instead of a Google sign-in. Write the new permission screen copy, and fill in the health apps declaration in Play Console before you submit the update.
5. Rebuild goals yourself. Google lists no replacement for the Goals API, so store goals in your own app or backend and compare them with the data you read.
6. Keep existing users working while you switch. Google’s guide says that if your app has a way for users to connect to Google Fit, or is on the Works with Google Fit list, you can keep that integration for current users, and that Google will update the guide with when to deprecate it. Google recommends offering Health Connect or the Google Health API as a new option, and not asking users to disconnect from Google Fit.
7. If you also use the Fitbit Web API, do that first, because Google’s date for turning it off, November 2, 2026, has passed (dev.fitbit.com showed October 30). Google says requests to it return HTTP 410 Gone.

For every other dated Apple, Google Play and Firebase requirement in 2026 and 2027, see App Store and Google Play deadlines for 2026 and 2027.

Need a hand?

If your app reads steps, workouts or sleep through Google Fit and you need it moved to Health Connect or the Google Health API, the App Fix Ticket covers it in two fixed-price steps. A $450 Diagnosis gives you the root cause with evidence and a fixed repair quote within 3 business days, credited toward the fix. If you go ahead, the $1,200 Fix takes 5 business days. If the app was built with an AI tool and you’re not sure what it calls, the AI-Built App Rescue starts with a $450 Launch Check in 3 business days. Or send me a short description.