Fitbit Web API shutdown (October 2026)

Google turns the Fitbit Web API off on 30 October 2026: the dates, the Google Health API and Health Connect paths, and a migration checklist.

Google is turning off the legacy Fitbit Web API on 30 October 2026; support already ended on 30 September 2026, and apps that still use it will stop receiving Fitbit data after the turn-off. The successor is the Google Health API, which uses Google OAuth 2.0 and covers Fitbit devices and Google Pixel watches; all of its scopes are restricted, so access needs Google's privacy and security review. This page lays out the dates, the two migration paths and how to keep the data in a standard format once it arrives.

Dates, from Google

The Fitbit Web API shutdown

Until 30 Sep 2026Fitbit Web API supported
30 Sep 2026Support ends: no fixes, no help
30 Oct 2026API turned off: no data, no sync
Google Health APIThe successor: Google OAuth 2.0, restricted scopes
Or the phoneFitbit data through Health Connect, read by your app

Source: Google's About the Google Health API page, October 2026.

Two ways to keep Fitbit data flowing

	Google Health API (cloud)	Health Connect (on the phone)
Where the data comes from	Google's servers	The person's Android phone, where the Fitbit app writes it
Access	Google OAuth 2.0, restricted scopes, privacy and security review	Health Connect permissions granted by the person in your app
Devices	Fitbit devices and Google Pixel watches	Any device whose app writes to Health Connect (Fitbit, Pixel Watch, Garmin, Oura, Withings…)
iPhone users	Yes, through the cloud	No — on iPhone, read Apple HealthKit instead
Users must reconnect	Yes: legacy Fitbit tokens move to Google OAuth	No cloud account link needed
Best for	Server-to-server sync, web apps	Mobile apps that already ask for Health Connect permission

Either way, store the readings once, in a vendor-neutral format, so the next API change does not reach your database: steps, heart rate, sleep and SpO₂ as LOINC-coded FHIR Observations. Health tracker API shows the codes and requests.

Migration checklist

List what you read today: data types, intraday or daily, and which users.
Apply for Google Health API access early: restricted scopes need a review, and the deadline is fixed.
Plan re-consent: every user must authorise again with Google OAuth.
Map data types to the new API, and expect overlapping records when a phone and a watch both count steps.
Consider Health Connect for Android users if a cloud integration is not essential.
Keep a vendor-neutral store so dashboards, analytics and AI features do not depend on one vendor's API.

Frequently asked questions

When does the Fitbit Web API shut down?

Google ends support on 30 September 2026 and turns the API off on 30 October 2026, according to its Google Health API documentation.

What replaces the Fitbit Web API?

The Google Health API, with Google OAuth 2.0. It covers all Fitbit devices and Google Pixel watches; all scopes are restricted and require a privacy and security review.

Can I still get Fitbit data without the Google Health API?

On Android, yes: the Fitbit app can write to Health Connect, and your app reads it there with the person's permission.

Does Anpheros connect to Fitbit?

No direct connection. Your app reads Fitbit data from Health Connect or the Google Health API and writes it to Anpheros as FHIR Observations, where it is stored with consent, provenance and history.