Hi Strava API support team and the community,
Let me write a few lines to have the context
- I initially submitted to the API Development program in May, 10, and never got back any response until Jun, 01, when the API program changed
- On Jun, 07, I submitted a support ticket to developers@strava.com, and the support team instructed me to submit a new form for review since my previous submission was closed due to changes in the API policy. I’m ok with that and submitted again.
- Today, Jun 11, I received this email and don’t know what I have to do next, since my app already reached the maximum athlete capacity, already implemented webhooks to receive the workout data, and manages stale and deauthorized athletes. Also, I’m sure that my app complies with the new API Agreement and API Policy
-
Here is the information about my app
- App name: Pace ID
- Primary Client ID: 233610
- Additional development app Client ID: 238433
- Production domain: https://paceid.net
Please let me know the next action I should take.
I know the Strava team members are doing their best to provide a quality API and service to everyone, introducing the MCP and new good things about the API. But on my side, my app has implemented some workarounds to wait for the submission review that added Email login so users can access basic Pace ID features without requiring Strava. Strava is now used as an optional, user-authorized connected activity service for automated race/event verification, tracklog review, anti-cheat checks, and auditability. We have official users in production, and the current 10-athlete Strava connection limit is now blocking additional users who want to connect to Strava for automated verification.
Looking forward to the next guidance from the support team.
Thank you