Authentication API failing in production right now

Reply
Highlighted

Authentication API failing in production right now

Music Fan

Hey Spotify,

 

I'm using your authentication api to register all my users and everything worked fine since yesterday. I just launced a big ad campaign and suddenly no new users or current ones can sign in and all the api returns are: 400 - 'invalid_request' without any error description or ENOTFOUND accounts.spotify.com. This happens when I'm requesting the authorization_code via: https://accounts.spotify.com/api/token.

 

But as I said everything worked fine since yesterday.

What is wrong?

 

I sincerely hope you can help me out. I'm losing users by the minute.

Regards,

 

Anker

 

36 Replies
Highlighted

Re: Authentication API failing in production right now

Visitor
I'm experiencing the exact same issue right now. This is very troublesome and it's costing me a lot of users. What is happening?
Highlighted

Re: Authentication API failing in production right now

Music Fan

Me too. I'm getting an authorisation code but not able to swap it for an access token. What is the response you guys see? is it similar to this =>

 {'error': 'invalid_request', 'error_description': ''}

Highlighted

Re: Authentication API failing in production right now

Music Fan
Yes excactly. That or ENOTFOUND accounts.spotify.com. Both are happening for me. It must be a problem on Spotify's end since it worked fine up until today.
Highlighted

Re: Authentication API failing in production right now

Music Fan

@Spotify you are a brilliant company, with an amazing bunch of dev friendly APIs but please fix this asap coz we be crapping our pants 😛

Highlighted

Re: Authentication API failing in production right now

Music Fan

@Spotify and @SpotifyJosh,

 

15 hours have gone by and still, nothing has happened. The error is still occurring and while I'm trending on the danish App Store none of my new users can sign up nor sign in. This is catastrophic for my whole startup. I sincerely hope you can help get this resolved asap as I'm having an event in a couple of hours with 1000's of new users. Please help.

 

Regards,

 

Anker

Highlighted

Re: Authentication API failing in production right now

Spotify
Spotify

Hi @ankerbachryhlSorry to hear about the difficulty you have been having here. The OAuth endpoints are working normally, from what we can see. Are you receiving the ENOTFOUND error most often, or are you receiving the 400 series error more often? Is your app open source by chance?

Highlighted

Re: Authentication API failing in production right now

Music Fan

Hi @spotifyjosh

 

Thank you for your reply. I'm afraid my app is not open source, but I can provide a detailed description here. I can't include any code here though, since everytime I try it gets marked as spam and my message gets deleted. So please provide an e-mail if you need my API calls.

 

Today I'm receiving the 400 error most often. I receive the error with the following response: { error: 'invalid_request', error_description: '' }

I'm only receiving the error when I try to call the https://accounts.spotify.com/api/token endpoint with the grant_type of "authorization_code". Every other web API call is working as usual and I'm able to receive the authorization code too. It's only when trying to get the token it fails. 

As I said earlier everything was working fine up until 3pm yesterday where I received the 400 error for the first time. It has then failed since. I have not changed any code or done any server work. Hence why I believe it must be an error on the Spotify API OAuth side. 

Highlighted

Re: Authentication API failing in production right now

Spotify
Spotify

I hear you - that sounds frustrating @ankerbachryhl. We have some open source code samples that use the authorization code flow. Have you tried remixing this Glitch sample app? It might be that you can compare this implementation with your app and find the problem that way.

Highlighted

Re: Authentication API failing in production right now

Music Fan

hey @spotifyjosh. This seemed to be working perfectly until yesterday. Absolutely nothing has changed in the code from our end. We've checked everything. the client id, secret, scopes, urls.We also are able to get an authorisation code but token swap is failing. Also played around with different accounts but to no avail. I seem to be consistently getting the following error : {'error': 'invalid_request', 'error_description': ''}.   What's peculiar is that there is no description. While we are not in the anxious predicament that @ankerbachryhl finds himself in, it is nonetheless frustrating since our dev work has been put on hold. 

SUGGESTED POSTS