mirror of
https://github.com/Googolplexed0/zotify.git
synced 2026-04-24 22:05:53 +03:00
[GH-ISSUE #151] Same API 429 problem after new update #134
Labels
No labels
bug
considering
discussion
documentation
enhancement
enhancement
good first issue
help wanted
pull-request
question
stale
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/zotify#134
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @daanreijrink on GitHub (Jan 14, 2026).
Original GitHub issue: https://github.com/Googolplexed0/zotify/issues/151
Originally posted by @Googolplexed0 in #135
after this i stil get the API error
@SkilletWarez commented on GitHub (Jan 15, 2026):
Delete
credentials.jsonWhich are you trying to do?
With developer app or none?
@daanreijrink commented on GitHub (Jan 16, 2026):
Yes, I’ve tried that, and it still doesn’t work.
And I think I’m using NONE.
@DieselMane2006 commented on GitHub (Jan 18, 2026):
Same, i installed the efficient api version, the normal one, reverted to earlier versions, nothing helps. i have no idea how to connect to my own API token with spotify developer or smth so im kinda stranded now. This is my first few monthd of python so i have no idea whats going on.
love the program, not sure what to do tho
@SkilletWarez commented on GitHub (Jan 18, 2026):
credentials.jsonto refreshzotify --client-id xxxxxxxxxxxxxxxxxAnd login link will show.
@LoZ9009 commented on GitHub (Jan 19, 2026):
Hey, unfortunately I have tried this same process but it seems to give me "INVALID_CLIENT: Invalid redirect URI" when going to the link
I figured this was due to the callback url in the developer app, but what do I need to set this to? I feel a little confused on this part
@SkilletWarez commented on GitHub (Jan 19, 2026):
Change * into the link you are connecting for e.g
http://127.0.0.1:1481/loginCALLBACK at developer App
http://127.0.0.1:*/login@LoZ9009 commented on GitHub (Jan 19, 2026):
Perfect, that did the job, thank you so much!
@ilovecats4606 commented on GitHub (Jan 19, 2026):
It says "Not Secure"
@ilovecats4606 commented on GitHub (Jan 19, 2026):
Also, where can i find my config files?
@SkilletWarez commented on GitHub (Jan 19, 2026):
Not reading.
@ilovecats4606 commented on GitHub (Jan 19, 2026):
I dont know how to find the port, to replace aesterick
@LoZ9009 commented on GitHub (Jan 19, 2026):
When Skillet mentioned to do http://127.0.0.1:*/login , he didn't mean a copy and paste
Where * is, you need to add the port number that you can find in the login link, when you try to log into Zotify with "zotify --client-id (YOUR CLIENT ID WITHOUT BRACKETS)"
Once that is added as a callback URI, you'll be able to log in without issues
@ilovecats4606 commented on GitHub (Jan 19, 2026):
yeah i get that now. However, when i try to zotify--clientid login, it either hangs on Logging In or gives a Errno 54 reset by peer. Therefore, trying to find the credentials.json, but I don't know where its located?
@ilovecats4606 commented on GitHub (Jan 19, 2026):
The same command is executed. One time it throws error. Another, it hangs on login. I wanted to find credentials.json to delete and try relogin but dont know where it is
@LoZ9009 commented on GitHub (Jan 19, 2026):
I see, and you're on Linux? I know where it is on Windows but not Linux
@ilovecats4606 commented on GitHub (Jan 19, 2026):
macOS
@ilovecats4606 commented on GitHub (Jan 19, 2026):
@LoZ9009 commented on GitHub (Jan 19, 2026):
Unsure where the credentials.json would be on Mac, but I imagine Skillet might have an idea
@ilovecats4606 commented on GitHub (Jan 19, 2026):
Found it! It's at your user profile/ApplicationSupport/Zotify.
Also, there is an issue with the Spotify, you cannot have localhost
@ilovecats4606 commented on GitHub (Jan 19, 2026):
Solution, how to use WebAPI Client ID
zotify -u USERNAME --client-id CLIENTID. Username can be found here https://www.spotify.com/au/account/profile/. Clientid is in your devapp settingsClick the link to login:and a big link, inside that link you will seeredirect_uri=http://127.0.0.1:XXXX/login. The four X are replaced with numbers. You need to put these number into your app Basic Information -> Redirect URIS ashttp://127.0.0.1:XXXX/login. Replace the four X with the numbers from the link in your terminal. If you press save and it says failed to edit, it may be because of other URIs that havelocalhost, those are not allowed, must be deletedlibrespot-python received callbackLogging Infor over a minute after signing in, go back to step 1. Note the four numbers may change so double check it.hopefully this can help anyone trying to login :)
edit: cant download anything with the "failed to fetch audio key". looked around in some issues and found that this is happening to people with spotify free only and looks like it wont be fixed? not sure :(
@jonaaa20 commented on GitHub (Jan 19, 2026):
It won't be fixed. It only works with Premium Accounts.
@LoZ9009 commented on GitHub (Jan 19, 2026):
Is there anywhere I could message you? Like Discord or something, since i'd be happy to help you out directly given it's working for me
@jonaaa20 commented on GitHub (Jan 19, 2026):
Are you using a Free or Premium Account? because i have the same problem.
@LoZ9009 commented on GitHub (Jan 19, 2026):
Premium account, and it was working fine for me yesterday when I used it, I can give it a look now to see if that's still the case
Edit: Still working fine for me
@jonaaa20 commented on GitHub (Jan 19, 2026):
His problem (and mine) is just the account not being Premium, i'll get another month sub and test again later.
@LoZ9009 commented on GitHub (Jan 19, 2026):
Seems to be the case yeah, hopefully there will be some workaround in the future but seems a little bleak with how Spotify is going
If either yourself or ilovecats needs anything downloading in the meantime let me know and i'll help out, no hassle. Can drop my contact for somewhere here and delete it after
@ilovecats4606 commented on GitHub (Jan 20, 2026):
ilovecats4606 is my discord
@LoZ9009 commented on GitHub (Jan 20, 2026):
Sent you a request now, we'll sort things there
@besweeet commented on GitHub (Jan 21, 2026):
Using the efficient-api branch (version 0.11.15). Stuck at OAuth errors:
@Aeiron2 commented on GitHub (Jan 21, 2026):
can I use someone else's developer api or do I have to use my own? Spotify unfortunately is not allowing new creations ;(
@jonaaa20 commented on GitHub (Jan 21, 2026):
Your own. You need an account with Premium and this same account MUST have a DEV API.
@besweeet commented on GitHub (Jan 21, 2026):
Is that the only option right now?
@jonaaa20 commented on GitHub (Jan 21, 2026):
Yes.
@Googolplexed0 commented on GitHub (Jan 21, 2026):
Your librespot_python is out of date.
@ilovecats4606 commented on GitHub (Jan 21, 2026):
you can't have a free account devapi, and have another premium spotify account? interesting
@besweeet commented on GitHub (Jan 21, 2026):
That did the trick. Thanks. I did need to add
--bypass-metadata-api Trueto the command. Also only works with individual tracks and not playlists, but better than nothing for now.@stannismannis commented on GitHub (Jan 22, 2026):
Hi @Googolplexed0! Thank you so much for all your work on maintaining Zotify, this has literally changed the way I've archived my media :)
Quick question - Is it expected that whenever the download finishes, the file name becomes the track's URL ID (e.g. 0uhYgQQ6WX9rCONnum7Fmw.mp3)? How do I make the filename correct like before? In this case it should be "I Know - Fiona Apple.mp3"
I'm able to download songs one by one using the efficient-api branch without the Spotify developer app like this:
Here's my config file
Do I need to change something in my config? Hope you may advise, thank you!
@U2EZNeko commented on GitHub (Jan 22, 2026):
Is there no way to add a client ID to config?
I keep running into similar issues, now with my new install it doesn't even recognize --client-id no matter which branch I try. "unrecognized argument"
I have multiple API keys setup for different spotify scripts so it's not like that's the issue.
@Googolplexed0 commented on GitHub (Jan 23, 2026):
@besweeet
This mandatory when
BYPASS_MD_APIis True, as the contents of a Playlist cannot be fetched.@stannismannis
Glad to know I am having a positive impact on your experience with music :)
This is mandatory when
BYPASS_MD_APIis True, as no track metadata can be fetched.@U2EZNeko
Planned feature, see #148. I need to fix all the bugs in new-hierarchy first, but this is next highest priority.
Overall, the
--client-idargument is only meant to be used once per Client ID, to authorize and obtain a key. After that, the key can be refreshed (effectively) forever.SAVE_CREDENTIALSshould be enabled andCREDENTIALS_LOCATION(or--creds) should be set to<your usual credentials path>\credentials<something unique here>.jsonfor each Client ID. This way each Client ID/credential pair gets its own file, instead of constantly overwriting each other. Then you just setCREDENTIALS_LOCATION(or--creds) to whichever credential file you'd like to use at runtime, loading the saved key and preventing the need for manual reauthentication every time you switch Client ID.@alexjohhh commented on GitHub (Jan 24, 2026):
I am not able to find --bypass-metadata-api int the arguments, is that still supported? thank you! trying to find my way without an api token
@besweeet commented on GitHub (Jan 24, 2026):
It's there:
Ensure you're using the efficient-api version.
@alexjohhh commented on GitHub (Jan 25, 2026):
Thanks besweeet! that was the issue, but im still running into this
@alexjohhh commented on GitHub (Jan 25, 2026):
anyone had success without the api key?
@SkilletWarez commented on GitHub (Jan 25, 2026):
try increasing your bulk wait
@jonaaa20 commented on GitHub (Jan 25, 2026):
This won't fix because he needs a Premium Account.
@SkilletWarez commented on GitHub (Jan 25, 2026):
It can bypass
Bypass in the configuration. But does not pull a metadata
@jonaaa20 commented on GitHub (Jan 25, 2026):
Nope. Doesn't work, at least not for me.
@wobblecauseimacripple commented on GitHub (Jan 26, 2026):
Zotify was working for me after working on everything, and suddenly it stopped?
This is what I get now, at all times. Any ideas on how to fix it?
@qvattr0 commented on GitHub (Jan 26, 2026):
Yeah, I've been getting this issue as well. I have a premium account and have had no issues with backing up my Spotify playlists back before the December of the previous year. I've actually had the DevAPI web app, but while troubleshooting the issue when it appeared for the first time, in my infinite lack of wisdom, I deleted the web app to see if I can create a new one. Unfortunately, I was no longer able to create a new web app after that. And since then, I was unable to back up any of my playlists and such.
@muneebmaster commented on GitHub (Jan 29, 2026):
I'm just looking to download individual songs and don't really care for metadata and/or lyrics. I don't have a DevAPI web app, only a Premium account's username and password. Is it still possible to use username/password? If so, how?
@DieselMane2006 commented on GitHub (Jan 30, 2026):
what exactly do i change how? do i replace the 4 numbers with the star? im new to this and im not sure what you mean with "change *".
do i change smth in the login ip? or do i need to change the whole ip to the one you provided? if thats even an IP, i have no idea what im talking about lol
@ilovecats4606 commented on GitHub (Jan 31, 2026):
@DieselMane2006
@DieselMane2006 commented on GitHub (Jan 31, 2026):
well, i dont have a developer id, and they dont give them out anymore, so zotify is dead for me and people without a developer ID, right?
@ilovecats4606 commented on GitHub (Jan 31, 2026):
Yes, even if I give you mine ( I wouldn't mine if I did) it must be on the same account as the Spotify Premium, which I do not have..
@ilovecats4606 commented on GitHub (Feb 26, 2026):