Fitness API Changes & Deadlines
Updated August 12, 2026 — new entries added as we verify them.
Get the deadlines in your calendar
Subscribe once and every deadline we verify afterwards shows up where you already look. Events with no confirmed day are titled [reported month] and placed on a nominal date for planning only — the calendar carries the same grading this page does.
- December 2026confirmed
Google Fit APIs: end of documented support
Google's own documentation states Fit APIs "will be supported until the end of 2026" (verified against developer.android.com on July 31, 2026). Migration targets differ by integration shape: Health Connect on-device, Health Services on Wear OS, or the Google Health API for server-side reads.
Google Fit shutdown hub → · checked July 31, 2026
- September 2026reported
Fitbit → Google Health side-by-side window reported to close
A window in which the legacy Fitbit Web API and the Google Health API run side by side is reported to extend into late September 2026 — the practical dual-read period for migrating integrations.
Fitbit → Google Health migration playbook → · checked August 11, 2026
- September 2026reported
Fitbit Web API turndown (reported window)
The legacy Fitbit Web API's retirement in favour of the cloud Google Health API is reported to land around September 2026. No official day is confirmed on a page we could verify; some third-party guides name September 30, which is weaker evidence, not stronger. Tokens are reported not to transfer — every user re-consents via Google OAuth.
Fitbit API shutdown center → · checked August 11, 2026
- 2026reported
Strava developer terms: Standard-tier subscription (reported)
Strava's developer access terms reportedly changed during 2026, with Standard-tier developers said to need a paid Strava subscription. The architectural constraints matter more than the fee: athlete data may generally only be displayed back to that athlete, and using it to train AI/ML models is prohibited.
Adapting to Strava API changes → · checked August 12, 2026
- 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, and reportedly cannot use the successor API until they do — a gate on your migration, not a detail inside it.
Fitbit API shutdown center → · checked August 11, 2026
- 2026reported
WHOOP membership restructuring
WHOOP has restructured its membership recently. Because WHOOP requires both a developer membership and an active end-user membership for data to flow, a restructuring moves two columns of the cost model at once — verify current terms before budgeting.
WHOOP API pricing → · checked August 12, 2026
- 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
- 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
- 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
- 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
- 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.
MediaPipe vs MoveNet → · checked August 2, 2026
- 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 Fit shutdown hub → · checked July 31, 2026
- 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
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 → - Garmin developer program sign-ups
Third parties report new partner sign-ups paused at times, with no reopening ETA. Existing partners are unaffected. Verify current status before planning a Garmin integration.
Garmin API approval →
Maintained by AIFitnessAPI. Grading rules live in the repo alongside the data — an entry never states more than the page it links.