These are the dates to plan around for the move to the Google Health API. We're still finalizing some of them with Google, and we'll update this page as they're confirmed. We'll also email every Fitabase customer and post a notice in the platform if anything changes.
| When | What happens |
|---|---|
| September 22, 2026 | Webinar: What Researchers Need to Know About the Fitbit API Transition. Watch the recording. |
| Available now | Participants can reconnect from the Partner apps screen in the Google Health app. |
| October 15, 2026 | Reauthorization opens in the Fitabase platform. We'll email you when reauthorization links and Connect to Google Health are live. |
| October 30, 2026 | Target for every active participant to be reauthorized. The Google Health app asks participants to reconnect by this date to keep their data syncing without interruption. The Fitbit Web API shuts off on this date, and participants who haven't reauthorized stop syncing new data. |
| Through November 30, 2026 | The reconnect option stays on the Partner apps screen in the Google Health app, giving participants who missed the deadline a way back. Reauthorization links from Fitabase also keep working. |
| Ongoing during the transition | Short "brown-outs" may delay syncing while Google moves traffic to the Google Health API. |
What you can do now
- Set aside time for your team to contact participants between now and October 30.
- Encourage participants to update their Google Health app before reauthorizing to the new API.
- Give participants a heads-up that a request is coming. Our sample message can help.
- Try the process on a test account as soon as reauthorization opens in Fitabase on October 15.
- Update any export scripts so they tolerate new columns. See Changes to Data Exports.