[GH-ISSUE #35] Bubble up more detailed error data #14

New issue

Closed

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

kerem commented

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

Owner

Originally created by @hrkfdn on GitHub (Mar 12, 2019).
Original GitHub issue: https://github.com/ramsayleung/rspotify/issues/35

It'd be nice if the API provided access to more detailed error data, such as the HTTP status code and headers.

This is necessary to implement rate limiting on the client side imposed by the Spotify API servers. Alternatively, an implementation in rspotify that respects Spotify's rate limits would be great, as well.

I'm currently encountering this in https://github.com/hrkfdn/ncspot/issues/29 and am not sure how to handle this.

Originally created by @hrkfdn on GitHub (Mar 12, 2019). Original GitHub issue: https://github.com/ramsayleung/rspotify/issues/35 It'd be nice if the API provided access to more detailed error data, such as the HTTP status code and headers. This is necessary to implement [rate limiting](https://developer.spotify.com/documentation/web-api/#rate-limiting) on the client side imposed by the Spotify API servers. Alternatively, an implementation in `rspotify` that respects Spotify's rate limits would be great, as well. I'm currently encountering this in https://github.com/hrkfdn/ncspot/issues/29 and am not sure how to handle this.