Skip to main content
Question

Reached 999 User Limit - Awaiting API Limit Increase (Submitted April 6 - Client ID: 217181)

  • April 29, 2026
  • 1 reply
  • 104 views

aimanfurqon
Forum|alt.badge.img+1

Hi Strava API Team! 

I submitted an API rate limit increase request back on April 6th, but haven't heard back yet (which is well past the standard SLA). I also followed up via Zendesk on April 20th.

My application (Client ID: 217181) creates custom data overlays for running communities. We recently gained unexpected traction and hit the 999-athlete cap much faster than anticipated.

We currently have several running clubs on a waitlist who are eager to onboard, and we are heavily relying on a manual input workaround right now. We'd love to get our capacity unlocked so we can continue providing a seamless Strava-connected experience for these communities.

(The full app description, URL, and use cases are already detailed in my API dashboard submission and Zendesk ticket).

Could someone from the team please help look into this? Any help to escalate this review would be highly appreciated! Thank you! 

1 reply

aimanfurqon
Forum|alt.badge.img+1
  • Author
  • Hub Rookie
  • May 6, 2026
I've now addressed both points from the feedback email received today:
  1. Webhooks implemented — Active subscription (ID: 344764) registered at https://www.pursuittag.com/api/strava/webhook, handling activity and deauthorization events
  1. Deauthorized athletes handled — App now calls POST /oauth/deauthorize on disconnect, and deauth webhook events are recorded in our database
Re-submission form has been submitted and a reply sent to the feedback email. Client ID: 217181
Hoping for a faster turnaround this time. Thank you!