Not able to authorise developer app

[VampyAfterDark]

Plan

Premium

Country

South Africa

Device

PC 

Operating System

Windows 11

My Question or Issue

Hello Spotify Support Team,

I’m reaching out for assistance with integrating Spotify into my Stream Deck. I’m following the standard setup process, which requires creating a Spotify app and using my Client ID and Client Secret for authorization.

I created an app successfully and entered the required details, but when I attempt to authorize the connection, I repeatedly receive an error page. I’ve tried multiple redirect URI combinations that were recommended in tutorials, as well as the URL formats shown in the Spotify API documentation, but I continue to encounter the same issue.

I’ve attached two screenshots for reference:

1. The error page that appears when I try to authorize.

2. The page showing the redirect URIs I have configured, along with the APIs I’ve enabled.

Could you please advise on what might be causing this authorization error, or what I may need to adjust in my app settings or redirect URIs to get the Spotify integration working with the Stream Deck?

Thank you in advance for your help!

[ethanop]

Hi there! 👋

It looks like you’re running into issues authorising your Spotify developer app when trying to integrate with your Stream Deck, this is something many developers face, and it typically comes down to the OAuth setup and redirect configuration, not a bug in the Spotify API itself.

Here are the most common causes and how to fix them:

1. Redirect URI must match exactly
Spotify strictly enforces that the redirect URI in your authorization request exactly matches one of the URIs you’ve registered in the Spotify Developer Dashboard. This includes:

• Protocol (https:// vs http://)
• Trailing slash (/callback vs /callback/)
• Any ports (e.g., :3000)

If there’s even a minor difference, you’ll get an error page instead of a successful authorization.

2. Use the correct OAuth flow
For desktop or web integrations, you should be using the Authorization Code flow (or Authorization Code with PKCE if the secret can’t be stored securely). The deprecated implicit grant flow is no longer supported in most cases. 

3. App development mode restrictions
If your app is still in development mode, Spotify sometimes restricts which users can authorize it until it’s reviewed/approved or moved to extended quota mode. This could lead to authorization failures for anyone other than the app owner.

4. Double-check your scopes and credentials
Make sure:

• Your client ID and client secret are correct.
• You’re requesting the proper scopes that your integration needs.
• The authorization request is structured according to Spotify’s docs.

If you’re feeling stuck with the implementation details, you can hire web developers from CMARIX Infotech who is specialize in OAuth integrations and API workflows. Getting expert help can save you a lot of time troubleshooting and ensure your app’s authentication is robust and reliable.