An Update on TrainingPeaks Partner API
As technology enhances how endurance athletes train and prepare for events, TrainingPeaks must adapt and evolve as the technology landscape changes. When TrainingPeaks launched 17 years ago, very few athletes made an effort to save their workouts, let alone took the additional time to upload their data to our web application. With more than 40 million workout files uploaded last year alone, it’s clear that times have changed. The use of GPS sports watches and even our phones for uploading data to the cloud is now seamless, and has become second nature for most athletes.
TrainingPeaks was one of the first fitness platforms to allow syncing of athlete data with third party applications and devices. Our initial strategy (circa 2005) was to have an open API (Application Programing Interface), which didn’t even require registration, and allowed any developer to leverage data on behalf of athletes. As the usage of our API grew, there were adverse affects of this decision as we had no control over who was accessing our API, or how much data they were reading or writing. Over time, we realized that we needed to modernize our API, which led to the decision to start over using current best practices. We began this work more than two years ago, and have been working closely with our partners to switch over to our new API. For most of you this work has been transparent, but we realize that for some of you this has been disruptive. Most applications that were using our API provided value to our coaches and athletes, while some did not and were not given access to our new API.
Looking forward we will continue to work with both existing and new partners to expand the capabilities of our API. We are not creating a closed system, instead we are being selective in our partnerships. This is to ensure a value-driven ecosystem of high-quality applications that provide additional value to athlete training data.
We have gained great traction with this new approach as witnessed by partners such as Garmin, Polar, MyFitnessPal, HRV4Training, FitnessSyncer and others, and we have many new projects in the works.
Some of the features of our new API will allow the following uses:
Uploading device files
Accessing an athlete’s daily workouts and the associated structured workout files
Reading limited workout summary data for an athlete
Access to our new API will require an application process, which will be made available later this year. In the meantime, if you are a developer of a commercial fitness application or device, more information on our partner API can be found here.
We are currently looking for a software developer to join our API team. If you or someone you know is interested, a complete list of all our open positions can be found here.
We understand that this new approach has caused some disruption for many developers, but we believe this will provide a stronger ecosystem for our customers and partners moving forward.
Co-Founder, President, Chief of Fitness Brands