The Fitbit API Shutdown Cuts Off Linked Apps on October 30 Unless You Reconnect Them

Fitness tracker on a wrist resting on a kitchen table beside a phone showing a generic sync prompt and a bowl of breakfast.
Illustration (AI-generated).

For years, the old Fitbit Web API has let apps such as MyFitnessPal read steps, sleep, heart rate and food logs from a Fitbit or Pixel Watch account. Google stopped supporting it today, September 30, and switches it off on October 30. From then on, an app still using it gets no new data from you until you reconnect it through Google’s new system. Google started emailing owners about the change this week, but MyFitnessPal is asking its members to wait for its own prompt first.

The two dates in Google’s notice

Google’s developer page, last updated on September 29, puts the end of support for the legacy Fitbit Web API on September 30. From that day the API keeps running, but Google no longer fixes bugs in it. On October 30 it will be “turned off and will no longer function or sync data.”

Fitbit’s own developer site said only that the API was being deprecated “in September 2026”, so until last week most reports gave today as the cut-off. The extra month first surfaced on September 24, when a developer quoted an email from Google on its support forum. The Fitbit site has since added the October 30 switch-off date.

The replacement is the Google Health API, which signs you in with a Google account in place of the old Fitbit login. Google’s migration guide says the old sign-in tokens “cannot be transferred”, so the permission you once gave an app doesn’t carry across. Every app that reads your Fitbit data from Google’s servers needs you to approve it again on a new Google screen.

The Fitbit API shutdown only affects apps that fetch your data from Google’s servers, and plenty of connections never worked that way. On Android, apps exchange data with the Google Health app through Health Connect, a data store on the phone itself. Apple Health does the same job on an iPhone. Google’s help page names Garmin, Oura, Samsung and Xiaomi devices as ones that use these routes.

A link set up in Health Connect or Apple Health doesn’t use the Fitbit Web API, so October 30 leaves it alone. The links at risk are the ones you approved on a Fitbit or Google web page, usually after tapping a connect button inside the other app. MyFitnessPal is one of them. Developers have also named MyDataHelps, an app that research studies use to collect wearable data.

Google’s email and your app’s prompt

Google told partner apps that from the week of September 28 it would email Google Health members about re-authorizing the apps linked to their accounts. MyFitnessPal’s help center, updated four days ago, tells its members to hold off for now: “No action is needed from you yet. Please wait for a prompt from MyFitnessPal (push notification and/or email) in mid-October before reconnecting.”

The same article warns that anyone who disconnects and reconnects after Google’s email will have to do it again when MyFitnessPal’s prompt arrives. Only that second reconnection keeps data flowing after the switch-off. Google’s guide explains why. Each app has to build the new Google consent flow into its own code, and until it ships that update, its connect button can only lead back to the old system.

Reconnect from inside each app once that app asks you to. Google’s email tells you the change is coming. It can’t tell you whether a particular app is ready for it.

Diagram of the two ways apps get Fitbit data, with phone links through Health Connect or Apple Health unaffected and cloud links needing a reconnect before the Fitbit Web API switches off on 30 October.

Apps that may not be able to move

Google’s developer page also says: “While we are not onboarding new projects at this time, we are actively working to open access to more developers.” An app that didn’t already have access to the Google Health API can’t move to it, however willing its developer is. For a small app or a single research study, October 30 could be the last day your data arrives.

Google has not published a list of approved partners, so from outside you can’t tell which apps have access. The practical test is whether an app has said anything. If one hasn’t asked you to reconnect or posted a help article about the change by the second half of October, write to its support team. Ask whether it will still receive your data in November.

Before October 30

Your history is safe either way. Google’s guide says your data stays in your account as long as the watch or tracker keeps syncing to the Google Health app. An app you reconnect later can fetch the days it missed, so the risk is a gap in that app’s records.

  1. Open the Google Health app, tap Connections at the top left, then Partner apps or Apps and services. The Connected list shows every service that reads your account.
  2. Finish setting up your Google Health profile if you haven’t yet. Google’s guide tells developers that linking fails for anyone whose profile is incomplete and asks them to send those people back to the app. If you set up blood pressure trends on a Pixel Watch last week, you’ve already done this.
  3. When an app sends its own prompt, reconnect from inside that app. The Google consent screen lets you approve data types one at a time. An app receives nothing you leave unticked, so allow whatever it needs to work.
  4. In the first days of November, open each linked app and check that new days are arriving.

What Google has not said

Google has not said whether October 30 could move again, though its Fitbit developer site has since adopted that date. It also hasn’t named the partners with access to the new API, or said what the emails to owners will ask them to do. If an app you rely on says it can’t migrate, export anything you keep only in that app before the end of October. Your Fitbit history stays in Google Health regardless.

Sources

Basis

Research-based: written from the published sources listed above, primary: Google, Google (Fitbit developer site). We have not used the products discussed ourselves, and any measurement quoted belongs to its source.

This article was created with the help of AI. How we work

← Back to the blog