> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/faq/help-topics/data-api-sdk/account-config-environments-and-going-live/google-fit-2026-deprecation.md).

# How does the 2026 Google Fit deprecation affect me?

Terra's **'Google Fit' provider** is implemented via the mobile SDK reading from **Health Connect on-device**, not the deprecated Google Fit REST API, so it is already on the post-2026 path and **requires no migration**.

The piece affected by the 2026 deprecation is the **REST-based 'Google' OAuth provider's fitness scopes**. **Switch fitness data collection to the Google Fit (mobile SDK) provider.** The Google provider remains useful for non-fitness Google data.

See the [mobile SDK docs](https://docs.tryterra.co/health-and-fitness-api/mobile-only-sources).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tryterra.co/faq/help-topics/data-api-sdk/account-config-environments-and-going-live/google-fit-2026-deprecation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.