> 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/provider-coverage-and-per-provider-data-availability/garmin-daily-fields-null-on-other-payloads.md).

# Why are Garmin daily fields like respiration and VO2 max null?

**Many fields that look null on the Garmin daily payload are actually delivered, just on the sleep or body payload rather than the daily envelope.**

* Garmin reports respiration only tied to sleep sessions, so `respiration_data.breaths_data` arrives on the **sleep payload**.
* The Garmin sleep score is at `scores.sleep` on the **sleep payload**. The daily summary carries no score.
* Some slots stay null because Garmin does not provide them at all (for example `resting_breaths_per_min`).
* Terra-derived fields like `data_enrichment` scores are separate and may not be populated for Garmin.

Check the sleep and body payloads for these metrics rather than the daily one. Field locations are listed in the [data models reference](https://docs.tryterra.co/reference/health-and-fitness-api/data-models).


---

# 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/provider-coverage-and-per-provider-data-availability/garmin-daily-fields-null-on-other-payloads.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.