# Fitbit’s legacy Web API shuts down October 30 — integrations must move to Google Health API Google has put a hard end date on the legacy Fitbit Web API: after October 30 it will stop functioning and syncing Fitbit user data, forcing existing integrations onto the Google Health API and Google OAuth 2.0. Fitbit API integrations have less than a month to migrate. The replacement changes authentication and API surface, while Google is still restricting onboarding for new Health API projects. - Status: Active - Published: 2026-10-08T06:22:55+13:00 - Updated: 2026-10-08T06:22:55+13:00 - Categories: Web Development, Developer Tools - Tags: API deprecation, API migration, Fitbit, Google Health API, OAuth - Canonical HTML: https://beyondthe.news/dossiers/fitbit-web-api-shutdown-google-health-api-october-30-2026 ## What changed Google's current Health API documentation says support for the legacy Fitbit Web API ended on September 30, 2026. The API continues operating temporarily, but on October 30 it will be turned off and will no longer function or sync data to or from Fitbit users. Developers must migrate integrations to the Google Health API. The replacement also moves authorization from legacy Fitbit authorization to Google OAuth 2.0. Google says it is not currently onboarding new projects to the Health API, although it is working to expand access. ## Why it matters This is a hard compatibility deadline rather than a documentation deprecation. Apps, dashboards, automations and research systems that still read or write Fitbit data through the legacy Web API can stop working after October 30. Migration also changes the identity/authentication boundary, so teams need to test consent, token handling, scopes, data-type mapping and user relinking rather than merely swapping an endpoint hostname. The restricted onboarding state creates an additional risk for developers trying to launch a new Fitbit-connected product during the transition. ## The old API stops working on October 30 Google says the legacy Fitbit Web API entered unsupported operation after September 30 and will be turned off October 30. After that date it will no longer function or sync Fitbit user data. ## Authentication moves to Google OAuth 2.0 The Google Health API replaces legacy Fitbit authorization with Google OAuth 2.0. Existing integrations therefore need to account for a new authorization flow and permission-management surface as part of the migration. ## The replacement API is not fully open to new projects Google's documentation currently says it is not onboarding new projects to the Google Health API and is working to expand access. Existing developers should verify project eligibility rather than assuming a new integration can be provisioned immediately. ## Treat this as a data-pipeline migration Builders should inventory every Fitbit endpoint and data type they use, map those dependencies to the Health API, test OAuth consent and refresh behaviour, validate historical and ongoing sync semantics, and plan for users who do not complete any required relinking before the cutoff. ## Key details - Legacy Fitbit Web API support ended September 30, 2026. - Google says the Fitbit Web API will be turned off October 30, 2026. - After shutdown the legacy API will no longer function or sync data to or from Fitbit users. - Developers are directed to migrate to the Google Health API. - The replacement uses Google OAuth 2.0 instead of legacy Fitbit authorization. - Google currently says it is not onboarding new Health API projects while it works to expand access. ## Builder takeaways - Audit production code, scheduled jobs and third-party integrations for legacy Fitbit Web API calls now. - Test the Google OAuth 2.0 migration as an identity and consent change, not just an endpoint migration. - Verify that every Fitbit data type your product depends on has an acceptable Health API path and semantics. - Plan user communication/relinking before October 30 if migration changes authorization state. - If building a new Fitbit-connected product, confirm Health API onboarding eligibility before committing to a launch date. ## What to watch - Whether Google opens Health API onboarding to more new projects before October 30. - Any migration extensions or exceptions announced before shutdown. - Changes to supported data types, OAuth scopes or Fitbit migration tooling. - Operational reports from developers as production integrations move to the replacement API. ## Uncertainties - Google has not given a public date for broad new-project onboarding to the Health API. - Individual integrations may require different user reauthorization or data-model changes depending on the Fitbit endpoints they currently use. ## Sources - [Data Access and Authorization](https://developers.google.com/health/migration/data-access) — Google Health API · primary documentation · 2026-10-03T00:00:00+13:00. Current Google documentation stating the September 30 support end, October 30 shutdown, Google OAuth 2.0 migration and restricted new-project onboarding.