Skip to main content
Question

Request to raise connected-athlete limit & rate limits — URUNN (Client ID: 156678)

  • July 16, 2026
  • 1 reply
  • 28 views

Forum|alt.badge.img

Hi Strava team,

We develop URUNN, a running/fitness coaching app in the Training category that integrates with the Strava API on our athletes' behalf.

We've now hit the Standard Tier ceiling of 999 connected athletes. we're at 999 / 999, so new users can no longer connect their Strava accounts. We'd like to request an upgrade to support our growing user base.

Application details

  • App name: URUNN
  • Client ID: 156678
  • Developer Tier: Standard
  • Category: Training
  • Athletes allowed to connect: 999
  • Athletes currently connected: 999 (at capacity)

Current rate limits

  • Overall: 600 requests / 15 min, 6,000 / day
  • Read: 300 requests / 15 min, 3,000 / day

What we're requesting

  1. An increase to the number of athletes allowed to connect (our primary blocker), we're requesting a limit of 20,000–50,000 athletes to accommodate current demand and near-term growth.
  2. A corresponding increase to our overall and read rate limits to keep sync reliable at that athlete count. Our daily usage already peaks around 3,200 requests/day, so we'll quickly outgrow the current 6,000/day ceiling as we scale.

How we use the API

  • Uploading athletes' completed workouts to their Strava accounts after each session
  • Reading activity data to confirm/sync workout results
  • We respect the X-RateLimit-* / X-ReadRateLimit-* headers, back off on 429s, and refresh tokens automatically to minimise redundant calls.

Happy to share usage graphs, OAuth scopes, or anything else needed to review the request.

Thanks in advance,
Yasin Ilhan
URUNN — yasin@withutraining.com

1 reply

Jan_Mantau
Forum|alt.badge.img+26
  • Hub Powerhouse
  • July 16, 2026

Hi ​@Yasin, please lookup https://developers.strava.com/docs/rate-limits/, Section “Adjustment Requests” for information about requirements and how to submit for a review.