Originally Posted by
Tycho Brahe
I have also built some tools around the Strava API. Since the API is not really public, and there are no developer keys, do you throttle yourself in order to not overwhelm Strava with API calls?
To do anything non trivial requires multiple calls. I have resorted to caching data, but most API providers do not allow the external storage of their data.
I only posted the link: the site has nothing to do with me. However, it looks as though veloviewer.com is caching the Strava data externally judging by the way the update mechanism is working.