Hello Strava developers,
We are building AxonFit, a running coaching SaaS platform in Brazil, and we have a question about the current Strava API Policy.
Our flow is:
1. An athlete creates an account in AxonFit.
2. The athlete connects their own Strava account through OAuth.
3. The athlete explicitly authorizes AxonFit to access their Strava activities.
4. The athlete is linked to a running coach in AxonFit.
5. We would like to display that athlete's Strava activity data to their own coach inside the coaching platform.
The purpose is to compare prescribed training sessions with completed activities, for example:
- distance
- duration
- pace
- elevation
- average heart rate
The athlete is the person who authorizes the Strava connection.
Our question is:
Under the current 2026 API Policy, is this use case permitted if the athlete provides explicit consent for AxonFit to share/display their Strava activity data with their own running coach?
We are particularly trying to understand the interaction between the current "display to the user" requirement and the "prior express consent" provision.
We are not asking about rate limits or athlete capacity in this post.
We would appreciate confirmation from someone familiar with the current API Policy.
Thank you.