Persistent 429 Error for Personal App in Development Mode (Client ID: 6088d0c...)

[braydonmacmaste]

Required Info:

Plan: Premium

Country: Canada

Device: Asus ZenBook Flip UX360UA

Operating System: Windows 10 Pro (WSL2 / Ubuntu 24.04)

My Question or Issue:

Hi, I am reaching out after an extensive troubleshooting session with standard support (Tiffany M).

Reference Support Chat ID: 17898cfe-1e4e-48b2-95fb-636813651a01

The Problem: My personal CLI client (ncspot) is receiving an immediate 429 Too Many Requests error upon launch.

My Setup:

Client ID: 6088d0c7cb444b2b8bf9eb9a973132d

Status: Active / Development Mode

API: Web API

Evidence: My Developer Dashboard shows a healthy 'Active' status with no warnings. However, even after rotating my Client Secret and ensuring zero active requests, the 429 block persists. As an individual developer, I am unable to access the Quota Extension form in my settings to resolve this.

Can an engineer please use the provided Chat ID to review my case and check if my Client ID or IP has been flagged by an automated system? I am looking for a rate-limit reset for this ID so I can finish my initial library sync. Thanks.

[Oniriel]

I have the same issue, in developement mode, if you reach the 429 once you get stuck for a very long time or even forever (no sure)

the Retry-after is not relevant by any means, and the app get stuck. Yesterday I had to delete the APP and recreate a new one to bypass the issue. But since we are limited at 24h for one app creation this is not a valid solution at all even less when in developement.

I mean I am ok with the 429 but the way it is handled is unreasonnable, how are we suppose to make our app work when the batch isnèt working and we hit the 429 so fast and then are blocked from working

I don't get it

[Oniriel]

does anybody has a solution for this ? I still receive 429 too many requests 3 hours after the problem started to occure

fill like I will have to delete the app and recreate it again in 24h just because of this

[Oniriel]

a solution for people hitting this issue, I added the name and artist manually in my own data

Note : Gemini or ChatGPT are actually capable of reading the track URL and extract the data for you which is convenient. and then you don't have to call the API to get the track info (which is the one returning 429 all the time)

the play and stop calls works properly and aren't affected.