[GH-ISSUE #124] Add unlimited endpoints #41

New issue

Closed

opened 2026-02-27 20:22:45 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 20:22:45 +03:00

Owner

Originally created by @marioortizmanero on GitHub (Sep 9, 2020).
Original GitHub issue: https://github.com/ramsayleung/rspotify/issues/124

One thing I really like about tekore is that it offers endpoints without limits. Spotify has a limit of items that may be returned with certain requests, such as the followed artists or the songs in a playlist.

There are two different ways to do that with tekore AFAIK:

And then the endpoints themselves are what you'd expect: followed_artists. These don't mention the "unlimited" mode, it's only tied to the client itself. The client will internally send multiple requests until the endpoint returned value is complete, and return the results.

How this could be implemented in this library could of course vary, but this feature itself is very useful and interesting.

Originally created by @marioortizmanero on GitHub (Sep 9, 2020). Original GitHub issue: https://github.com/ramsayleung/rspotify/issues/124 One thing I really like about [tekore](https://github.com/felix-hilden/tekore) is that it offers endpoints without limits. Spotify has a limit of items that may be returned with certain requests, such as the followed artists or the songs in a playlist. There are two different ways to do that with tekore AFAIK: * [scoped for a number of calls](https://tekore.readthedocs.io/en/stable/reference/client.html#tekore.Spotify.max_limits) * [when initializing the client](https://tekore.readthedocs.io/en/stable/reference/client.html#tekore.Spotify) And then the endpoints themselves are what you'd expect: [`followed_artists`](https://tekore.readthedocs.io/en/stable/reference/client.html#tekore.Spotify.followed_artists). These don't mention the "unlimited" mode, it's only tied to the client itself. The client will internally send multiple requests until the endpoint returned value is complete, and return the results. How this could be implemented in this library could of course vary, but this feature itself is very useful and interesting.