Fitbit API shutdown may have been pushed back by a month

Google may have given developers another month to move existing Fitbit users onto the Google Health API. An email sent to at least one developer says the migration deadline has moved from September 30 to October 30, although Google’s public documentation still hasn’t caught up.

The deadline appears to have moved

Back in June, a Google Health Community specialist said September 30, 2026 was the exact date when the Fitbit Web API would be fully decommissioned and disabled. Existing authorisations and refresh tokens were also expected to stop working at that point.

But a developer posted on Google’s support forum on September 24 saying they had received a new email from Google. According to the message, Google is “extending the user migration deadline to October 30, 2026,” while official developer support for the legacy Fitbit API will still end on September 30. 

That suggests Google may now be separating two deadlines. Developer support would end on September 30, but existing Fitbit API connections could keep working until October 30 while users complete the migration.

Google’s own documentation still says September

Google’s main developer page still says the legacy Fitbit Web API will be turned down in September 2026 and tells developers to migrate before then. It does not currently mention the reported October 30 extension. So this is all yet to be confirmed.

There is some support for the later date elsewhere. MyDataHelps, which provides health-data tools used in research projects, has updated its own migration guidance to say the Fitbit API will shut down on October 30.

So October 30 increasingly looks like the new cutoff, but Google’s public-facing documentation remains inconsistent. With September 30 almost here, that is likely to leave some developers wondering exactly what will stop working this week.

Users still have to reconnect

Moving from the Fitbit Web API to Google Health is not something developers can handle entirely in the background. Google uses a different OAuth system for the new API, so existing Fitbit access and refresh tokens cannot simply move across.

Users therefore need to authorise the connection again. Google’s migration guide recommends temporarily supporting both systems, keeping existing users on the Fitbit API until they complete the new Google Health consent process. 

That makes an extra month useful. Developers may already have moved their apps to Google Health technically, but some users will not have opened the app, seen the migration notice or reconnected their Fitbit account yet.

The switch is part of Google’s wider move away from the old Fitbit software platform. The company has rebuilt the API around Google infrastructure and Google OAuth, while retaining access to data from Fitbit devices and Pixel Watches.