Announcements
Happy Values Week! Today we celebrate *Support* in the Spotify Stars Program!

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

Web API authetication after 2025/04/09

Web API authetication after 2025/04/09

Plan

Premium

Device

Macbook Air

Operating System

macOS 10.15

 

My Question or Issue

After the new rollout of Increasing the security requirements for integrating with Spotify, apps with custom URI scheme like this:

com.example://callback

can no longer be authenticated, as the authorization returns:

INVALID_CLIENT: Insecure redirect URI

 

This shouldn't be the case, as the documentation clearly mentions that 

  • com.example://callback can still be used as before

I'm using Authorization Code with PKCE Flow

Reply
2 Replies

Same here, "Insecure redirect URI" is returned while using custom URI schemes.

Also having this issue as well. It is breaking some of my redirect URIs

Suggested posts