Open stevereaver opened 1 year ago
I've spun up my own branch and removed the /, however the error still persists. This has got me really puzzled.
HTTP Error for GET to https://api.spotify.com/v1/shows/47Xw6QagBN5lTAp1Cyoyye/episodes with Params: {'limit': 20, 'offset': 0, 'market': None} returned 404 due to non existing id
Traceback (most recent call last):
File "/home/reaver/.local/lib/python3.8/site-packages/spotipy/client.py", line 245, in _internal_call
response.raise_for_status()
File "/home/reaver/.local/lib/python3.8/site-packages/requests/models.py", line 1021, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://api.spotify.com/v1/shows/47Xw6QagBN5lTAp1Cyoyye/episodes?limit=20&offset=0
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./code.py", line 7, in <module>
results = spotify.show_episodes(uri)
File "/home/reaver/.local/lib/python3.8/site-packages/spotipy/client.py", line 512, in show_episodes
return self._get(
File "/home/reaver/.local/lib/python3.8/site-packages/spotipy/client.py", line 297, in _get
return self._internal_call("GET", url, payload, kwargs)
File "/home/reaver/.local/lib/python3.8/site-packages/spotipy/client.py", line 267, in _internal_call
raise SpotifyException(
spotipy.exceptions.SpotifyException: http status: 404, code:-1 - https://api.spotify.com/v1/shows/47Xw6QagBN5lTAp1Cyoyye/episodes?limit=20&offset=0:
non existing id, reason: None
Not quite sure why, but if you use SpotifyOAuth (no scopes) instead of SpotifyClientCredentials, it seems to work just fine. So my guess is that this is a problem on Spotifys side.
Also, I made an interesting discovery: when I request a token in the Spotify Developer Console, it asks for the "user-read-playback-position" scope, but it seems to work just fine without scopes. The (obvious) difference is a missing playback position for each episode. Maybe Spotify has restricted access to this endpoint only because of this optional scope, but that's just a theory.
And where did you get your token when using cURL?
And where did you get your token when using cURL?
The token was generated on the spotify developer console.
Describe the bug When requesting a show list using show_episodes the URI that is used seems to be; https://api.spotify.com/v1/shows/47Xw6QagBN5lTAp1Cyoyye/episodes/?limit=50&offset=0
However if the same request is done with a curl the URI used is; https://api.spotify.com/v1/shows/47Xw6QagBN5lTAp1Cyoyye/episodes?offset=0&limit=20
NOTE: spotipy adds and addtional / after episodes, which breaks the URI and results in a 404
CURL Command
Python Code
Expected behavior As per description above
Output From Python
Output From CURL
NOTE: The different URI's in each output above.
Environment:
Additional context Add any other context about the problem here.