Skip to main content
Question

Client ID: 101852 — My API request was rejected 3 times with only a generic message. Could you please share the exact reason? I’m fixing issues based on assumptions, which is wasting time. Specific feedback would help me resolve the correct issues.

  • July 1, 2026
  • 2 replies
  • 30 views

Forum|alt.badge.img+1

Client ID: 101852

My API access request has been rejected three times, but each time I only received a generic rejection message. Because of that, it’s very difficult to understand what is actually missing or what needs to be fixed.

I have already addressed everything I could based on the Strava API guidelines and previous feedback. Could you please provide more specific and granular feedback on why my application is still being rejected? Knowing the exact issues would help me resolve them instead of making changes based on assumptions.

I also have one question regarding my Fitness Challenges app.

The app includes a leaderboard where I display other participants’ names, total points (calculated using my own scoring formula), total distance, and total elevation. As I understand the Strava API policy, we should not expose another user’s distance and elevation data. However, in the context of a fitness challenge, showing only the points is not very useful. Participants need to know how much distance and elevation others have completed so they can understand the competition and know how much more they need to ride to move up the leaderboard.

The app does not display athlete profiles, Athlete IDs, activity details, or links back to Strava. It only shows aggregated challenge statistics for competition, motivation, and leaderboard purposes.

Could you please clarify whether displaying these aggregated public activity totals (distance and elevation) for challenge participants is allowed in this specific use case? If not, I would appreciate your guidance on the recommended approach.

2 replies

Jan_Mantau
Forum|alt.badge.img+26
  • Hub Powerhouse
  • July 1, 2026

It’s possible that the leaderboard is indeed the problem but other users can only guess.


Forum|alt.badge.img+1

I also assuming the same. So asked Strava team via developer email to provide detail explanation and approval to this use case and also give granular feedback to fix. But no luck as of now