Looks like something changed on Spotify's side that started causing 502 Bad Gateway errors when accessing top tracks/artists, where the combined value of limit and offset parameters exceeds the total number of items - 100:
We originally defined a limit of 49 for top items streams in order to maximise the amount of data returned (i.e. over 100 items) by exploiting a previous quirk of the API, where paginating with next links yielded an "extra" 49 items (147 total):
Looks like something changed on Spotify's side that started causing
502 Bad Gateway
errors when accessing top tracks/artists, where the combined value oflimit
andoffset
parameters exceeds the total number of items - 100:Working
Broken
We originally defined a
limit
of 49 for top items streams in order to maximise the amount of data returned (i.e. over 100 items) by exploiting a previous quirk of the API, where paginating withnext
links yielded an "extra" 49 items (147 total):1st request
2nd request
3rd request (now
502 Bad Gateway
) - nonext
link, pagination stopsIf 50 was used instead, pagination would stop at
?limit=50&offset=50
(100 total):1st request
2nd request - no
next
link, pagination stops