Spotify connection fails with 401 Valid user authentication required

:bullseye: What is your goal?

Connection to Spotify

:thinking: What is the problem & what have you tried?

Hello Make Community,

I’m having trouble connecting Spotify in Make and would appreciate your help.
It worked till last week.

Issue

When I try to create a new Spotify connection, I receive the following error:

Unexpected error: {"status":401,"message":"Valid user authentication required"}

What I’ve already verified

  • I created a completely new Spotify Developer App.
  • I’m using the new Client ID and Client Secret in Make.
  • The Spotify Developer App contains the following Redirect URI:
https://www.integromat.com/oauth/cb/spotify/
  • The Redirect URI matches the one Make sends to Spotify.
  • The Spotify user I’m logging in with is the same user that is listed in the app’s User Management.
  • I deleted the old Make connection and created a completely new one.
  • I even created a brand new Make scenario containing only a Spotify module.

Authorization Request

The authorization request sent by Make is:

https://accounts.spotify.com/authorize?redirect_uri=https%3A%2F%2Fwww.integromat.com%2Foauth%2Fcb%2Fspotify%2F&state=4c167097c8b3a6384e7d&response_type=code&client_id=954a9070ec234d3f9fadd41b77d77b66

Spotify accepts the Redirect URI (if it is not configured correctly, Spotify returns the expected “redirect_uri: Not matching configuration” error).

However, after authentication, Make reports:

Unexpected error: {"status":401,"message":"Valid user authentication required"}

My question

Could you please verify whether this is an issue with the Spotify connector or the OAuth token exchange on Make’s side?

Is there anything else required for the current Spotify integration besides:

  • a valid Spotify Developer App,
  • matching Redirect URI,
  • correct Client ID/Secret,
  • and an authorized Spotify user?

Thank you for your help.

Hi @marexx

It’s not just you – a few other users have been experiencing an issue with Spotify recently. So far, we have not found the root cause on our side causing this issue. It looks like it might be on Spotify’s side, but we are looking into this problem now. I will be back here with an update as soon as I know more :pray:

Marina :make: