Fitness API Changes & Deadlines

1. December 2026confirmed

   Google Fit APIs: end of documented support

   Google's Fit migration guide on developer.android.com (updated September 10, 2026) states "The Google Fit APIs will be supported until the end of 2026" — end of support, with no switch-off date published. It recommends the Google Health API for cloud-based integrations (including the Fit History and Session APIs), Health Connect for step tracking and mobile-first apps, and Health Services on Wear OS, and lists no replacement for the Goals API.

   Google Fit shutdown hub → · checked October 2, 2026

2. November 3, 2026confirmed

   Terra legacy widget endpoint deprecation

   Terra relaunched its connect widget. Its documentation says the older session endpoint, POST https://api.tryterra.co/v2/auth/generateWidgetSession, "keeps working today, with deprecation planned for 3 November 2026", and that "Accounts created after 3 September 2026 cannot use it at all." New sessions are created at POST https://access.tryterra.co/api/widget/session; the response shape (session_id, url, status, expires_in) is unchanged, while the multi-provider and all-providers options are now sent differently.

   How to integrate Terra → · checked October 17, 2026

3. October 30, 2026confirmed

   Fitbit Web API turn-off

   Google's Google Health API page states that on October 30, 2026 "the Fitbit Web API will be turned off and will no longer function or sync data to or from Fitbit users", and that all current integrations "must migrate their applications and users to the Google Health API and Google OAuth 2.0 as soon as possible". Until then the legacy API keeps operating without support, and Google's migration guide has apps support both login methods while it does. Existing tokens cannot be transferred, so every user re-consents through Google OAuth.

   Fitbit API shutdown center → · checked October 12, 2026

4. October 2026confirmed

   Sahha replaces its Free plan with a 30-day free trial

   Sahha's pricing page no longer lists a Free plan. The Internet Archive's capture of 2026-10-17 shows Free at $0 for 30 days, to "Build and test in sandbox" with 25 development users; on 2026-10-22 the page instead offers "Try any plan for 30 days", with "Card required, nothing charged today" and "Cancel before it ends and pay nothing". Starter ($299 a month billed annually, 1,000 users) and Pro ($1,499, 10,000 users) are unchanged. Sahha gives no date for the change, and its homepage FAQ still says to "Start free with 25 development users" in sandbox.

   Sahha API pricing → · checked October 22, 2026

5. October 2026confirmed

   Garmin Connect Personal API and Starter/Enterprise access

   Garmin reorganised its Connect Developer Program and gives no launch date: first seen on 2026-10-22, absent from the 2026-10-17 snapshot. A new Garmin Connect Personal API lets individuals create their own API key on Garmin Connect Web for their own data; Garmin says it "is available for personal use" and "is not intended for commercial applications serving multiple end users". The business program now describes Starter Access and Enterprise Access, its FAQ moved under a new Business section (the old address no longer loads), and the earlier FAQ statement that the program was only for business use is gone.

   Garmin API for personal use → · checked October 22, 2026

6. 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 October 30, 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

7. September 27, 2026confirmed

   This site served HTTP 402 for five days

   From 2026-09-27 (21:38 UTC, the first probe that saw it) until recovery on 2026-10-02, every request to aifitnessapi.com answered HTTP 402 with x-vercel-error: DEPLOYMENT_DISABLED — Vercel had disabled the project's deployments, which is an account and billing state, not a code, build or DNS fault. Googlebot and bingbot got that status on every URL for five days, and a sustained 4xx reads as removal rather than retry. The site serves 200 again on the apex and on www. This entry is about this site rather than a vendor API, and it is here because a tracker that goes dark for five days and does not say so is not a record.

   Site changelog → · checked October 3, 2026

8. September 9, 2026confirmed

   FTC rescinds its 2021 health-app breach policy statement

   The FTC's press release says "The Federal Trade Commission rescinded the 2021 Policy Statement on Breaches by Health Apps and Other Connected Devices", because the Commission's 2024 update to the Health Breach Notification Rule covers "health apps and connected devices like fitness trackers, rendering the policy statement unnecessary." The FTC's rule page dates the release September 9, 2026. The rule itself, 16 CFR part 318, still applies; eCFR's current text lists no amendment after May 30, 2024.

   FTC Health Breach Notification Rule for fitness apps → · checked October 17, 2026

9. 2026confirmed

   Strava developer terms: Standard Tier subscription

   Strava's API Policy makes Standard Tier apps "subject to subscription requirements", including "that the developer or specified end users maintain an active Strava subscription", and its getting-started guide calls a subscription "a prerequisite for creating an app". Access itself is free: the API Agreement (2026), effective June 1, 2026, says it is "currently provided at no charge". The architectural constraints matter more than the fee: Strava data may be shown only to the athlete it belongs to, and the API Policy forbids using it in the development, training, evaluation or operation of any AI application. Graded reported until Strava's own pages were re-read on 2026-10-17.

   Strava API pricing → · checked October 17, 2026

10. 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

