This fall, Google is retiring the Fitbit Web API and requiring all third-party apps, Fitabase included, to migrate to the Google Health API. This means that your study participants will need to grant permission again for Fitabase to access their data so that it continues to sync. We're hosting a webinar to walk through what's changing, who needs to take action, and how to keep your study's data flowing without interruption.
Date: September 22, 2026
Time: 10 a.m. PDT
Speakers: Aaron Coleman, Fitabase CEO and Hailey Persinger, Fitabase Head of Product
Register for the webinar here.
The OAuth reconnection requirement:
- Why this change is happening
- How already-enrolled participants can re-authorize seamlessly, as well as what new participants will need to do
- How to handle demo or test accounts yourself and how to invite the rest
- The process of reauthorization from start to finish
- How to encourage participants to reauthorize as soon as possible, plus the key dates to plan around
What's changing in your exports:
- Most fields map as before; we'll cover where the data shape changes.
- New UTC and time-zone columns, plus a source column showing whether data came from the Fitbit or Google Health API
How to plan for:
- Having every participant reconnected by October 31, 2026 so data sync isn't delayed at the Fitbit API shutoff
- Syncing delays during Google Health brown-outs as the transition is made to the new API
- Rewriting any scripts resilient to added columns
Whether your study is actively collecting Fitbit/Google data or just getting started, this session will give you what you need to keep your participants' data flowing into Fitabase.
Register for the webinar here.
Can't make it live? Register anyway and we'll send the recording afterward.
Feel free to reach out to hello@fitabase.com with any questions about the transition, the Google Health API, or using Fitabase to collect data for research.
See you there,
The Fitabase team