Athlete capacity increase — Developer Program form submitted for Esprit Trail (Client ID 232321)

Question

Hi everyone,Posting here for visibility on a Developer Program form submission, as suggested by the support auto-response.CONTEXTI just submitted the Developer Program form on June 9, 2026 to request an athlete-capacity increase for my application Esprit Trail (Client ID 232321), currently in Single Player Mode. Form confirmation acknowledged the submission ("Thank you for submitting your application for review — Strava API Team").WHAT THE APP DOESEsprit Trail is a companion app for trail runners: AI-assisted training plans, a curated trail-race calendar, training-spots discovery and a community space. Connecting Strava is the recommended onboarding path so the athlete's past and new activities populate their stats, training plan and history.- Web: https://esprit-trail.vercel.app- Distribution: PWA on the web + Android app published on Google Play (TWA wrapper)API USAGE SUMMARY- OAuth 2.0 authorization code flow with refresh-token handling- Scopes: activity:read_all, profile:read_all (read-only)- Endpoints: POST /oauth/token, GET /api/v3/athlete, GET /api/v3/athlete/activities (paginated, "after" cursor)- Activity import is user-initiated from /settings/connections/strava — no scheduled polling- Webhooks not yet implemented; planned for the first month after Single Player Mode is lifted- Storage in Supabase with Row Level Security per athlete; full GDPR Article 17 deletion available from the connection pageBRAND GUIDELINES COMPLIANCE- Official "Connect with Strava" button (1.1 asset, orange 237x48) used wherever an athlete initiates the OAuth flow (settings page + two points in the onboarding flow)- Official "Powered by Strava" horizontal orange logo displayed as attribution on the Strava connection page- No recreated, modified or animated Strava logos anywhere- No Strava logo as the app icon (our own runner-sunset logo)- Strava name/logos appear near, but separate from, our brand and never more prominently- The "Connect with Strava" button links to https://www.strava.com/oauth/authorize via our server-side redirect at /api/oauth/stravaWHAT I'M HOPING FOR- Visibility for the form submission (Client ID 232321) so it doesn't fall through- Any tips from devs who recently went through the same review process — timing, gotchas, common reasons for back-and-forthEstimated capacity needed: 100 to 300 connected athletes over the next 3 months (closed beta then progressive public launch).Happy to share more details if useful.Thanks!Guillaume — Esprit Trail

Mark_AJ · Answer

Hey ​@Esprit TRAIL! Appreciate the detailed write-up but your app has a fundamental policy violation that will get it rejected.The AI training plans are a hard blocker. Strava's current policy explicitly bans using API data with AI models or similar applications. This isn't a grey area or something you can get approval for, it's a flat out ban. If your training plans use Strava activity data fed into an LLM, that feature needs to go before you resubmit.Webhooks being absent is the second flag. Ship them before resubmitting, don't wait.Until the LLM issue is resolved, the rest of the submission doesn't matter.Good luck!

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded