Google has published a clear timeline on its About the Google Health API page:
- Sept 30, 2026: support for the legacy Fitbit Web API ended. It still works, but no fixes.
- Oct 30, 2026: the Fitbit Web API is turned off.
Its replacement, the Google Health API, uses Google OAuth 2.0. Google says all its scopes are Restricted, so apps need a privacy and security review before they can access data. That’s good for privacy, but it raises the bar for small hobby projects.
Who is affected
Anything that reads Fitbit or Pixel Watch data through the old API: fitness dashboards, sync tools, scripts, and possibly integrations such as Home Assistant’s Fitbit integration. Check whether each tool you use has migrated before Oct 30.
What still works
Your data keeps syncing to Google through the Fitbit app. According to Google, migrated apps can query historical data once they’re on the new API.
Do this now
- Export a copy with Google Takeout (select Fitbit). Keep it somewhere you control.
- List the apps connected to your Fitbit account and check each for a Google Health API update.
- If you rely on a DIY script, plan to register a Google Cloud project and go through the new consent flow, or switch to periodic Takeout exports.
See the Fitbit Charge 6 and Pixel Watch 3 scorecards for the full picture.