Migration Overview: Why Fitabase Is Moving to the Google Health API
Learn why Google is retiring the Fitbit Web API on October 30, 2026, why participants must reauthorize Fitabase, and what stays the same for your study.
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.
Learn why Google is retiring the Fitbit Web API on October 30, 2026, why participants must reauthorize Fitabase, and what stays the same for your study.
Find out which participants must reauthorize for the Google Health API: active, longitudinal, demo, and test accounts, versus those finishing before the cutoff.
Walk participants through Google Health API reauthorization in the Google Health app Partner apps screen or a Fitabase link, and track who needs to reconnect.
Reauthorize study-managed demo and test accounts yourself from the Requires reauthorization tab using Connect to Google Health and the account's credentials.
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.
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.
See which Fitabase exports include Google Health API data today, which are delayed, which stay Fitbit API only, and which datasets are new in Google Health.
Use this sample email or script to tell participants they must grant Fitabase permission again, in the Google Health app or with their reauthorization link.
Plan around key Google Health API migration dates: when reauthorization opens, the October 30 Fitbit Web API shutoff, and the November 30 reconnect window.
Get answers to common researcher questions about the Google Health API move, including reauthorization, invitation links, IRB, step goals, and sleep data.