Announcements

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

"User not registered in the Developer Dashboard" on user's requests

"User not registered in the Developer Dashboard" on user's requests

It seems that the API has been incorrectly reporting the "User not registered in the Developer Dashboard" error on every other request our users have been trying to make (while trying to retrieve their playlists, for example).
This doesn't really make sense since this was not the case as of yesterday and since we haven't done any recent changes whatsoever on our code. It would seem that this could be an issue on Spotify's end, and we'd appreciate if any additional info regarding possible workarounds could be provided. As always, thanks.

Reply
5 Replies

Do you have a quota extension?

Do you by any chance mean this? https://developer.spotify.com/documentation/web-api/concepts/quota-modes

 

Wasn't aware of this limitation, seems to be a rather new thing, right?

 

Anyway, if that's the case, then no, I don't have a quota extension.

 

While checking the prerequisites over at the application form for the extended quota it would seem like they intend to curb all support to home automation projects, but that doesn't seem right... does it?

There must be something I've missed, because from where I'm standing it looks like this'll be a huge (bad) thing for all third-party integrations that rely on the API.

 

In case this is exactly what they seek to accomplish by making these changes, I'd very much like to know about any alternatives for cases like mine (home automation app, reasonable amount of users, suddenly deprived of any possibility of integration with the platform).

There is no alternative. You must get a quota extension granted if you want other users to be able to use your app.

Try adding a username to the authorization request.

I use Spotipy in Python, so here's an example of what I mean

import os
from dotenv import load_dotenv  # pip install python-dotenv

load_dotenv("path/to/your/.env")

CLIENT_ID = os.getenv("Client_ID")
CLIENT_SECRET = os.getenv("Client_Secret")
REDIRECT_URI = os.getenv("Redirect_URI")
DISPLAY_NAME = os.getenv("Display_Name")


def authorization_flow(scope=""):
    import spotipy
    from spotipy.oauth2 import SpotifyOAuth

    # Create a Spotify API Client
    sp = spotipy.Spotify(
        auth_manager=SpotifyOAuth(
            client_id=CLIENT_ID,
            client_secret=CLIENT_SECRET,
            redirect_uri=REDIRECT_URI,
            scope=scope,
            username=DISPLAY_NAME,  # email might also work
        )
    )
    return sp


if __name__ == "__main__":
    sp = authorization_flow(scope="playlist-modify-private")
    user = sp.current_user()
    user_id = user["id"]

:

 

 

The username is not used in the authorization request. the `username` parameter in `SpotifyOAuth.init` is only used by spotipy, not Spotify.

Suggested posts

Let's introduce ourselves!

Hey there you,   Yeah, you! 😁   Welcome - we're glad you joined the Spotify Community!   While you here, let's have a fun game and get…

ModeratorStaff / Moderator/ 4 years ago  in Social & Random