+1Hello Community, I have been trying to get Strava to respond to athlete limit increases since October, submitted the form multiple times and have never got a response.
Is Strava going under? Should we be selling our stock? What is going on, it seems like no one is working there? Has anyone had any luck getting past the 1 athlete limit for new apps in the past 6 months?
Thanks!
Best answer by ActivityFix
Does the website have to be 100% functional and live for the app to be approved?
For example, if the website is mostly complete but certain features (especially the ones relying on Strava’s API) are still under development, does that pose an issue during the approval process?
For initial approval my guess would be no. I think as long as you’ve got some API features working and Strava can see that you’re making API calls successfully you’ll probably be fine. However it may impact your API limits that initially get set since they will only see you using a small subset of the API. Most apps are frequently changing and updating which means that even established ones will potentially add/remove API calls or change how they call the API.
- What exactly does Strava look at during the review?
Do they just check compliance with their API guidelines, or is there a deeper review of the backend, endpoints, and user flows?
They don’t ask for any code access so there’s no deeper review that I am aware of. My guess would be checking that the site complies with their guidelines, and they probably look at your historical API usage to see if you’re making a reasonable number of requests, subscribed to webhooks, etc… Again I expect it’s slightly different for initial approval vs future limit increases, as there’s not really a lot to see when only a single user is using the app. Once you have more users they can get a better idea of how you’re using the API to decide what the new limits should be .
+4I started asking for an increase in athlete capacity limit in september 2024 and they first responded and adjusted in december 2024. They wrote “We appreciate your patience as our team works through the backlog”. Best of luck 😊
I’m currently working on integrating the Strava API into my project, and I’m at the stage where I need to get my app approved. I was wondering if anyone here knows:
Does the website have to be 100% functional and live for the app to be approved?
For example, if the website is mostly complete but certain features (especially the ones relying on Strava’s API) are still under development, does that pose an issue during the approval process?
What exactly does Strava look at during the review?
Do they just check compliance with their API guidelines, or is there a deeper review of the backend, endpoints, and user flows?
I’m trying to avoid unnecessary delays or rejections, so any tips from those who’ve been through this process would be super helpful!
Thanks a lot!
+24
Does the website have to be 100% functional and live for the app to be approved?
For example, if the website is mostly complete but certain features (especially the ones relying on Strava’s API) are still under development, does that pose an issue during the approval process?
For initial approval my guess would be no. I think as long as you’ve got some API features working and Strava can see that you’re making API calls successfully you’ll probably be fine. However it may impact your API limits that initially get set since they will only see you using a small subset of the API. Most apps are frequently changing and updating which means that even established ones will potentially add/remove API calls or change how they call the API.
- What exactly does Strava look at during the review?
Do they just check compliance with their API guidelines, or is there a deeper review of the backend, endpoints, and user flows?
They don’t ask for any code access so there’s no deeper review that I am aware of. My guess would be checking that the site complies with their guidelines, and they probably look at your historical API usage to see if you’re making a reasonable number of requests, subscribed to webhooks, etc… Again I expect it’s slightly different for initial approval vs future limit increases, as there’s not really a lot to see when only a single user is using the app. Once you have more users they can get a better idea of how you’re using the API to decide what the new limits should be .
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
