Every month we write some updates to our API, SDK, and front-end solutions. Here's March:
🚀 TL;DR:
We've added five new integrations (Decathlon, Strava, Tredict, Cronometer, and PUL), improved standardization for Garmin payloads, and made significant performance upgrades to our system.
Get the latest Terra Research reports and insights every week as soon as they're published.
By continuing, I agree to the Privacy Policy and Terms of Service.
🔌 New Integrations:
What?
We're excited to announce that we've added five new integrations to our platform: Decathlon, Strava, Tredict, Cronometer, and PUL. These integrations allow us to gather more data from various fitness-tracking devices and apps.
Why?
We aim to make it easy for developers to access and use fitness data from various sources. Adding these new integrations expands the range of data accessed through our platform, giving developers more flexibility and options for their applications.
How?
We've added these integrations to our platform and updated our API documentation to include details on accessing the new data streams. Developers can now start using these integrations immediately to access the needed data.
📊 Additional Standardization for Garmin Payloads:
What?
We've made additional standardization updates to our platform to handle Garmin payloads better. Specifically, we send empty payloads if no data is retrieved, consistent with every other provider.
Why?
Garmin payloads are unique in that they are sent asynchronously and in parts, making it difficult to handle compared to other sources. Standardizing how we handle Garmin payloads ensures that our platform behaves consistently across all providers.
How?
We now wait for 2–3 minutes to check if any additional data comes in and then dispatch the payload as a whole, containing all its different elements. This ensures developers receive complete and consistent data from Garmin, just like from other providers.
💻 Massively Increased Performance:
What?
We've made significant internal optimizations to our platform that have led to much better and more efficient processing of requests.
Why?
As our platform grows and more developers use our service, we need to ensure that we can handle heavier workloads without any reduction in performance. Our focus is on scaling our platform to meet the needs of all our customers, no matter how large or small.
How?
We've modulated the way we handle queuing for requests and have implemented a more robust elastic scaling system for heavier workloads. We've upgraded our systems across the board to enable handling whatever is thrown at them. These changes have led to faster processing times and reduced request times, which ultimately means a better developer user experience.
🎉 We're excited about these updates to our platform and hope that they make it even easier for developers to access and use fitness data in their applications.
