The Fitness API Graveyard
15 APIs, SDKs and endpoints from 9 vendors · sources read October 31, 2026
The graveyard
Showing 15 of 15
- DyingAPI
Google Fit APIs (Android and REST)
Google
? – 2026
End of support: 2026
“The Google Fit API (including the REST API) will only be supported until the end of 2026. We recommend migrating to the Google Health API for cloud-based integrations or Health Connect for step tracking and mobile-first apps.”
Google's Fit platform APIs, including the REST API. Google gives an end of support, not a switch-off day, and recommends the Google Health API for cloud integrations and Health Connect for step tracking and mobile-first apps.
- May 1, 2024 · New developer sign-ups closed: “As of May 1, 2024, developers cannot sign up to use these APIs.”
Replaced by: Google Health API (cloud); Health Connect (Android)
Checked October 31, 2026 · Google Fit shutdown hub - DyingAPI
Google Fit Goals API
Google
? – 2026
End of support: 2026
“No replacement API available. Manage goal tracking and daily activity targets within your application logic.”
The Fit API for the step and heart-point goals users set in the Google Fit app. Google's migration guide lists it among the features with no direct replacement, so goal tracking moves into your own app's logic.
Replaced by: no replacement named by the vendor
Checked October 31, 2026 · Google Fit shutdown hub - DyingAPI
Google Fit Sensors API and BLE API
Google
? – 2026
End of support: 2026
“The following features don't have a direct API replacement. Use the recommended Android standard APIs:”
Fit's real-time raw sensor API and its Bluetooth Low Energy sensor API. Google lists both as deprecated features with no direct API replacement and points to the standard Android APIs instead.
Replaced by: Android Sensors framework or Fused Location Provider (Sensors API); Android Bluetooth APIs (BLE API)
Checked October 31, 2026 · Google Fit shutdown hub - DyingEndpoints
Terra legacy widget session endpoint
Terra
? – 2026
Deprecation planned: November 3, 2026
“Existing integrations keep working today, and the legacy endpoint is planned for deprecation on 3 November 2026. Accounts created after 3 September 2026 cannot use it at all.”
POST /auth/generateWidgetSession, the older way to open Terra's connect widget. Terra's documentation says existing integrations keep working until the planned deprecation, and that newer accounts cannot use it at all.
Replaced by: POST access.tryterra.co/api/widget/session
Checked October 31, 2026 · How to integrate Terra - DyingAPI
Fitbit Web API
Google (Fitbit)
? – 2026
Turn-off: November 2, 2026
“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.”
The legacy Fitbit Web API and the Fitbit OAuth endpoints. Google says requests fail with HTTP 410 Gone after the turn-off, and that integrations must move their users to the Google Health API and Google OAuth 2.0.
- September 30, 2026 · End of support: “Support for the Fitbit Web API ends. The API will continue to operate, but Google will no longer fix bugs or provide API support.”
Replaced by: Google Health API
Checked October 31, 2026 · Fitbit API shutdown center - DeadEndpoints
Strava Club Activities, Club Members and Club Admins endpoints
Strava
? – 2026
Removed: September 1, 2026
“Club Activities, Club Members, and Club Admins endpoints removed”
Three club endpoints of Strava's V3 API. Strava's changelog announced the removal on June 1, 2026 and records it under September 1, 2026, without naming a replacement.
- June 1, 2026 · Removal announced: “Club Activities, Club Members, and Club Admins endpoints will be removed on September 1, 2026”
Replaced by: no replacement named by the vendor
Checked October 31, 2026 · How to integrate the Strava API - DeadAuth method
Oura personal access tokens
Oura
? – 2025
Deprecated, no longer available: December 2025
“Please note that personal access tokens were deprecated in December 2025 and are no longer available for use.”
Single-account tokens for reading your own Oura data from a script. Oura's API specification says they can no longer be used, which leaves the OAuth 2.0 flow for every integration.
Replaced by: OAuth 2.0 API applications
Checked October 31, 2026 · Oura personal access token deprecated - DeprecatedSDK
Samsung Health SDK for Android
Samsung
? – 2025
Deprecated: July 31, 2025
“Samsung Health SDK for Android has been depricated as of 31 July, 2025. Please use Samsung Health Data SDK to access Samsung Health data to integrate with Samsung Health.”
The partner SDK for sharing data between Samsung Health on Android phones and third-party apps. Samsung's overview page says it is deprecated and points to the Samsung Health Data SDK. The misspelling in the quote is Samsung's.
Replaced by: Samsung Health Data SDK
Checked October 31, 2026 · How to integrate Samsung Health - DeadAPI
Oura API V1
Oura
? – 2024
Removed: January 22, 2024
“The V1 API was removed on January 22nd, 2024.”
The first version of Oura's cloud API. Oura's getting-started page dates its removal and links the V2 documentation.
Replaced by: Oura API V2
Checked October 31, 2026 · How to integrate the Oura API - DeprecatedSDK
MediaPipe Pose (Legacy Solution)
Google
2020 – 2023
Upgraded to a new solution: May 10, 2023
“As of May 10, 2023, this solution was upgraded to a new MediaPipe Solution.”
The original MediaPipe Pose solution (mp.solutions.pose and the @mediapipe/pose web package). Google upgraded it to Pose Landmarker; its legacy-solutions guide says the code and prebuilt binaries stay available on an as-is basis.
- March 1, 2023 · Support ended for the listed legacy solutions: “We have ended support for the MediaPipe Legacy Solutions listed here as of March 1, 2023.”
Replaced by: MediaPipe Pose Landmarker (Tasks API)
Launch: November 10, 2020, @mediapipe/pose first published to npm
Checked October 31, 2026 · MediaPipe Pose Landmarker models - DeadEndpoints
Strava Running Races endpoints
Strava
? – 2021
Removed: November 1, 2021
“The get running race and list races endpoints will start to return empty values starting October 15th, 2021, and will be removed completely by November 1st, 2021.”
The get running race and list races endpoints of Strava's V3 API. The changelog entry of October 1, 2021 set the empty-response and removal dates and named no replacement.
Replaced by: no replacement named by the vendor
Checked October 31, 2026 · How to integrate the Strava API - DeadAPI
Moves app and developer API
Moves
? – 2018
Shut down: July 31, 2018
“As of July 31, 2018, you can no longer log in or use the Moves app.”
The Moves activity-tracking app and its developer site, dev.moves-app.com. By December 31, 2018 the Internet Archive's capture of the developer site shows only this notice.
Replaced by: no replacement named by the vendor
Checked October 31, 2026 - DeadPlatform
Google Health (personal health record service)
Google
? – 2012
Retired: January 1, 2012
“Google Health (retiring January 1, 2012; data available for download through January 1, 2013)”
Google's earlier personal health record service, not the Google Health API that replaces the Fitbit Web API. Google's blog post of June 24, 2011 gave the retirement date and a year of data downloads; its help page later said the data was being deleted from January 2, 2013.
- January 2, 2013 · Remaining data deleted: “All Google Health user accounts have been deactivated, and all data stored in them is being systematically deleted from Google’s systems starting on January 2, 2013.”
Replaced by: no replacement named by the vendor
Checked October 31, 2026 - DeprecatedModel package
PoseNet for TensorFlow.js (@tensorflow-models/posenet)
Google (TensorFlow.js)
2018 – …
Deprecated: no date given
“This package is deprecated in favor of the new pose-detection package.”
The PoseNet browser pose model package. Its README says it is deprecated in favor of the pose-detection package and gives no date; the last version on npm, 2.2.2, was published on March 10, 2021.
Replaced by: @tensorflow-models/pose-detection
Launch: May 7, 2018, @tensorflow-models/posenet first published to npm
Checked October 31, 2026 - DeprecatedAPI
WHOOP API v1
WHOOP
? – …
No longer supported: no date given
“The v1 API is no longer supported and any new features or functionality will be added to v2 only.”
Version 1 of the WHOOP Developer API and its integer-ID webhooks. WHOOP's migration guide says v1 is no longer supported and gives no date for switching it off.
Replaced by: WHOOP API v2
Checked October 31, 2026 · How to integrate the WHOOP API
How an API gets a stone
The vendor’s words or nothing. Every entry quotes a passage from the vendor’s own documentation, changelog, specification or blog, read on the date the stone shows. Where the vendor has taken its notice down, the source is an Internet Archive capture of the vendor’s page, with the capture date. Shutdowns we know of but could not read on a vendor page this way are not here yet; press coverage is not a source.
Dates are never sharpened. “Until the end of 2026” is recorded as 2026, and its countdown says it counts to the end of the year. Launch dates appear only where a primary record dates them, such as a package’s first publication on npm; otherwise the stone shows a question mark.
Endpoints count. A removed endpoint breaks an integration as surely as a removed API, so Strava’s retired endpoints sit beside whole platforms. Symbol-level deprecations inside a live SDK, such as renamed HealthKit identifiers, are left to the reference pages.
Dated changes that are not endings, such as pricing and terms changes, are on the changes and deadlines tracker. The two deadlines most readers arrive for have their own pages: the Fitbit Web API turn-off and the Google Fit end of support.
Download the data
Every entry, with its status, dates, replacement, source URL, check date and quote, as one JSON file written at each build: graveyard/data.json. Our fields are free to reuse with a link to this page; the quoted passages belong to their publishers.
Embed the graveyard
A compact list for your own article or docs, without the site chrome, with each entry’s status, end date and replacement and a link back here. It shows the graveyard as it stands when your reader opens it. Preview the widget. Other widgets: embeds & badges.
<iframe src="https://aifitnessapi.com/embed/graveyard"
title="The Fitness API Graveyard"
width="100%" height="640" loading="lazy" style="border:0"></iframe>Or one stone as a live countdown to its end date, with the vendor’s sentence under the count:
Embed a countdown: Fitbit Web API
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-web-api"
title="Fitbit Web API: countdown"
width="100%" height="300" loading="lazy" style="border:0"></iframe>
<p><a href="https://aifitnessapi.com/fitbit-api-shutdown">Fitbit Web API: countdown</a> via AIFitnessAPI</p>Embed a countdown: Terra legacy widget session endpoint
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/terra-legacy-widget-session"
title="Terra legacy widget session endpoint: countdown"
width="100%" height="300" loading="lazy" style="border:0"></iframe>
<p><a href="https://aifitnessapi.com/integrate/terra-api">Terra legacy widget session endpoint: countdown</a> via AIFitnessAPI</p>Embed a countdown: Google Fit APIs (Android and REST)
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/google-fit-apis"
title="Google Fit APIs (Android and REST): countdown"
width="100%" height="300" loading="lazy" style="border:0"></iframe>
<p><a href="https://aifitnessapi.com/google-fit-shutdown">Google Fit APIs (Android and REST): countdown</a> via AIFitnessAPI</p>Embed a countdown: Google Fit Goals API
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/google-fit-goals-api"
title="Google Fit Goals API: countdown"
width="100%" height="300" loading="lazy" style="border:0"></iframe>
<p><a href="https://aifitnessapi.com/google-fit-shutdown">Google Fit Goals API: countdown</a> via AIFitnessAPI</p>Embed a countdown: Google Fit Sensors API and BLE API
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/google-fit-sensors-ble-apis"
title="Google Fit Sensors API and BLE API: countdown"
width="100%" height="300" loading="lazy" style="border:0"></iframe>
<p><a href="https://aifitnessapi.com/google-fit-shutdown">Google Fit Sensors API and BLE API: countdown</a> via AIFitnessAPI</p>Embed a countdown: Strava Club Activities, Club Members and Club Admins endpoints
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/strava-club-endpoints"
title="Strava Club Activities, Club Members and Club Admins endpoints: countdown"
width="100%" height="300" loading="lazy" style="border:0"></iframe>
<p><a href="https://aifitnessapi.com/integrate/strava-api">Strava Club Activities, Club Members and Club Admins endpoints: countdown</a> via AIFitnessAPI</p>Embed a countdown: Samsung Health SDK for Android
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/samsung-health-sdk-android"
title="Samsung Health SDK for Android: countdown"
width="100%" height="300" loading="lazy" style="border:0"></iframe>
<p><a href="https://aifitnessapi.com/integrate/samsung-health-api">Samsung Health SDK for Android: countdown</a> via AIFitnessAPI</p>Embed a countdown: Oura personal access tokens
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/oura-personal-access-tokens"
title="Oura personal access tokens: countdown"
width="100%" height="300" loading="lazy" style="border:0"></iframe>
<p><a href="https://aifitnessapi.com/fix/oura-personal-access-token-deprecated">Oura personal access tokens: countdown</a> via AIFitnessAPI</p>Frequently asked questions
What do dead, dying and deprecated mean in the Fitness API Graveyard?
Each entry takes the state its vendor's own notice states. Dead: the vendor says it was removed, turned off or can no longer be used (6 entries). Dying: the vendor names a future end date, and the entry shows a countdown to it (5). Deprecated: the vendor says it is deprecated or unsupported but names no end, or it keeps running as-is (4). A dying entry whose date has passed fails this site's build until someone re-reads the source and moves it.
Which fitness and health APIs are ending without a replacement?
In the graveyard as of October 31, 2026, the vendor names no replacement for 5: Google Fit Goals API; Strava Club Activities, Club Members and Club Admins endpoints; Strava Running Races endpoints; Moves app and developer API; Google Health (personal health record service). For Google Fit's Goals API, Google's migration guide says to manage goal tracking within your own application logic.
Where do the Fitness API Graveyard's dates come from?
From the vendor's own page, quoted on each entry: documentation, changelogs, specifications and blog posts, or an Internet Archive capture of that page when the vendor has taken it down. Every entry records the day the source was read. Dates keep the source's precision, so an end the vendor gives only as a year stays a year, and 2 entries say no date was given. Events we could not read on a vendor page are left out rather than taken from press coverage.
Can I embed the Fitness API Graveyard or download its data?
Yes. https://aifitnessapi.com/embed/graveyard is a compact widget for an iframe, with a link back to the page, and https://aifitnessapi.com/graveyard/data.json has every entry as JSON with its source URL, check date and quote, regenerated at each build. Each entry also has a share button that copies a text summary or draws a PNG card in your browser.
Related
By AIFitnessAPI. Product and company names are trademarks of their respective owners; quoted passages are the publishers’ own words, reproduced to attribute each date. Vendors change their notices: check the linked source before you plan around a date.
Next step
Turning this into a choice of API: