API returns HTTP 429 with -1/-1 rate limits — Client ID 190585

Hello Strava Developer Support,

I’m developing PerformanceLAB, an endurance training and performance platform using the Strava API.

Client ID: 190585
Developer level: Standard
Athlete capacity: 10
Connected athletes: 1

We are consistently receiving HTTP 429 Too Many Requests when calling:

GET /api/v3/athlete/activities

We have instrumented the API response and captured the following rate-limit headers from a real request:

X-RateLimit-Limit: -1,-1
X-RateLimit-Usage: 3,9
X-ReadRateLimit-Limit: -1,-1
X-ReadRateLimit-Usage: 3,9
Retry-After: not present

The application dashboard also displays:

Overall Rate Limits: -1 requests every 15 minutes, -1 daily
Read Rate Limits: -1 requests every 15 minutes, -1 daily

The API usage shown in the dashboard is very low, yet /athlete/activities consistently returns HTTP 429.

According to the current Strava API documentation, expanded access with an athlete capacity of 10 should provide read limits of 200 requests / 15 min and 2,000 / day, and overall limits of 400 requests / 15 min and 4,000 / day.

OAuth authentication and token refresh are working correctly. The access token is valid when the activities request is made. We have also confirmed that this is a real Strava HTTP 429 response and not an application-side throttle.

Could you please check whether Client ID 190585 has been provisioned correctly, or whether there is a restriction/throttle currently applied to the application?

I can provide timestamps, response headers, screenshots and additional diagnostics if required.

Thank you,

Aitor Bajo
PerformanceLAB / NextOrigin Systems
performancelab.pro