--- title: "The Fitness API Graveyard" canonical: "https://aifitnessapi.com/graveyard" markdown: "https://aifitnessapi.com/graveyard.md" type: "record" last_reviewed: "2026-10-31" description: "Shut-down, dying and deprecated fitness and health APIs, from Fitbit and Google Fit to Oura and Strava: end dates, replacements, each vendor's own words." publisher: "AIFitnessAPI — funded by KinesteX; first-party pages disclose it" cite_as: "\"The Fitness API Graveyard\", AIFitnessAPI, https://aifitnessapi.com/graveyard" --- # The Fitness API Graveyard > The Fitness API Graveyard records 15 fitness and health developer APIs, SDKs and endpoints that their vendors have shut down, scheduled to shut down or deprecated: 6 dead, 5 dying with a published end date and 4 deprecated. Each entry quotes the vendor’s own notice, with its end date at the precision the vendor gave and the replacement the vendor names. As of October 31, 2026, the next to go is the Fitbit Web API: Google for Developers gives November 2, 2026 (turn-off). - Canonical: https://aifitnessapi.com/graveyard - Last reviewed: 2026-10-31 - Publisher: AIFitnessAPI (https://aifitnessapi.com) - Cite as: "The Fitness API Graveyard", AIFitnessAPI, https://aifitnessapi.com/graveyard --- 15 APIs, SDKs and endpoints from 9 vendors · sources read October 31, 2026 *[Interactive: the filters, countdowns and share cards, in the browser at https://aifitnessapi.com/graveyard; not reproduced in this mirror.]* ## The graveyard ### Google Fit Sensors API and BLE API | Status | Kind | Vendor | End of support | Replaced by | Checked | |---|---|---|---|---|---| | Dying | API | Google | 2026 | Android Sensors framework or Fused Location Provider (Sensors API); Android Bluetooth APIs (BLE API) | October 31, 2026 | > “The following features don't have a direct API replacement. Use the recommended Android standard APIs:” — [Android Developers](https://developer.android.com/health-and-fitness/health-connect/migration/fit) 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. [Google Fit shutdown hub](https://aifitnessapi.com/google-fit-shutdown) ### Google Fit Goals API | Status | Kind | Vendor | End of support | Replaced by | Checked | |---|---|---|---|---|---| | Dying | API | Google | 2026 | no replacement named by the vendor | October 31, 2026 | > “No replacement API available. Manage goal tracking and daily activity targets within your application logic.” — [Android Developers](https://developer.android.com/health-and-fitness/health-connect/migration/fit) 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. [Google Fit shutdown hub](https://aifitnessapi.com/google-fit-shutdown) ### Google Fit APIs (Android and REST) | Status | Kind | Vendor | End of support | Replaced by | Checked | |---|---|---|---|---|---| | Dying | API | Google | 2026 | [Google Health API (cloud)](https://aifitnessapi.com/google-health-api); [Health Connect (Android)](https://aifitnessapi.com/health-connect) | October 31, 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.” — [Android Developers](https://developer.android.com/health-and-fitness/health-connect/migration/fit) 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.”](https://developers.google.com/fit) [Google Fit shutdown hub](https://aifitnessapi.com/google-fit-shutdown) ### Terra legacy widget session endpoint | Status | Kind | Vendor | Deprecation planned | Replaced by | Checked | |---|---|---|---|---|---| | Dying | Endpoints | Terra | November 3, 2026 | [POST access.tryterra.co/api/widget/session](https://aifitnessapi.com/integrate/terra-api) | October 31, 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.” — [Terra documentation](https://docs.tryterra.co/unified-api/user-authentication/implementation-terra-widget) 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. [How to integrate Terra](https://aifitnessapi.com/integrate/terra-api) ### Fitbit Web API | Status | Kind | Vendor | Turn-off | Replaced by | Checked | |---|---|---|---|---|---| | Dying | API | Google (Fitbit) | November 2, 2026 | [Google Health API](https://aifitnessapi.com/google-health-api) | October 31, 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.” — [Google for Developers](https://developers.google.com/health/about) 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.”](https://developers.google.com/health/about) [Fitbit API shutdown center](https://aifitnessapi.com/fitbit-api-shutdown) ### Strava Club Activities, Club Members and Club Admins endpoints | Status | Kind | Vendor | Removed | Replaced by | Checked | |---|---|---|---|---|---| | Dead | Endpoints | Strava | September 1, 2026 | no replacement named by the vendor | October 31, 2026 | > “Club Activities, Club Members, and Club Admins endpoints removed” — [Strava V3 API changelog](https://developers.strava.com/docs/changelog/) 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”](https://developers.strava.com/docs/changelog/) [How to integrate the Strava API](https://aifitnessapi.com/integrate/strava-api) ### Oura personal access tokens | Status | Kind | Vendor | Deprecated, no longer available | Replaced by | Checked | |---|---|---|---|---|---| | Dead | Auth method | Oura | December 2025 | [OAuth 2.0 API applications](https://aifitnessapi.com/fix/oura-personal-access-token-deprecated) | October 31, 2026 | > “Please note that personal access tokens were deprecated in December 2025 and are no longer available for use.” — [Oura API V2 specification](https://cloud.ouraring.com/v2/static/json/openapi-1.43.json) 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. [Oura personal access token deprecated](https://aifitnessapi.com/fix/oura-personal-access-token-deprecated) ### Samsung Health SDK for Android | Status | Kind | Vendor | Deprecated | Replaced by | Checked | |---|---|---|---|---|---| | Deprecated | SDK | Samsung | July 31, 2025 | [Samsung Health Data SDK](https://aifitnessapi.com/integrate/samsung-health-api) | October 31, 2026 | > “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.” — [Samsung Developer](https://developer.samsung.com/health/android/overview.html) 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. [How to integrate Samsung Health](https://aifitnessapi.com/integrate/samsung-health-api) ### Oura API V1 | Status | Kind | Vendor | Removed | Replaced by | Checked | |---|---|---|---|---|---| | Dead | API | Oura | January 22, 2024 | [Oura API V2](https://aifitnessapi.com/integrate/oura-api) | October 31, 2026 | > “The V1 API was removed on January 22nd, 2024.” — [Oura API documentation](https://cloud.ouraring.com/docs/) The first version of Oura's cloud API. Oura's getting-started page dates its removal and links the V2 documentation. [How to integrate the Oura API](https://aifitnessapi.com/integrate/oura-api) ### MediaPipe Pose (Legacy Solution) | Status | Kind | Vendor | Upgraded to a new solution | Replaced by | Checked | |---|---|---|---|---|---| | Deprecated | SDK | Google | May 10, 2023 | [MediaPipe Pose Landmarker (Tasks API)](https://aifitnessapi.com/motion/mediapipe-pose-landmarker-models) | October 31, 2026 | > “As of May 10, 2023, this solution was upgraded to a new MediaPipe Solution.” — [MediaPipe repository (Google)](https://raw.githubusercontent.com/google-ai-edge/mediapipe/master/docs/solutions/pose.md) 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.”](https://developers.google.com/edge/mediapipe/solutions/guide) Launch: November 10, 2020, [@mediapipe/pose first published to npm](https://registry.npmjs.org/@mediapipe/pose) [MediaPipe Pose Landmarker models](https://aifitnessapi.com/motion/mediapipe-pose-landmarker-models) ### Strava Running Races endpoints | Status | Kind | Vendor | Removed | Replaced by | Checked | |---|---|---|---|---|---| | Dead | Endpoints | Strava | November 1, 2021 | no replacement named by the vendor | October 31, 2026 | > “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.” — [Strava V3 API changelog](https://developers.strava.com/docs/changelog/) 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. [How to integrate the Strava API](https://aifitnessapi.com/integrate/strava-api) ### Moves app and developer API | Status | Kind | Vendor | Shut down | Replaced by | Checked | |---|---|---|---|---|---| | Dead | API | Moves | July 31, 2018 | no replacement named by the vendor | October 31, 2026 | > “As of July 31, 2018, you can no longer log in or use the Moves app.” — [Moves (Internet Archive capture)](https://web.archive.org/web/20181231164810/https://dev.moves-app.com/), captured December 31, 2018 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. ### Google Health (personal health record service) | Status | Kind | Vendor | Retired | Replaced by | Checked | |---|---|---|---|---|---| | Dead | Platform | Google | January 1, 2012 | no replacement named by the vendor | October 31, 2026 | > “Google Health (retiring January 1, 2012; data available for download through January 1, 2013)” — [Official Google Blog (Internet Archive capture)](https://web.archive.org/web/20120107124413/http://googleblog.blogspot.com/2011/06/update-on-google-health-and-google.html), captured January 7, 2012 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.”](https://web.archive.org/web/20130111034326/http://www.google.com/intl/en_us/health/about/) ### WHOOP API v1 | Status | Kind | Vendor | No longer supported | Replaced by | Checked | |---|---|---|---|---|---| | Deprecated | API | WHOOP | no date given | [WHOOP API v2](https://aifitnessapi.com/integrate/whoop-api) | October 31, 2026 | > “The v1 API is no longer supported and any new features or functionality will be added to v2 only.” — [WHOOP Developer Platform](https://developer.whoop.com/docs/developing/v1-v2-migration/) 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. [How to integrate the WHOOP API](https://aifitnessapi.com/integrate/whoop-api) ### PoseNet for TensorFlow.js (@tensorflow-models/posenet) | Status | Kind | Vendor | Deprecated | Replaced by | Checked | |---|---|---|---|---|---| | Deprecated | Model package | Google (TensorFlow.js) | no date given | [@tensorflow-models/pose-detection](https://aifitnessapi.com/motion/movenet-models) | October 31, 2026 | > “This package is deprecated in favor of the new pose-detection package.” — [tfjs-models repository (TensorFlow)](https://raw.githubusercontent.com/tensorflow/tfjs-models/master/posenet/README.md) 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. Launch: May 7, 2018, [@tensorflow-models/posenet first published to npm](https://registry.npmjs.org/@tensorflow-models/posenet) ## 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](https://aifitnessapi.com/changes). The two deadlines most readers arrive for have their own pages: [the Fitbit Web API turn-off](https://aifitnessapi.com/fitbit-api-shutdown) and [the Google Fit end of support](https://aifitnessapi.com/google-fit-shutdown). ## 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](https://aifitnessapi.com/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](https://aifitnessapi.com/embed/graveyard). Other widgets: [embeds & badges](https://aifitnessapi.com/badges). ## 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. [Permalink](https://aifitnessapi.com/graveyard#faq-1) ### 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. [Permalink](https://aifitnessapi.com/graveyard#faq-2) ### 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. [Permalink](https://aifitnessapi.com/graveyard#faq-3) ### 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. [Permalink](https://aifitnessapi.com/graveyard#faq-4) ## Related - [Fitness API changes & deadlines tracker](https://aifitnessapi.com/changes) - [Fitbit API shutdown: what's confirmed](https://aifitnessapi.com/fitbit-api-shutdown) - [Google Fit shutdown: timeline and paths](https://aifitnessapi.com/google-fit-shutdown) - [Migrate off a deprecated fitness API](https://aifitnessapi.com/migrate/migrate-off-a-deprecated-fitness-api) 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: - [The Best Fitbit API Alternatives (2026)](https://aifitnessapi.com/alternatives/fitbit-api-alternatives) - [Google Fit API Alternatives (It's Deprecated) (2026)](https://aifitnessapi.com/alternatives/google-fit-api-alternatives) - [The Best Wearable Fitness & Health-Data APIs (2026)](https://aifitnessapi.com/fitness-apis/wearable-data-apis)