Tutorial
The Fitbit Web API was switched off on 2 November. Here's a Python path to the Google Health API
DEV Community: python · By Muhammet Savaş ·
The legacy Fitbit Web API and its OAuth endpoints were scheduled to be turned off on 2 November 2026. Apps that still call it stop receiving Fitbit and Pixel Watch data. The replacement is the Google Health API v4 , and there was no Python client for it, so I wrote one…
The Brief
- The legacy Fitbit Web API and its OAuth endpoints were scheduled to be turned off on 2 November 2026.
- Apps that still call the API stop receiving Fitbit and Pixel Watch data.
- The replacement is the Google Health API v4. No Python client existed, so the author wrote one.
Why it matters
Apps still using the Fitbit Web API lose access to Fitbit and Pixel Watch data and need to move to the Google Health API.
Who’s affected
- Developers whose apps call the Fitbit Web API
- Python developers integrating Fitbit or Pixel Watch data
What to do
- Migrate apps from the Fitbit Web API to the Google Health API v4
- Google Health API v4
- #fitbit
- #google-health-api
- #api-migration
- #python
- #wearables
- #oauth
Timeline
Fitbit Web API and OAuth endpoints turned off
DEV Community: python
The Fitbit Web API was switched off on 2 November. Here's a Python path to the Google Health API