Quick Verdict
If any third-party app reads your Fitbit data, open it this month and check that it still shows today's numbers. Fitbit's own developer site now carries a deprecation notice: "The Fitbit Web APIs are moving to a new, scalable infrastructure. We will be deprecating the legacy Fitbit Web API in September 2026." That interface is the pipe almost every non-Google app has used to pull your steps, sleep and heart rate out of Fitbit. Its replacement is the Google Health API, which Google's developer site describes as "the next generation of the Fitbit Web API" and runs on Google's OAuth 2.0 framework rather than Fitbit's. The consumer half of the change already happened: Google's help center says that starting May 19, 2026, the Fitbit app became the Google Health app.
Here is the catch, and it is the reason this is worth ten minutes of your time rather than none. No single authoritative consumer shutdown date has been published, and the apps that have warned their users do not say the same thing. Big Team Challenge tells members they "must update your connection to Google Health before the 30th September 2026". HealthCheck360 tells its users the transition "is automatic for existing Fitbit users and preserves all historical workout stats and health metrics". Both statements can be true, because two different things moved: your Fitbit account, which Google migrated for you, and the authorisation each separate app holds to read your data, which in general it did not. Fitbit's own notice names a month and not a day. The practical conclusion is unglamorous: assume every app connection needs to be redone before the end of September, and verify it by looking at real numbers rather than at a green "connected" label.
What Changed, and When
Every row below comes from the page named in the last column, fetched for this article. We have kept the attribution per row on purpose, because the dates come from different kinds of source and carry different weight.
| Date | What happened | Stated by |
|---|---|---|
| May 19, 2026 | "Starting May 19, 2026, the Fitbit app will become the Google Health app" | Google Health Help Center |
| May 19 to 26, 2026 | Accounts already connected to a Google Account update automatically; standalone Fitbit accounts must be moved to Google | Google Health Help Center |
| Around May 25, 2026 | Weight stopped reaching at least one partner platform through the connection | HealthCheck360 |
| September 2026 | "We will be deprecating the legacy Fitbit Web API in September 2026" | Fitbit developer site |
| September 30, 2026 | "You must update your connection to Google Health before the 30th September 2026" | Big Team Challenge |
Two things are worth noticing in that table. The only first-party date for the developer interface is a month, not a day, so September 30 is one partner's reading of it rather than a published Google deadline. And the weight row is the kind of detail that never makes a headline: a single metric quietly stopped crossing over six days after the app changed name, and the only place that is written down is a corporate wellness vendor's help article.
One more change is buried in Google's own notes and matters if it applies to you: the help center states that connections to Lifescan devices are no longer supported. That is a hard removal, not a reconnection.
Why Your Apps Have to Ask You Again
The short version is that the login moved houses. The legacy Fitbit Web API authenticated against Fitbit. The Google Health API, in Google's own words, lets developers "view and manage health and fitness metrics and measurement data from Fitbit, Pixel Watch, and other third-party devices and apps" on "a unified API infrastructure on Google's secure OAuth 2.0 framework". When the identity provider changes, the permission an app was granted under the old one does not automatically become a permission under the new one.
You can see that in the instructions partners are writing. HealthCheck360 tells users to pick "Continue with Google. Do not put in your email address or password as Fitbit is now connected with Google", and to "Ensure that you select Allow All to make the connection". Big Team Challenge walks members through Sync Device settings, a "Start update" button, and "Reconnect with Google" using the same account linked to their Google Health app. Both flows are a fresh sign-in, not a silent handover.
The detail that catches people out is the account choice. If you ever had a standalone Fitbit login and a separate Google account, the reconnection screen will happily let you authorise the wrong one, and the app will then sync an empty account rather than fail loudly. Big Team Challenge is explicit that it has to be the same Google account as the one in your Google Health app.
The Two Routes Fitbit Data Can Take
There are now two distinct ways your Fitbit numbers reach another app, and they fail for different reasons. Knowing which one your app uses tells you what to check.
| Route | Works on | Who has to do the work | How it breaks |
|---|---|---|---|
| Cloud, through the Google Health API | iPhone and Android | The app developer migrates, then you re-authorise with Google | Developer did not migrate, or you never re-authorised |
| On-device, through Health Connect | Android only | You grant per-data-type permissions on the phone | A data type was never permitted, or the source app stopped writing it |
| Apple Health | iPhone | Listed by Google as a way third-party sources share data with the Google Health app | Google does not publish an equivalent list of what it writes out to Apple Health |
On Android the on-device route is the more durable one, because it does not depend on anyone's cloud credentials. Google's help center says that "for most third-party apps and devices, data can be shared with the Google Health app through Health Connect (Android phones) and Apple Health (iPhones)", and its Health Connect page lists a long set of types Google Health can both read and write, covering fitness, sleep, vitals, body measurements, nutrition and cycle health. If your Android app can read from Health Connect, that path is worth setting up as a backstop even if the direct connection is working today. Our guide to Health Connect with Garmin covers the same permission model in more detail, and the mechanics are identical whichever wearable is writing.
iPhone is where this gets thinner. Google names Apple Health as a way data is shared with the Google Health app, which is inbound. It does not publish a matching list of what Google Health writes out to Apple Health, and Fitbit does not share with Apple Health. Beacon has no direct Fitbit connection, so Fitbit data has no route into Beacon today. So on iPhone, if an app loses the cloud connection, there is no obvious local fallback. Treat that as the version of this change most likely to leave someone with a gap in their history.
What Partner Apps Are Telling Their Users
Google's help center names Apple Watch, Garmin watches and trackers, Samsung Galaxy watches, WHOOP and Oura rings among the devices that connect to the Google Health app, and Strava and MyFitnessPal among the apps. That is the scale of what is being re-plumbed. The useful reading, though, is in the notices individual apps wrote for their own members, because those describe what actually went wrong.
Big Team Challenge documents a live problem rather than a theoretical one: "a known issue on Google's side where synced totals are lower than what appears on your device or inside the Google Health app". That is the failure mode to watch for. Your app looks connected, your steps look plausible, and the number is simply short. A connection status light will not catch it. Comparing one day's total against the Google Health app will.
HealthCheck360 lists what its integration receives after the move: duration, distance, steps, calories, sleep and heart rate in beats per minute. That is a narrower set than Fitbit devices record, and it is a reasonable expectation to carry into any app you reconnect. If your app used to show a metric that is not on a list like that, verify it specifically rather than assuming the whole connection came back intact.
We also looked for a notice from MyFitnessPal, which Google lists as a connected app. Its help center refused our request, so we are not quoting what we could not read.
What To Do Before the End of September
This takes about ten minutes and it is the whole point of the article.
First, list the apps that read your Fitbit data. Most people have more than they remember: a calorie tracker, a training app, an insurance or workplace wellness portal, maybe a sleep app. Second, open each one and look at a number you can verify, such as today's steps or last night's sleep duration, and compare it against the Google Health app. Do not accept a connection indicator as proof.
Third, where the numbers are missing or short, disconnect and reconnect, and at the sign-in screen choose Continue with Google using the same Google account as your Google Health app. Grant the data types you actually want synced — a partial grant is the most common reason one metric comes back and another does not, so if a number is missing, check that its type is permitted rather than granting everything by default. Fourth, if you are on Android, open Health Connect and check which apps have read and write permission for the types you care about, so you have a second path if the cloud connection lapses. Our breakdown of which wearable metrics actually sync is a useful reality check on the gap between what a device records and what it exports.
Finally, if you were already thinking about leaving the platform, this is a reasonable moment to price the alternatives rather than reconnect out of habit. We covered the field in the Fitbit Air alternatives roundup, and Fitbit Air versus Pixel Watch 4 covers what staying inside Google's health stack now looks like.
Where Beacon Fits
Plainly: Fitbit data does not reach Beacon today. Beacon has no direct Fitbit or Google Health connection, and Fitbit data does not write to Apple Health, which is the route Beacon uses for most other devices.
So this API change does not affect Beacon, because there is no Fitbit connection to break. Our integrations page lists what Beacon does connect to: WHOOP, Oura and Withings directly, plus Apple Health.
For the devices it does read, Beacon calculates its own Sleep, Exercise, Diet, Focus and Mindfulness scores from the underlying data and has no readiness or recovery score of its own; Oura's Readiness and Garmin's Body Battery do not appear in Beacon.
FAQ
Is the Fitbit API shutting down?
The legacy one is. Fitbit's own developer site carries a notice reading: 'The Fitbit Web APIs are moving to a new, scalable infrastructure. We will be deprecating the legacy Fitbit Web API in September 2026.' It directs developers to the Google Health API, which Google describes as the next generation of the Fitbit Web API. Fitbit's notice names the month rather than a specific day.
Will my Fitbit still sync with other apps after September 2026?
Only if the app migrated to the Google Health API and you re-authorised it. The change moves authentication from Fitbit to Google's OAuth 2.0 framework, so an older permission does not carry over by itself. Open each app, compare a real number such as today's steps against the Google Health app, and reconnect if it is missing or short.
Do I have to reconnect Fitbit in every app?
Assume yes, and verify rather than trust a status light. Big Team Challenge tells members they must update their connection to Google Health before September 30, 2026, using a Reconnect with Google step. HealthCheck360 describes the account transition itself as automatic. Both are consistent: Google moved your account, but each app's authorisation is separate.
Can apps get Fitbit data through Health Connect instead?
On Android, yes, and it is the more durable route because it does not depend on cloud credentials. Google's help center says most third-party apps and devices share data with the Google Health app through Health Connect on Android and Apple Health on iPhone, and its Health Connect page lists types Google Health can both read and write across fitness, sleep, vitals, body measurements, nutrition and cycle health.
Does Fitbit data reach Apple Health on iPhone?
Not as a route you can rely on. Google lists Apple Health as a way third-party sources share data with the Google Health app, which is data coming in, and it does not publish a matching list of what it writes out. Fitbit does not share with Apple Health, and Beacon has no direct Fitbit connection, so Fitbit data has no route into Beacon today.
How does Fitbit connect to Beacon?
It does not, today. Beacon has no direct Fitbit connection, and Fitbit data lives in Google Health and does not write to Apple Health, so it has no route into Beacon.