Whether a participant needs to reauthorize depends on when they connected and whether they'll keep collecting data after the Fitbit Web API shuts off at the end of October 2026.
Existing participants who are still collecting data: yes
Every participant connected through the Fitbit Web API today must reauthorize to keep their data syncing past the cutoff. In most studies that means every active participant.
- Participants can reauthorize from a banner in the Google Health app or from a link you send them from Fitabase. See How to Reauthorize Participants.
- It takes a participant about a minute, roughly the same time as when they first authorized Fitabase.
- Reauthorization opens in the second half of October, earlier if possible. See Key Dates.
Tip:
Once reauthorization is available, the Requires reauthorization tab on your Participants page lists everyone who still needs to reauthorize.
Participants who finish before the cutoff: no
If a participant's data collection ends before the Fitbit Web API shuts off, they don't need to reauthorize. All the data synced before that date stays available in Fitabase.
Remember:
Make sure those participants do a final sync before they finish, so all of their data reaches Fitabase. When in doubt, reauthorize them anyway. It doesn't hurt.
Participants in longitudinal studies: yes, before their next collection period
If a participant is between data collection waves and will start collecting again after the cutoff, they still need to reauthorize. The option to reconnect stays available after the cutoff, so they can do it before their next wave begins.
Demo and test accounts: yes, and you can do it for them
Demo and test accounts, including the research accounts Google makes available to study teams, work the same way as participant accounts. If your team manages the credentials, you can reauthorize them yourself without involving the participant. See Reauthorizing Demo and Test Accounts.
New participants who join after the cutoff: no extra step
Anyone who connects after Fitabase switches over to the Google Health API goes through the normal authorization process and connects to the new API directly. There's nothing extra for them to do, and they won't notice a difference.
Note: Participants who connect before the switch
Participants who connect before Fitabase switches over are connected to the Fitbit Web API, so they will need to reauthorize like everyone else. After the switch, we'll show clearly in the platform who connected before it and still needs to reauthorize.
What about invitation links I've already created?
They'll keep working. Invitation links open a Fitabase page, and on that page we swap the old authorization button for the new one automatically. If you send a link before the switch and the participant opens it afterward, they'll connect to the Google Health API. You don't need to do anything.