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. |
| Mid-to-late October 2026 (exact date TBD) | Reauthorization opens. We'll email you and turn it on in the Fitabase platform. If we can open it earlier, we will. |
| End of October 2026 | Target for every active participant to be reauthorized. The Fitbit Web API shuts off, and participants who haven't reauthorized stop syncing new data. |
| Through November 30, 2026 | The reconnect banner stays 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 during the second half of October.
- 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.
- Update any export scripts so they tolerate new columns. See Changes to Data Exports.