February updates - Terra API
Get ready for a bunch of new integrations added to Terra's API, starting the new year with a BOOM 💣 💥
tl;dr
- Nolio, Ketomojo, Trainxhale, Lezyne, CyclingAnalytics, EatThisMuch, and LiveRowing are new integrations added to Terra's API.
- A new feature has been added that allows requests that get rate-limited by providers to be retried automatically, currently enabled for Fitbit.
- A beta version, "2022–12–12" has been released that removes the need to handle "user_reauth" payloads, simplifying developers' work by keeping the user_id constant even if the user re-authenticates with a fitness data provider.
Fuel your users' fitness journeys with new integrations! 💪🚴 ♂️
What?
We're thrilled to announce the addition of several new integrations to our platform: Nolio, Ketomojo, Trainxhale, Lezyne, CyclingAnalytics, EatThisMuch, and LiveRowing! 🔌 These integrations will give end users even more options for tracking and analyzing their progress and reaching their fitness goals.
Why?
Our goal has always been to provide our users with the best possible experience; to do so, we need to offer a diverse range of integrations that cater to everyone's needs. 🌈 With these new additions, we can expand our reach further and offer more options for tracking and analyzing workouts across various activities. Whether you're a runner, cyclist, or rower, there's something for everyone in this batch of integrations.
How?
We've been working closely with these companies to build the necessary infrastructure to support these integrations and to integrate their APIs. 🤝 We're constantly looking for ways to improve our offerings and provide our users with the best possible experience, and these new integrations are just the latest step in that direction. Get ready to take your fitness journey to the next level with these exciting new integrations! 💪🏋 ️♂️
Get Data No Matter What! 💪
What?
We're excited to announce a new feature on our platform: retries for rate-limited requests. 💻 This allows requests that are rate-limited by providers to be retried automatically later.
Why?
This is about ensuring that developers get webhooks with updated data as expected, even if Terra's request to a provider is rate-limited. With this new feature, developers will always get data no matter what, even if they hit providers' rate limits. This is because we keep track of data gathered for a given request, and if a rate limit is hit, we send the currently fetched data and retry the request later automatically. 🔌
How?
To implement this feature, we had to create the infrastructure to keep track of data gathered for a given request and determine the timing for retrying requests that get rate-limited. We are starting with Fitbit and plan to expand to more integrations. 🔜 No more waiting for data! 💻 With our new retries for rate-limited requests, you'll always get the data you need when you need it. 💪
New Version! (Beta)
What?
A new beta version, "2022–12–12" has been released, simplifying developers' work by removing the need to handle "user_reauth" payloads. In addition to the above improvements, we aim to add more features to this API version to improve it further. These features will be designed to make the API more user-friendly and efficient while providing developers with the tools to manage their data and integrations better.
Why?
The beta version is designed to simplify developers' work by not requiring them to handle "user_reauth" events. The user_id is now constant even if the user re-authenticates with a given fitness data provider, making it easier for developers to track and manage their data.
How?
This change has been made possible by the user_id only be provided after the user has successfully authenticated. This eliminates the need for developers to store or keep track of the user_id before authentication, making their job simpler and less prone to errors.
Stay tuned for more updates and new features in future releases!
