Hi Strava Developer Community,
I'm the developer of Zivox, a fitness RPG app that integrates with Strava.
We recently reached our 10-athlete capacity and submitted an application for increased athlete capacity.
Unfortunately, our application was declined.
The rejection email listed several common possible reasons:
-
The app does not offer a complementary experience for Strava users
-
API usage is not optimized
-
Security or privacy concerns
-
API Agreement or API Policy compliance
However, it did not indicate which of these actually applies to Zivox.
Our Strava integration is already in production.
Zivox uses an athlete's own Strava activities as part of a fitness RPG experience: physical activity contributes to in-game Energy, which users can use for monster progression and gameplay.
On the technical side, we have implemented webhooks and designed our backend to avoid unnecessary polling and API requests.
I contacted Developer Support asking whether they could at least identify the category that caused the rejection, but received an automated response stating that rate limit and athlete capacity requests are not reviewed via email and directing me to the Developer Community Hub.
I'm happy to correct anything that is not compliant or does not meet Strava's requirements. The difficulty is that without knowing which area caused the rejection, resubmitting would essentially be guesswork.
Could a Strava team member or someone familiar with the current review process please help clarify what we should review or change before submitting again?
If a Strava team member needs our Client ID or application details to look into the specific submission, I'm happy to provide them.
Thank you.
