Migration Overview: Why Fitabase Is Moving to the Google Health API
Learn why Google is retiring the Fitbit Web API in October 2026, why participants must reauthorize Fitabase, and what stays the same for your study.
Fitbit API to Google Health API Migration
What the move from the Fitbit Web API to the Google Health API means for your study: who must reauthorize, how to do it, key dates, and export changes.
Who Needs to Reauthorize
Find out which participants must reauthorize for the Google Health API: active, longitudinal, demo, and test accounts, versus those finishing before the cutoff.
How to Reauthorize Participants
Walk participants through Google Health API reauthorization via the Google Health app banner or a Fitabase link, and track who still needs to reconnect.
Reauthorizing Demo and Test Accounts
Reauthorize study-managed demo and test accounts yourself from the Requires reauthorization tab using Connect to Google Health and the account's credentials.
What Happens If a Participant Doesn't Reauthorize
See what happens when a participant misses the reauthorization deadline: past data is kept, new data pauses, and Fitabase backfills the gap once they reconnect.
Changes to Data Exports
Review how Fitabase exports change with the Google Health API: new UTC, time zone, and source columns, unchanged column names, and tips for export scripts.
Sample Message for Participants
Use this sample email or script to tell participants they must grant Fitabase permission again, via the Google Health app banner or their reauthorization link.
Key Dates and Timeline
Plan around key Google Health API migration dates: when reauthorization opens, the October 2026 Fitbit Web API shutoff, and the November 30 reconnect window.
Migration FAQ
Get answers to common researcher questions about the Google Health API move, including reauthorization, invitation links, IRB, step goals, and sleep data.