Hello Strava Developer Team,
I'm writing to request an increase from the default 1-athlete limit for my application "Running Coach Pro", currently in private MVP testing.
APPLICATION DETAILS
- App Name: Running Coach Pro (branded "Team Total Trail" during testing)
- Client ID: 236045
- Website: https://teamtotaltrail.netlify.app
- Authorization Callback Domain: sbluphkqhfeoiwfcaccy.supabase.co
- Brand compliance: full compliance with Strava Brand Guidelines — the Strava brand orange (
#FC4C02) is used only for the official "Connect with Strava" button; the rest of the app uses our own brand palette (turquoise/blue/green gradient).
WHAT THE APP DOES
A SaaS platform for running and trail coaches to manage their athletes. Athletes connect their Strava account so coaches can:
- View training activities (distance, pace, heart rate, splits, zones)
- Adjust personalized training plans based on real performance data
- Provide per-session feedback (visible to the athlete)
- Track progress toward race goals (5K → ultras)
Athletes never pay — the product is for the coach (B2B SaaS), the athlete is the coach's client. AI assists the coach but never communicates directly with the athlete without coach supervision.
OAUTH FLOW
Standard authorization_code flow, fully implemented end-to-end:
- Frontend redirects athlete to /oauth/authorize with scope=activity:read_all
- Supabase Edge Function (strava-oauth-callback) exchanges the code for tokens via POST /api/v3/oauth/token
- Tokens stored per-athlete (access_token + refresh_token + expires_at) in our database
- Refresh handled automatically before each API call when expires_at < now()
WEBHOOK IMPLEMENTATION
Push Subscription active:
- Subscription ID: 345139
- Callback URL: https://sbluphkqhfeoiwfcaccy.supabase.co/functions/v1/strava-webhook
- Registered: May 8, 2026
The webhook handles:
- GET hub.challenge — subscription verification (returns 200 OK with echoed challenge after verifying our verify_token)
- POST athlete deauthorize events — immediately deletes the athlete's tokens from our database (privacy compliance)
- POST activity events — logged for now; full real-time processing planned for the next iteration
SCOPES REQUESTED
- activity:read_all (for reading athlete activities)
EXPECTED SCALE
- Initial private testing (now): ~25 athletes (3 coaches × 5-8 athletes each)
- Public launch (3-4 months): 100-300 athletes
- 12-month target: up to 1,000 athletes
API USAGE BEHAVIOR
- Activity sync is on-demand (manual button) plus webhook-driven — no aggressive polling
- Token refresh is just-in-time (only when expires_at < now)
- Webhook reduces unnecessary API calls vs polling
Could you please increase the athlete limit so we can move forward with private testing? Happy to provide any additional info.
Thank you for your time.
Best regards, Santiago. Running Coach Pro / Team Total Trail santiagoesperguin@gmail.com
