The Fitbit Web API has been improved and modernized to provide a more standardized, consistent, and scalable foundation for developer integrations, and is now called the Google Health API. The Google Health API represents the strategic evolution of the legacy Fitbit Web API, rebuilt from the ground up on Google's modern infrastructure.
With this platform, developers gain access to the full power of Google Cloud developer tooling and the convenience of a familiar, streamlined way for users to manage their permissions through Google OAuth 2.0.
What do you get with the Google Health API?
- Unified source of truth: Our new "Reconciled Stream" handles the complex task of reconciling overlapping data points from multiple sources. This ensures apps display the same consistent data users see within the Fitbit app. This stream will be provided in addition to our first party stream which includes data from Fitbit and Pixel devices, as well as manual entries.
- Technical modernization & performance: We have consolidated over 100 legacy endpoints down to a streamlined set of simplified data type bundles and eliminated inconsistencies in data formats, time zones, measurement units, and error handling. Furthermore, we now support the HTTP/REST protocol for high-performance data retrieval. Additionally, intraday data and webhooks are now available for all relevant data types through a dedicated list endpoint.
- Enhanced webhooks & scalability: Benefit from expanded webhook support, including auto-subscriptions and detailed management for all relevant data types, designed to scale with the next generation of AI-driven health apps.
- Streamlined identity & security: Replace legacy Fitbit Authorization (FOT) with Google OAuth 2.0. This allows developers to utilize standard Google authentication libraries, simplifying codebases while providing users with a familiar, centralized way to manage their permissions. All Google Health API scopes are categorized as Restricted, necessitating a privacy and security review for access.
Like what you see? Get started now!
What about the Fitbit Web API?
The legacy Fitbit Web API is being turned down according to the following timeline:
- September 30, 2026 (End of support): Support for the Fitbit Web API ends. The API will continue to operate, but Google will no longer fix bugs or provide API support.
- October 30, 2026 (API turn-off): The Fitbit Web API will be turned off and will no longer function or sync data to or from Fitbit users.
All current integrations utilizing the Fitbit Web API and Fitbit Authorization must migrate their applications and users to the Google Health API and Google OAuth 2.0 as soon as possible to ensure uninterrupted data continuity.
See the migration guide to get started.
What devices are supported?
All Fitbit devices and Google Pixel watches, current and previous, will collect data that is returned through the Google Health API. The type of data available will depend on the functionality the devices support.
The list of current devices can be found on the Google Store.
How do I provide feedback?
Your feedback is highly valued. We encourage you to share your thoughts through our support channels, which are listed on the Support page.
While we have gone to great lengths to ensure these APIs support you well, the Google Health API is actively evolving. Please be aware that based on your feedback, we may introduce changes between now and the end of May that would require corresponding updates on your end.
Roadmap
These are a list of features that are coming in 2026.
Q4 2026
Data Types (read & write)
- Granular skin temperature
- Basal Metabolic Rate
- We'll be adding data types to reach parity with Health Connect. You can expect many more of the Health Connect data types to be added in Q4 2026 and Q1 2027.
Features
- Public beta channel for early access to new data types
- Statistics endpoint to monitor webhooks telemetry