App rate Limit used up by one athlete's import

Question

Over the weekend I got hundreds of 429 errors from Strava when requesting activity details after a webhook notification. It looks that athlete imported 100s of activities into Strava and for each one we received a webhook create-activity notification.Fetching the activities then quickly used up our apps rate limit:

{"message":"Rate Limit Exceeded","errors":[{"resource":"Application","field":"overall rate limit","code":"exceeded"}]}

Thus rendering our apps Strava integration non-functional for all connected Strava athletes. IMHO it would be better to have per athlete rate limits, so one athlete cannot break the integration for other athletes.

We’re think about rate-limiting fetching activities from Strava on our side. But since there is barely any data of the actual activity in the web-hook request, it makes it hard to decide, if we really want to fetch the activity.

Do you have any recommendations how to handle these situations?

Thanks and best regards

Martin

Jan_Mantau · Accepted Answer

You have to handle the rate limits in your app by creating queues. If you don’t have a server that can balance the API access between users the app should at least evaluate the response headers for the current limit usages.

MartinFU · Answer

Thanks, for the input. We already thought of going that direction and wanted some input and confirmation what’s the best solution.

Sign up

Login to the community