Skip to main content
Answered

API Limit Increase Rejected Despite Webhook-Based Integration

  • March 31, 2026
  • 3 replies
  • 94 views
U
Forum|alt.badge.img

Our request for API limit increase was rejected, and we’re trying to understand the reason.

We are following a controlled approach:

  • Using webhooks as primary source for activity updates
  • Minimal polling (only manual/historical sync)
  • Proper rate limit handling (429, Retry-After, backoff)
  • Token lifecycle management (refresh + deauthorization)

Our API usage is limited and not aggressive.

I’ve attached a screenshot of our current usage/limits for reference.

Client ID: 156908

Could you please help us understand what needs to be improved for approval?

Best answer by ActivityFix

Disclaimer: Most responses on this board are from community members so this is all opinion. You would need to contact developers@strava.com for an official answer.

---

Was there any message or explanation given when your request was rejected?

I cannot remember what the default limits are but I think it’s 999 athletes and 200/2000 requests per 15m/24h? If that is the case, you still seem to have a lot of overhead in your API usage so unless you are near the athlete limit they may have rejected it because you aren’t that close to your limits yet.

The other question would be how many connected athletes do you have? My understanding from reading other threads on here is that nearing athlete capacity seems to be the most likely way to increase your limits. Even if you are using all of your API requests, if you only have a few hundred connected athletes you may not get an increase since your app is “inefficient.”

3 replies

ActivityFix
Superuser
Forum|alt.badge.img+24
  • ActivityFix
  • Superuser
  • Answer
  • April 1, 2026

Disclaimer: Most responses on this board are from community members so this is all opinion. You would need to contact developers@strava.com for an official answer.

---

Was there any message or explanation given when your request was rejected?

I cannot remember what the default limits are but I think it’s 999 athletes and 200/2000 requests per 15m/24h? If that is the case, you still seem to have a lot of overhead in your API usage so unless you are near the athlete limit they may have rejected it because you aren’t that close to your limits yet.

The other question would be how many connected athletes do you have? My understanding from reading other threads on here is that nearing athlete capacity seems to be the most likely way to increase your limits. Even if you are using all of your API requests, if you only have a few hundred connected athletes you may not get an increase since your app is “inefficient.”

    V
    Forum|alt.badge.img

    também apareceu essa mesma mensagem para mim

    V
    Forum|alt.badge.img

    está acontecendo comigo

    Terms & ConditionsCookie settingsAccessibility statement