Google has announced that it will be replacing the Fitbit Web API with the new Google Health API. This is a significant change for the wearable research ecosystem, and we want to make sure you know what to expect and how Fitabase is preparing.
What's changing?
Google is consolidating its health and fitness data platforms under a single API. The existing Fitbit Web API, which Fitabase has used to collect participant data for years, will be replaced by the Google Health API. The transition is planned for September 2026.
What does this mean for your research?
We expect minimal change for existing datasets. The types of data available through the new API should remain largely the same, and your historical data collected through Fitabase will not be affected.
However, there are a few things to be aware of:
- Google OAuth 2 may require participant reauthorization. Depending on how Google handles the migration of existing tokens, some participants may need to reconnect their accounts.
- Fitabase is already actively working with Google to test the new API and ensure a smooth transition for our users.
- We will communicate any required actions well in advance so you have plenty of time to plan.
What is Fitabase doing?
Our engineering team has been working directly with Google to gain early access to the new API. We are actively testing data retrieval, authentication flows, and compatibility with our existing platform features. Our goal is to make this transition as seamless as possible so that your research is not disrupted.
We'll continue to share updates as we learn more. If you have any questions or concerns about the transition, please don't hesitate to reach out to us at hello@fitabase.com.