11. 2026reported

    WHOOP membership restructuring

    Reported, not confirmed: 2026 press coverage said WHOOP had restructured its membership and upgrade model, and this site's WHOOP pricing page repeated it until the page was re-verified on 2026-10-17. WHOOP's developer pages read for that re-verification do not mention a restructuring. They do say a developer must have a WHOOP membership to build an app and that users connect with their own WHOOP accounts, so a membership change moves two columns of the cost model at once — check WHOOP's current terms before budgeting.

    WHOOP API pricing → · checked October 17, 2026

12. 2026confirmed

    ExerciseDB becomes AscendAPI, with free V1 and V2 tiers

    The exercisedb.dev home page now reads "Previously ExerciseDB" above the name AscendAPI, and AscendAPI's documentation (pages last modified in March 2026) describes two products. ExerciseDB V1 has a free hosted tier of "1,500 exercises with 180p GIFs. No authentication required" at oss.exercisedb.dev, plus a paid RapidAPI tier; ExerciseDB V2, on RapidAPI only, gives each exercise an MP4 video and has a free Basic plan of 2,000 requests a month and 200 exercises, on which "free tier media is watermarked". This site first saw the AscendAPI name on 2026-10-22; neither the rename's date nor the paid prices are published on the pages we could read.

    Exercise database API pricing → · checked October 22, 2026

13. 2026reported

    Nutritionix open free tier reportedly curtailed

    Reports conflict on whether Nutritionix's open free tier still exists; higher tiers route through a Syndigo sales contact. If the free tier is gone, the freemium classification shifts toward sales-gated.

    Nutrition API pricing → · checked August 12, 2026

14. December 2025confirmed

    Oura personal access tokens deprecated

    Oura deprecated personal access tokens in December 2025 — scripts and internal tools built on PATs need the OAuth flow instead. This page's phrasing has been quoted back to us in search queries, a sign assistants cite it.

    Oura PAT deprecation fix → · checked August 2, 2026

15. June 30, 2025reported

    ANT+ membership and certification programs discontinued (reported)

    Per widely-quoted announcements from the ANT+ organization — the official page was unreachable in our research pass, so this stays reported — the ANT+ membership and certification programs were discontinued on June 30, 2025, with certification applications accepted only until March 31, 2025. Device profiles and documentation reportedly remain available and existing devices are unaffected; coverage cites the EU Radio Equipment Directive as a driver. For new fitness apps, BLE is the practical default radio.

    ANT+ vs Bluetooth for fitness sensors → · checked August 14, 2026

16. 2024confirmed

    Strava tightened its developer program

    Strava tightened developer-program rules in 2024 — the start of the stricter display, branding, and access regime its API operates under today.

    Adapting to Strava API changes → · checked August 12, 2026

17. 2024confirmed

    MoveNet: no model updates observed since 2024

    No updates to the MoveNet pose models have been observed since 2024. The single-person models remain Apache-2.0; treat the weights as stable rather than evolving.

    Pose estimation models compared → · checked August 2, 2026

18. May 1, 2024confirmed

    Google Fit: new developer sign-ups closed

    Google closed Google Fit API sign-ups for new developers on May 1, 2024 — the first hard milestone of the Fit sunset. Existing integrations continued to work. Google's documentation stated the date when we checked on July 31, 2026; its current Fit migration guide (updated September 10, 2026) no longer repeats it.

    Google Fit shutdown hub → · checked July 31, 2026

19. April 2023confirmed

    MediaPipe Pose Landmarker weights: last modification

    The served MediaPipe Pose Landmarker .task model files were last modified in April 2023. The framework evolves; the pose weights have not — pin versions and treat model updates as an event, not a stream.

    Pose Landmarker model guide → · checked August 2, 2026

How to read the grades

The label records provenance, not plausibility: a reported item can be very likely true and still be reported. When we graded the entries on September 1, 2026, the confirmed ones were mostly past or documented, something a vendor had already done or committed to in writing, while the reported ones were mostly still ahead and commercial: turndowns, pricing changes, membership requirements. Vendors document what they have done far more reliably than what they are about to do to your costs.

Reported does not mean ignorable. Act on the direction, verify the specific date or number yourself before anything depends on it, and write down which of your assumptions is unsourced. A precise date you cannot trace back to the vendor is weaker evidence than an imprecise one you can, because the precision is presentation rather than sourcing.

The same grading works on your own dependency list. Give each dependency a row with the date or term you are assuming, where it came from and when you last checked it. Vendor documentation, a vendor changelog or a vendor email addressed to you counts as confirmed; a community thread, an aggregator blog, a conference talk or a colleague’s memory counts as reported. Re-check the oldest rows first, and re-plan when an item moves from reported to confirmed, which usually means the vendor finally published.

On watch — undated, not predictions

• Google Health API pricing and quota model

  The Fitbit successor's pricing model is not clearly public. Until it is, the free-to-call classification of the Fitbit ecosystem is the least stable cell in our dataset.

  Fitbit API pricing →
• MoveNet MultiPose licence gap

  The MultiPose model card we read carried no licence line, while the single-person models are Apache-2.0. Confirm independently before shipping multi-person tracking commercially.

  Multi-person pose tracking →