> 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/changelog/2024/2024-september-updates.md).

# September Updates 2024

Check out what we've been doing at Terra over the month of September 2024!

## Backend 💾

### Features

* Apple sleeps now provide if if the session is a nap or not via is\_nap field
* Laps data can now be retrieved via Coros workouts
* Move Dexcom to use V3 API
* Compute in bed duration directly in the case this sample is not provided from Apple Health
* Apple Health now supports /athlete endpoint! (providing the unique device ID from Apple health)
* Added default Intensity to Garmin Planned Workouts

### Bug fixes

* Fixed a bug where Fitbit did not return heart rate data in the case workout was small and recorded on Google Pixel watches
* Fixed a bug where samples were provided still even if SAMPLES scope was turned off
* Fixed a bug with Aktiia where not all samples were returned
* Fixed a bug where some samples may be duplicated for Freestylelibre
* Display invalid credentials correctly in Freestylelibre authentication
* Wahoo now returns workout upload type (AUTOMATIC/MANUAL) correctly

## Health Scores

* New scores!
  * Work Capacity score is released!

## Teams API

* Improve metrics schema (making it more interoperable and easy to parse)
* You can now get all integrations detailed for Teams api via the /integrations/detailed endpoint

***

## SDK 📱

### [TerraAndroid](ref:reference-android-sdk)

* Allow for direct aggregation of all Health Connect origins so that you may use Health Connect as a direct source (version 1.5.0 above)

***

## Frontend📺

### Landing Page

* Updated our [Careers](https://tryterra.co/careers) page
* Fixed an issue with blog searches

### Dashboard

* Directly access Colour wheel on Widget Customisation page


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.tryterra.co/changelog/2024/2024-september-updates.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.