BUG: Spotify API persistent 401 Unauthorized (after refresh token expiration update)

Beginner Questions
,
1

:bullseye: What is your goal?

I would like to be able to connect my Spotify premium (family plan administrator) account to make scenarios.

:thinking: What is the problem?

Make can no longer re-authenticate, verify, or add a Spotify account to my Make account credentials (and I’m guessing this applies to everyone, not just me). No matter what I try, I always receive a persistent 401 Unauthorized error when trying to connect Spotify (note this is after successful Spotify logins).

Spotify’s API has changed to require authentication refresh every 6 months as described here (with a universal forced token expiration date of July 20, 2026):

https://developer.spotify.com/blog/2026-06-18-refresh-token-expiration

After much troubleshooting I suspect that Make’s enterprise Client ID may be flagged or rate-limited by Spotify following the July 20, 2026 token expiration update. Is Make aware of any blockage on their native Spotify integration?

:test_tube: What have you tried so far?

  1. First, I ensured that my Spotify premium subscription was active (no issue there)
  2. Re-authenticated Spotify account (on Make credential side)
  3. Verified Spotify account (on Make credential side)
  4. Deleted existing Spotify Make credentials connection, then re-added via a Make scenario using Spotify login portal pop-up window (not Client ID & Client secret)
  5. OAuth2.0 credentials via Client ID & Client secret as shown here: Spotify - Apps Documentation NOTE this functionality is on pause per this link, but I tried anyway: https://community.spotify.com/t5/Spotify-for-Developers/Unable-to-create-app/td-p/7283365
  6. Repeated the above on both Blink & Gecko engine browsers
  7. Repeated all steps with every browser extension disabled, cache cleared, and in incognito mode - to ensure browser configuration wasn’t the issue
4

Any updates on this?

5

None I’m aware of (other than it’s still broke, just checked).
If I discover it’s somehow resolved, I’ll give an update.
Hope to hear from the Make team before I reach out to Spotify (so I can give them more useful information).

6

Hi @here,

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 can’t give any more details at the moment, I’m afraid, but I will be back here with an update as soon as I know more :pray:

Marina :make:

7

Here my Spotify connection ended working last Saturday, 25th July.
Also tried to create a new API; it is somehow related to the redirect URL, I guess.

What I noticed is that the redirect URL is not beginning with /spotify2 at the end but with only /spotify:
…gromat.com%2Foauth%2Fcb%2Fspotify%2F&state=212d…

8

This issue has now been resolved, with a fix applied to all zones, so everything should be working now :white_check_mark:

image (17)
image (17)1718×1371 241 KB

9

You’re awesome, Marina. Going to try this now :smiley:

10

Can confirm that it is now working!!

I did end up having to recreate my scenarios to get them linking properly (some modules required connecting to Spotify twice), not a big deal.

To be seen if Make (or Spotify) will alert users that their API access will expire after 6 months. Worst case is a perpetual reminder on my calendar to keep this working I guess.

Thanks for the help!!