Skip to main content
Question

Follow-up on athlete limit increase request — Ticket #17768 (App ID 111286)

  • September 7, 2026
  • 4 replies
  • 41 views
Forum|alt.badge.img+1

Hi Strava API Team,

I submitted a request to increase the connected-athlete limit for my app More Race (Client ID: 111286) after hitting the 999-athlete cap (403 error). I completed the official form as advised, and received confirmation that my submission is under review (Ticket #17768).

It has now been 10 days since submission, and I haven't received any further update. I understand increased access isn't guaranteed and that reviews take time — I just wanted to respectfully check whether there's any update on the status of my request, or if any additional information is needed from my side to help move it forward.

More Race is a race/event management platform for running events. Participants connect their Strava accounts so we can sync their activities for event tracking, results, and leaderboards.

Thank you very much for your time and support.

Best regards,
Nguyen Vinh Kieu — More Race

4 replies

Forum|alt.badge.img

I am currently at 700/999 users, I have a technical question, hope you don’t mind me asking this… does Strava API simply stop working altogether for existing users and prevent them from a token refresh/ relogin altogether or only new users are prevented from signing in? 

Strava API support has been very disappointing, I am slowly moving the login to Garmin/ Apple Watch only for my app 

    Forum|alt.badge.img+1
    • More Race team
    • Author
    • Hub Rookie
    • September 7, 2026

    Hi, happy to share from experience — my app went past 999.

    From what I've seen (and per Strava's OAuth docs): the 999 cap limits the number of connected athletes on your app, not the traffic of athletes already connected.

    • Existing users (already connected before you hit the cap): they keep working normally. Their access tokens still work, refresh tokens still refresh, and re-login/re-auth is fine — because they're already in your connected list, so no new "slot" is needed.
    • New users (not yet connected when you're at 999/999): they're the ones blocked, getting the 403 "Limit of connected athletes exceeded" at the OAuth step.

    The only way an existing user's tokens get invalidated (401 Unauthorized) is if the app calls the deauthorize endpoint (POST /oauth/deauthorize) to remove them — that's a deliberate action, it doesn't happen automatically at the cap.

    So in short: at 999/999, existing users aren't cut off — only new sign-ins are blocked. Hope that helps!

      Jan_Mantau
      Forum|alt.badge.img+26
      • Jan_Mantau
      • Hub Powerhouse
      • September 7, 2026

      ​@More Race team  Please lookup section 3.6 in the API policy https://www.strava.com/legal/api_policy , there isn’t any target for the review time.

      Forum|alt.badge.img

      Hi, happy to share from experience — my app went past 999.

      From what I've seen (and per Strava's OAuth docs): the 999 cap limits the number of connected athletes on your app, not the traffic of athletes already connected.

      • Existing users (already connected before you hit the cap): they keep working normally. Their access tokens still work, refresh tokens still refresh, and re-login/re-auth is fine — because they're already in your connected list, so no new "slot" is needed.
      • New users (not yet connected when you're at 999/999): they're the ones blocked, getting the 403 "Limit of connected athletes exceeded" at the OAuth step.

      The only way an existing user's tokens get invalidated (401 Unauthorized) is if the app calls the deauthorize endpoint (POST /oauth/deauthorize) to remove them — that's a deliberate action, it doesn't happen automatically at the cap.

      So in short: at 999/999, existing users aren't cut off — only new sign-ins are blocked. Hope that helps!

      Thanks for the detailed reply, really appreciate it… was just confused on whether to continue showing the Strava Login option on my app post 999, this has answered my question :)

      Terms & ConditionsAccessibility statement