How much notice fitness API shutdowns gave
Announcement pages read Nov 6, 2026 · 15 rows in the dataset · every figure recomputed from it at each build
3 of 15
graveyard entries with a dated vendor announcement and an end date to the day
92 days
median notice between announcement and end
31 to 191 days
shortest and longest notice measured
Method
Every entry of the Fitness API Graveyard, 15 in all, is one row. The end date, its precision and the vendor's quote for it are the graveyard's own.
The announcement date is the day the vendor published the notice, and it is recorded only where a vendor page read on Nov 6, 2026 dates it: a changelog entry or a timestamped post, with the quote. A date when sign-ups closed, a capture date in the Internet Archive or press coverage does not count. The changes tracker's 22 entries were searched too; they date the events themselves, not when they were announced.
Notice is the number of whole days from announcement to end, computed only when both are dates to the day. Every other entry is listed with the reason it is left out and what its pages do say.
Notice measured
Days from the vendor's dated announcement to the end it announced, for the 3 entries where both are dates to the day.
| Entry | Vendor | Announced | End | Notice | How the announcement is dated |
|---|---|---|---|---|---|
| Strava Running Races endpoints | Strava | Oct 1, 2021 | Nov 1, 2021 | 31 days | Strava's changelog lists the deprecation, with both dates, under its entry of October 1st, 2021. |
| Strava Club Activities, Club Members and Club Admins endpoints | Strava | Jun 1, 2026 | Sep 1, 2026 | 92 days | Strava's changelog lists the removal under its entry of June 1, 2026. |
| Google Health (personal health record service) | Jun 24, 2011 | Jan 1, 2012 | 191 days | Google's blog post giving the retirement date is timestamped 6/24/2011 (Internet Archive capture of January 7, 2012). |
Entries left out
The 12 entries left out, with the reason and what the pages read say instead.
| Entry | Vendor | End | Reason | What the pages say |
|---|---|---|---|---|
| Fitbit Web API | Google (Fitbit) | Nov 2, 2026 | no dated announcement on the pages read | Google's Google Health API page, read 2026-11-06, gives the end of support (September 30, 2026) and the turn-off (November 2, 2026) but no date for when either was announced. |
| Terra legacy widget session endpoint | Terra | Nov 3, 2026 | no dated announcement on the pages read | Terra's widget documentation, read 2026-11-06, gives the planned deprecation date and a 3 September 2026 cut-off for new accounts, but not when the deprecation was announced. |
| Google Fit APIs (Android and REST) | 2026 | end date given only as a year | Google's Fit page, read 2026-11-06, says the APIs will be deprecated in 2026; its May 1, 2024 date is when new sign-ups closed, not an announcement. | |
| Google Fit Goals API | 2026 | end date given only as a year | Google's migration guide lists it among the features with no replacement and dates the end only to 2026. | |
| Google Fit Sensors API and BLE API | 2026 | end date given only as a year | Google's migration guide lists both among the features with no direct replacement and dates the end only to 2026. | |
| Samsung Health SDK for Android | Samsung | Jul 31, 2025 | no dated announcement on the pages read | Samsung's overview page, read 2026-11-06, dates the deprecation, not its announcement. |
| Oura API V1 | Oura | Jan 22, 2024 | no dated announcement on the pages read | Oura's API V1 page, read 2026-11-06, dates the removal, not its announcement. |
| Oura personal access tokens | Oura | Dec 2025 | no dated announcement on the pages read | Oura's API specification, as quoted in the graveyard, dates the deprecation to December 2025 and gives no announcement date. |
| WHOOP API v1 | WHOOP | none given | no end date | WHOOP's migration guide says v1 is no longer supported and gives no date. |
| MediaPipe Pose (Legacy Solution) | May 10, 2023 | no dated announcement on the pages read | Google's legacy-solution page and solutions guide, as quoted in the graveyard, date the upgrade and the end of support, not an announcement. | |
| PoseNet for TensorFlow.js (@tensorflow-models/posenet) | Google (TensorFlow.js) | none given | no end date | The package README says it is deprecated and gives no date. |
| Moves app and developer API | Moves | Jul 31, 2018 | no dated announcement on the pages read | The Internet Archive capture of the Moves developer site, read 2026-11-06, records the shutdown, not when it was announced. |
What this method cannot see
- Vendors rarely date their own notices on the page that carries them, and the pages read here are the ones the graveyard quotes. A notice sent by email or posted on a page not read here is missed, so a missing announcement means not found, not none given.
- A shutdown the graveyard does not record is not in this study, and the graveyard records only shutdowns whose notice it could read on a vendor page.
- 3 measured cases from different years and vendors are a list, not a sample, and the median of so few says little about the next shutdown.
Download the data
The rows behind every figure on this page, CC BY 4.0: fitness-api-shutdown-notice-2026.json, fitness-api-shutdown-notice-2026.csv and the dataset card that describes every column. All of this site’s datasets are on the open datasets page.
How to cite
Quote a figure with the date its data was read and link this page; each headline figure has its own anchor, such as https://aifitnessapi.com/research/shutdown-notice#notice-measured.
AIFitnessAPI. "How much notice fitness API shutdowns gave." Data as of 2026-11-06. https://aifitnessapi.com/research/shutdown-notice
@misc{aifitnessapi-research-shutdown-notice,
author = {{AIFitnessAPI}},
title = {How much notice fitness API shutdowns gave},
year = {2026},
url = {https://aifitnessapi.com/research/shutdown-notice},
urldate = {2026-11-06},
note = {Data as of 2026-11-06}
}More citable counts about this site and the ecosystem it tracks are on the press page.
Frequently asked questions
How much notice do fitness API shutdowns give?
Where this site could date both ends, Strava Running Races endpoints: 31 days; Strava Club Activities, Club Members and Club Admins endpoints: 92 days; Google Health (personal health record service): 191 days. That is 3 of the 15 graveyard entries; the rest could not be measured.
Why is the Fitbit Web API turn-off not counted in the notice figures?
Google's Google Health API page, read 2026-11-06, gives the end of support (September 30, 2026) and the turn-off (November 2, 2026) but no date for when either was announced. Its row is listed with the reason: no dated announcement on the pages read.
Which graveyard entries were left out of the notice figures, and why?
12 of 15: 7 have no dated announcement on the pages read, 3 give the end date only as a year and 2 have no end date. Each excluded row in the dataset says what the pages read state instead.
Does the changes tracker record when a shutdown was announced?
No. Its 22 entries date the events themselves, such as an end of support or a turn-off, so they give the end of a notice period but not its start.