> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/help-center/help-topics/data-api-sdk/provider-coverage-and-per-provider-data-availability/trainingpeaks-premium-account-requirements.md).

# What does TrainingPeaks need a premium account for?

TrainingPeaks limits basic athletes to activity summaries, so detailed workout metrics, daily, body and sleep data, and future planned workouts need the athlete on a premium TrainingPeaks account.

**TrainingPeaks limits what its API returns for basic athletes, so most data beyond the activity summary needs the athlete on a premium TrainingPeaks account.**

On a basic account, activities still arrive with their type, start time, duration and distance. The following need premium:

* **Workout metrics** such as heart rate, power, cadence, calories, elevation and TSS. TrainingPeaks returns these as empty for basic athletes.
* **Per-workout detail**, including heart rate, power, cadence and position samples.
* **Daily, body and sleep data**, which come from TrainingPeaks metrics.
* **Planned workouts for a future date.** TrainingPeaks rejects these for basic athletes, even though the user granted the permissions when connecting.

{% hint style="info" %}
If data or planned workout pushes fail for one TrainingPeaks user but work for others, check whether that athlete is on a premium plan first.
{% endhint %}

TrainingPeaks lists the exact restrictions on its [Premium vs. Basic Athlete](https://github.com/TrainingPeaks/PartnersAPI/wiki/Premium-vs-Basic-Athlete) page.