spotify-downloader: 429/500/404 Errors and Rate Limiting Issues
Hey everyone,
I’ve been seeing more 429/404/500 errors, and slow query processing lately. This is because of Spotify’s rate limits on our shared project.
Quick Fix: Use Your Own Client ID and Secret
To avoid these issues, we recommend using your own client ID and secret from Spotify. Here’s how:
- Visit the Spotify Developer Dashboard: Go to Spotify Developer Dashboard.
- Log In: Sign in or create a Spotify account.
- Create a New App: Click “Create an App” and fill in the details. (Set APIs used to
Web APIand Redirect URIs tohttp://127.0.0.1:9900/(or whatever you want to use)) - Get Your Credentials: Copy your client ID and secret.
Update Your Settings:
- Config File: Update your settings in the config file as described here.
- Command Line Options: Alternatively, use the following command line options:
--client-id CLIENT_ID --client-secret CLIENT_SECRET
I’m working on a long-term fix to better manage our rate limits. Stay tuned for updates!
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 72
- Comments: 45 (3 by maintainers)
I had the same issue as @Wallvon and @SudoZachCampbell, using my own Client ID and Secret, but it would still throw 429.
What fixed it for me was to use your own Client ID and Secret, and delete
~/.spotdl/.spotipyFWIW, using the
--user-authoption fixed the issue for me (specifying client id/secret did not work). You’d have to be logged in on your browser though.I believe the reason this no longer works is due to changes related to algorithmic and Spotify-owned editorial playlists.
More details here: https://developer.spotify.com/blog/2024-11-27-changes-to-the-web-api
For some reason, the API occasionally returns content for curated playlists, but other times it responds with a 404 error.
Getting the metadata from Spotify. We can’t do that without authorization.
hello bros um i got this for like a week or two i just made my playlist public and i was able to download my playlists that i was trying to download, i think it still holds up its just the playlist was private on spotify it cant get shit because its private idk, i just made my playlist public and i got the playlists i was about to punch my laptop when i thought about making my playlist public so spotdl can find the shit, can any one of you guys check if you can download a playlist with it in a private playlist and a public one it the theory is correct then i was right, if i was wrong theres something wrong with spotdl,( ive been using spotdl for a week now i just fixed it just know july 23 i mean i didnt fix it i just changed my spotify playlist to public haha well anyway i hope yall try it because it worked for me just make your spotify playlist to public) bye bye
For anyone else having issues with the 429 Too Many Requests error: I just did this: https://github.com/spotDL/spotify-downloader/issues/2139#issuecomment-2241152315 And also what was recommended as the “quick fix” (first post in this issue)
And now, this works for small albums, but when I try on a larger playlist (like my 300+ liked songs) it returns the 429 error. No matter, for if that’s the case, it’s probably better to split your liked songs playlist into several smaller public playlists, to then download sequentially.
I just tried this - hasn’t fixed it for me. Even with my own client id and secret. But thanks anyway.
I have only ever used command prompt method and constantly rate limited.
well what worked for me was downloading directly from command prompt:
spotdl download ( your link here without paretheses)
idk why but why interface isn’t working for me.
I’ve setup a Spotify app and entered the credetials but I still get the follwing:
sooooo, what is the solution to this, i have 4.2.11 and it blocks at 50%
Just want to chip in and say I’m having the same issue as @Wallvon, no auth solution is fixing the sync command for myself
Using a client id + client secret or user auth doesn’t work for me when using
spotdl sync {filename}.spotdl. I keep getting the following 429 error:I have already tried creating a new sync file to no avail:
i’ve been getting the same behaviour (sync hanging after
DEBUG MainThread - Found 50 songs in 1 lists).i’m rotating 3 different spotify apps, but still doesn’t (always) helps.
any chance we could get some debug logs that could warn about the process being stuck and the reason ? (i guess if we don’t get a console feedback after 30 minutes the issue is clear, but avoiding the infinite hanging would be nice)
thank you @xnetcat this worked perfectly to resolve the issue.