504 on offsets over 10k

[happy-machine]

Issue found on February 19th 2015.

Endpoint(s):

• GET /v1/users/{user_id} https://api.spotify.com/v1/search https://api.spotify.com/v1/users/playlists/ https://api.spotify.com/v1/users//playlists/tracks

Scope(s):

• None (application is not using authentication)

Steps to reproduce:

My code searches for tracks on playlists, getting 504 on searches with offset set to over 10000. Have found lots of other complaints about this specific issue online. The API docs state the limit is 100 000

Expected behaviour:

Actual behaviour:

504 Server Error (consistently)

[dotfield]

It has worked for me until today. Suddenly I also hit a 10000 limit. That is not enough, there are more than 10000 releases and I can't filter them by number of tracks in my search.

I only want releases with 4 tracks or fewer.

[hughrawlinson]

Thanks for the report @happy-machine. Should definitely not return a 504. I'll bring this up with the team.

[happy-machine]

Thanks man 😊 seen lots of people moaning about this when searching around at the time so i think its affecting other peeps too

[shillshocked]

It used to be 100,000, which was also not enough if we want to get a year's releases.

There are over 1,000,000 characters in the unicode standard library. Are you suggesting we do 1,000,000 requests to find ALL new releases using tag:new?

This workaround might find most releases in English. There are still about 4,000 songs though it doesn't work on under tag:new because they use special characters, or non-Latin languages like Chinese, Japanese, Korean, Arabic, etc. What is the solution for users of every other language besides English?

The easy solution if Spotify wants to be lazy is to allow us to search by release day (like Napster), not just once every two weeks. Then all this monkeying around with substrings will be less of an issue. What is proposed now is an ethnocentric solution that doesn't address non-English spotify users, artists, albums, playlists and songs.