Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Can't access API anymore, did I exceed limits?

Can't access API anymore, did I exceed limits?

Plan

Free/Premium

Country

 

Device

(iPhone 8, Samsung Galaxy 9, Macbook Pro late 2016)

Operating System

(iOS 10, Android Oreo, Windows 10,etc.)

 

My Question or Issue

 

Hi folks, I was starting to make a music search app and was able to keep querying the API for around 2 days, then suddenly my api requests are no longer working, returning: array(1) { ["error"]=> array(2) { ["status"]=> int(401) ["message"]=> string(17) "No token provided" } } No tracks found for the genre: indie 

 

I saved multiple to working api request files over the 2 days and none of them are working so I don't think it is a code issue as my scripts were working fine.

 

I've tried to create several new apps using new client id and secret but this hasn't helped.

 

If I did exceed rate limits how do I find out?  Would signing up to spotify premium help? I do want to anyway to get better control of the sdk music player.

 

Thanks,

 

Kias, Australia

 

 

 

 

Reply
3 Replies

I think the refresh token is expired. You should re-authenticate your account.

XimzendSpotify Star
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
Note: I'm not a Spotify employee.

Probably. The app/service need to retain the refresh token between different sessions. 

In this case look like the app didn't save it. 

That would explain the "No token provided".

I think after few wrong attempt Spotify servers just remove the main authorization code and the app need to repeat the login/permission. 

No need to feel bad about it. I see a lot of big companies implementations  messing up  the refresh token cycle. 

hmm possibly.. I'm running a function to generate an auth token so that shouldn't be an issue... but then perhaps I still don't fully understand.  The only way around it was to create another account... which is silly because I signed up to spotify premium in hopes that would fix the other account.  I'll have to double check if still locked out on first account. I wasn't using rate limiting practices yet so this might explain it.

Suggested posts