Hello Strava Community,

I'm experiencing an issue with the "Get Activity Streams (getActivityStreams)" method. When an activity lasts more than 5-6 hours, the response includes an excessive amount of data, resulting in a 500 server error. Is there a way to limit the number of data points returned to prevent this heavy response?

I understand that different stream types (keys) can be queried individually by passing them as parameters, allowing us to request data like distance, time, heart rate, watts, etc., separately instead of all at once. However, even when querying individually, we're still encountering a 500 error for long activities. With the increasing popularity of long endurance sports, where athletes cover distances of 200 miles or more, we can expect very large activities, even in training sessions.

For instance, Garmin provides an option to restrict the number of data points returned, which reduces the data load. While this results in less accurate data, it is often sufficient for long-distance activities where precision is less critical.

Is there any way to retrieve streams for long activities without encountering a 500 error?

Thank you very much.

Kind regards,