Skip to main content

I’ve been using the api/v3/activities/{id}/streams?keys=time,watts in a web application for roughly 3 years with no problems. This last week, suddenly, the exact same API call seems to be returning data with gaps: not starting with the same timestamp as the .fit file (ie, missing the first 200 or so values) and skipping one or two seconds of power data throughout the stream (ie, like Swiss cheese, full of holes)

Is this my problem or Strava??

Be the first to reply!

Reply