Are my files sent anywhere?

No. The check runs in your browser with JavaScript, and what you paste never leaves the page. Only an anonymous count of matches is recorded for usage statistics, and the example is not counted.

When did the Fitbit Web API stop working?

Google says support for the legacy Fitbit Web API ended on September 30, 2026, and set November 2, 2026 as the date it and the Fitbit OAuth endpoints are turned off, no longer function or sync data to or from Fitbit users, and return HTTP 410 Gone. dev.fitbit.com showed October 30. Google says to migrate to the Google Health API and Google OAuth 2.0.

When do the Google Fit APIs stop?

Google says the Google Fit APIs, including the REST API, are supported only until the end of 2026. It gives no specific day. New sign-ups stopped on May 1, 2024.

Does the Google Health API need a review?

Yes. Google classes all Google Health API scopes as Restricted, which means a privacy and security review before you get access. Leave time for it.

Free toolFitbit and Google Fit shutdown checker

Paste your dependency files or your app and server code to see whether they still call the legacy Fitbit Web API, which Google set to turn off on November 2, 2026, or the Google Fit APIs, which Google supports only until the end of 2026. The check runs in your browser; nothing is uploaded.

Check my app

Free, no sign-up. Dates checked October 24, 2026.

Fill in at least one box. The more you paste, the more it can check.

Dependency files

Paste several files one after another if you like. Commented-out lines are ignored.

App or server code

What it checks

November 2, 2026: Legacy Fitbit Web API; Google's date for turning it and the Fitbit OAuth endpoints off: requests return HTTP 410 Gone and data stops syncing. dev.fitbit.com showed October 30. The tool looks for api.fitbit.com, www.fitbit.com/oauth2 and the fitbitter, fitbit-node, passport-fitbit and python-fitbit libraries. Move to the Google Health API.
End of 2026: Google Fit REST API; Supported only until the end of 2026. The tool looks for googleapis.com/fitness/v1, fitness.googleapis.com, fitness scopes and the googleapis client calls. Move to Health Connect or the Google Health API.
End of 2026: Google Fit Android APIs; The Android Fit SDK and libraries built on it. The tool looks for play-services-fitness, the Fitness clients, react-native-google-fit and fit_kit. Move to Health Connect.
Replacements: Google Health API and Health Connect; When it sees health.googleapis.com, googlehealth scopes or androidx.health.connect, the tool marks them as found, so you can see what has already moved.

What this tool can’t see

It reads the text you paste. It can’t see transitive dependencies, a backend you didn’t paste, or a third-party service that calls Fitbit or Google Fit for you. A clean result means no match in the text, not that you are clear.

Shipping on Android too? The free Google Play deadline checker reads your Gradle files for the target API, 16 KB and Billing Library dates. Every app store and platform date is in App Store and Google Play deadlines for 2026 and 2027.

Questions

Are my files sent anywhere?: No. The check runs in your browser with JavaScript, and what you paste never leaves the page. Only an anonymous count of matches is recorded for usage statistics, and the example is not counted.
When did the Fitbit Web API stop working?: Google says support for the legacy Fitbit Web API ended on September 30, 2026, and set November 2, 2026 as the date it and the Fitbit OAuth endpoints are turned off, no longer function or sync data to or from Fitbit users, and return HTTP 410 Gone. dev.fitbit.com showed October 30. Google says to migrate to the Google Health API and Google OAuth 2.0.
When do the Google Fit APIs stop?: Google says the Google Fit APIs, including the REST API, are supported only until the end of 2026. It gives no specific day. New sign-ups stopped on May 1, 2024.
Health Connect or the Google Health API?: Google recommends Health Connect for mobile-first Android apps and step tracking, and the Google Health API for cloud integrations such as fitness tracker companion apps. Many health and fitness platforms need both.
Does the Google Health API need a review?: Yes. Google classes all Google Health API scopes as Restricted, which means a privacy and security review before you get access. Leave time for it.
If the checker finds nothing, am I clear?: Not necessarily. It reads only the text you paste. It can’t see transitive dependencies, a backend you didn’t paste, or a third-party service that calls Fitbit or Google Fit for you.

Sources, checked October 24, 2026: About the Google Health API, Migrate from the Fitbit Web API, Fitbit Web API authorization, Google Fit migration guide, Google Fit migration FAQ, Google Fit REST API get started, Google Fit Android get started, Health Connect get started.

Need the migration done before the date?

The App Fix Ticket covers it in two fixed-price steps. A $450 Diagnosis maps every Fitbit and Google Fit call in your app, picks Health Connect or the Google Health API for each, and gives you a fixed quote within 3 business days, credited toward the fix. If you go ahead, the $1,200 Fix comes as a pull request.

Pay $450 & start What the App Fix Ticket covers

Full refund if Simon can’t take it on once he sees your project, or if you cancel before work starts. Refund terms.

Writing about the Fitbit Web API turn-off, Google Fit or Health Connect? You’re welcome to link here. The checker is free, needs no sign-up, and never uploads what you paste.

HTML link

<a href="https://app369.com/tools/fitbit-google-fit-shutdown-checker/">Fitbit and Google Fit shutdown checker</a>

Fixed-price help for your app

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

App Fix Ticketfrom $450One reproducible bug in an existing mobile or web app, diagnosed and fixed.