DEV Community

antivex
antivex

Posted on

How to keep your Fitbit data after the Google Health switch

The old Fitbit Web API is shut down on 30 October 2026 (support already ended on 30 September). Apps that read your Fitbit data through it, like intervals.icu, lose that connection, and old tokens stop working. Here is what you can do, from easiest to most hands-on. All of it is free.

1. First, save a copy of your data

Go to Google Takeout (takeout.google.com), deselect everything, select only "Fitbit", and export. You get a zip with JSON and CSV files: sleep, heart rate, steps, weight and more. Keep it somewhere safe. Do this even if you plan to use the other options: it is your backup.

CSV files open in any spreadsheet. For sleep and steps, a pivot table by date is usually enough to see trends.

2. Check what your app already supports

Many apps are adding a connection to the new Google Health API. Look at the app's forum or changelog before building anything.

3. Android: Health Connect

The Google Health app writes sleep, heart rate, resting heart rate, HRV, weight, steps and exercises to Health Connect (Android 9 or newer; not iPhone). Some free apps read Health Connect and send the data to intervals.icu, for example ICU Coach on the Play Store and the open source intervals-icu-health-sync (GitHub). Without the history permission, only the 30 days before your consent are read, so connect early.

4. iPhone, or no Android: the Google Health API

The new Google Health API replaces the Fitbit Web API. For personal use you can create a free Google Cloud project, keep it in "Testing" mode and add yourself as a test user. Limits you should know:

  • the authorization expires after 7 days, so you re-approve about once a week;
  • you see an "unverified app" warning each time;
  • sleep, resting heart rate, HRV, weight and steps are available.

Two open source options use this route to write to intervals.icu: giabisson/fitbit-intervals-sync (Python, renewal link via Telegram) and the bridge I made, google-health-to-intervals (runs on your own free GitHub account, still in testing, looking for iPhone testers): https://github.com/Alessandro-barrale/google-health-to-intervals

If you only want charts, arpanghosh8453/fitbit-grafana reads the Google Health API into Grafana.

5. What will not transfer easily

Women's health data is exported by Takeout, but almost no app imports it. Keep the raw files. The same goes for minute-level heart rate: it is in the export, but few destinations accept it.

Checklist before 30 October

  1. Take a Takeout export of your Fitbit data.
  2. Check what your app plans to support.
  3. Choose one route (Health Connect or Google Health API) and set it up this week, not on the 30th.
  4. Check that sleep, resting heart rate and HRV show up for a few days.

I wrote a 15-page step-by-step guide with the full setup for each route, for people who want it done in one evening (pay what you want, from 5 EUR): https://antivex.gumroad.com/l/fitbit-google-health-intervals

Sources: Google Health API docs (developers.google.com/health/about, /setup, /data-types) and Health Connect docs, read on 22/10/2026.

Top comments (0)