Skip to content
AF

Fitbit API Changes & Deadlines Timeline

4 entries · checked against their source pages between October 12, 2026 and November 2, 2026

The changes tracker holds 4 dated entries that name Fitbit Web API (Google): 3 confirmed, where the vendor’s own words are quoted on the linked page, and 1 reported, where the claim comes from notices we could not confirm on an official page. They are listed newest first, each date at the precision its source gives, and each links the page on this site that carries the sourced detail.

Follow Fitbit changes

Fitbit RSS feed →Email alerts for Fitbit →As JSON →Add Fitbit to my stack →

Embed a countdown to the next Fitbit deadline

Free to embed with attribution. The frame counts down on the reader’s clock, says what the date is counted to (the sources give days, not times), and links back to the page that sources it. Preview · Terms

<iframe src="https://aifitnessapi.com/embed/countdown/fitbit"
        title="Next Fitbit API deadline"
        width="100%" height="300" loading="lazy" style="border:0"></iframe>
<p><a href="https://aifitnessapi.com/changes/fitbit">Next Fitbit API deadline</a> via AIFitnessAPI</p>
  1. November 2, 2026confirmed

    Fitbit Web API turn-off moves to November 2, 2026

    Google's Google Health API page, last updated October 23, 2026, now gives November 2, 2026 as the turn-off: "The Fitbit Web API and Fitbit OAuth endpoints will be turned off and will no longer function or sync data to or from Fitbit users. Requests to these endpoints will fail and return an HTTP `410 Gone` status code." When we read the page on October 12 it gave October 30. A 410 from a Fitbit endpoint after that date means the turn-off, not a fault in your integration.

    Fitbit API shutdown center → · checked October 31, 2026

  2. October 29, 2026confirmed

    Thryve deprecates its Fitbit data source

    Thryve's data-sources table marked Fitbit "Deprecating on Oct 29 2026" when we read it in October. When we read it on November 2, 2026 it listed "Fitbit (Deprecated)", with no date, beside Google Health as a separate source with no shared OAuth client. The docs do not say how existing Fitbit connections carry over, so ask Thryve before relying on them.

    Thryve API pricing → · checked November 2, 2026

  3. September 30, 2026confirmed

    Fitbit Web API end of support

    Google's Google Health API page states that on September 30, 2026 "support for the Fitbit Web API ends. The API will continue to operate, but Google will no longer fix bugs or provide API support." The turn-off follows on November 2, 2026. Third-party guides had named September 30 before Google published the timeline; it is the end-of-support date, not the switch-off.

    Fitbit API shutdown center → · checked October 12, 2026

  4. May 2026reported

    Fitbit accounts: Google Account consolidation gate (reported)

    Users on legacy Fitbit-only logins are reported to need consolidation into a Google Account by roughly mid-May 2026. Google's migration guide confirms the gate itself but gives no date: a user must sign in to the Google Health mobile app to link Google Health to their Google Account before an app can sync their data, and calls made before that fail with ACCOUNT_NOT_LINKED. A gate on your migration, not a detail inside it.

    Fitbit API shutdown center → · checked October 12, 2026

Where these entries come from

An entry is on this page when its title or summary on the changes tracker names Fitbit as a whole word, the same rule that lists it on the Fitbit directory entry. A vendor gets a timeline once two entries name it. For everything else on this site about Fitbit, start at Fitbit API Integration Guide.

← Every vendor’s changes and deadlines

Maintained by AIFitnessAPI. Confirm current details in Fitbit’s own documentation before you act on a date.