You might have seen Google’s announcement about the Fitbit API being replaced with a brand new API for health data called the Google Health API. As longtime Fitbit, now Google, partners, we’re excited to be part of helping test out this new API as it’s prepared for full release.
While this news may be fresh to the general public, we’ve been hard at work behind the scenes checking out the data the new API is returning, understanding how it maps to the data we currently pull and share with you, and coordinating with product and technical folks at Google on how best this API can work for research teams.
As noted in the Google announcement, this API will replace the current one in September 2026. At that time, the API that we’ve used to date will switch over.
What you can expect:
- Minimal change to the types and granularity of what you see for existing datasets on the Fitabase platform
- Authorization/security updates. The introduction of Google Oauth 2 may mean that existing participants will need to reauthorize Fitabase to pull their data from this new API.
- Ultimately, expanded dataset offerings that will serve more researchers and study topics
If you have any questions about how Fitabase is preparing for this switch or what it means for studies that are currently in flight, feel free to send them to hello@fitabase.com.