# January Updates 2023

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

### Integrations

* Nolio
* Ketomojo
* Trainxhale
* Lezyne
* CyclingAnalytics
* EatThisMuch
* LiveRowing

### Features

* Include start and end time to HTTP request headers
* Include step samples for Polar activities
* Fitbit now returns Device data properly
* Laps samples are added to Polar, Suunto and Wahoo
* SPO2 and Respiration data are sent with Fitbit sleep payloads
* Added ECG data for Fitbit and Withings
* Reference IDs are now included in 'deauth' and 'reauth' webhooks
* A new version '2022-12-12' has been released!
  * Does not require you to store the 'user\_id' on '/auth/authenticateUser/' endpoint
  * Removes the need to handle reauth payloads.
* Deleting planned workouts are now based on workout IDs
* Planned workouts now allows you to write steps percentage

### Bug Fix

* Version 2022-03-02 now uses Oura V2 API
* Fixed a bug where Garmin HTTP requests timeout when a request of over 10 years is submitted
* Fixed a bug where WHOOP's sleep data were not sent with correct times
* Fixed a bug where Nutrition data from Cronometer/Nutracheck were not sent in time
* Fixed a bug where 'Chunk'-ing payloads were not sent with the correct payload references.

### [TerraiOS](https://docs.tryterra.co/reference/terra-ios-package) v1.3.0

* New minor version:
  * Includes Error returning in callbacks instead of throwing
  * Terra class is treated as a singleton within the package
  * Rename the Terra class to TerraManager
  * Allow you to request data to the app directly for Apple Health or send to Webhook
  * Dev experience improvements
* Version 2022-03-02 now properly sends Sleep data

### [TerraAndroid](https://docs.tryterra.co/reference/terraandroid-1) v1.3.8

* Fixed a bug where if Health Connect is not installed, 'initConnection' crashes the app.
* Widget now support Polish, Finnish, and Arabic languages
* Login pages now start typing with uncapitalised letters for user experience
* New Capture the Flag challenge
* New Steps challenge


---

# Agent Instructions: 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/changelog/2023/2023-january-updates.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.