September updates
Summer holidays? More like summer worky-days 🥳 no time for a break when wearables are constantly evolving! Here's yet some more exciting updates we've been pushing out over August.
tl; dr:
New integrations, new user-facing Graph API, and ability to write workouts & workout plans
New integrations!
What?
Huawei is in 😍 and Oura API V2 has also arrived!
We're giving access to new data fields for Oura, and a huge player in the Chinese market for wearables
Why?
Popular demand! After asking for what devs wanted on our Discord server, we heard a lot of demand for this provider. It made sense to add Huawei which owns an important market share in its field, and now that Oura's V2 API is fully out, we can fully support it
How?
We've been wanting to add Huawei in for a little while now, but needed to formalize our partnership process with them in order to be able to move forward. Now that we've made internal changes on our end, and solidified the structure of creating keys on Huawei's end for this integration, we were ready to move forward!
In the meantime, as Oura developed their V2 API, we'd been dying to get our hands on it. We helped throughout the development process by beta testing it and providing them with feedback, and were now ready to provide full support for it and release its new data points to you all!
Graphs API beta
What?
A whole new API made to generate user-facing graphs to display within your app. We've made it even easier to showcase the power of the Terra API by providing an interface to showcase user healthmetrics with minimal effort.
Why?
Popular demand of course(wow this seems to be a recurring factor here 👀 )
We want to make developer experience as easy as possible. This means simplifying each step of the process of using wearable data. At the core, access to the raw data itself is the focal point of what we do; beyond that, we are looking to expand further into a dev's workflow and simplify later stages of the development process of a health & fitness app.
How?
We've made creating a polished user-facing graph one single API call away. All that needs to be done is to request a token, and pull up an iframe using that token with the requested data type. Alternatively, all this functionality is also available in a React wrapper 😍
Writing workouts back!
What?
A couple months ago we introduced writing back data to Fitbit's nutrition endpoint. We've now gone ahead and implemented writing detailed workouts to Wahoo, and workout plans to Garmin. Stay tuned for next month's updates, when we will be doing the same thing for Zwift!
Why?
We're always looking for ways to expand our interaction with the data providers we work with, and writing data back is a new dimension in which we are taking Terra's influence to the next level. A two-way connection is something we've heard time and again since starting our API, and we're making this a reality with the aforementioned updates.
How?
We've needed to perform a reverse-mapping of our data models back into the providers' formats. This requires us to encode our own FIT files from the data passed into our API, and upload these to Wahoo's cloud. For Garmin, this required us to implement a new data structure for planned workouts. Our current activity endpoint makes sense for performed workouts, but not for workout plans, so we had to adapt.
