Spotify

Members sign in with their Spotify account, in the system browser.

Before you start

Console	Spotify Developer Dashboard
Endpoint group	Social Login
Email	Returned, but not verified — cannot match an existing account
Signs in	In the browser

Create the app

1. Open the Spotify Developer Dashboard and press Create app.

2. Fill in the app name and description. Members read both when authorising.

3. Add the Redirect URI: the address from Memberside → API Keys → Social Login → Spotify, which looks like https://yoursite.com/wp-json/memberside/v1/social/callback/spotify. Press Add — a URI typed but not added is discarded on save.

4. Tick Web API under which APIs you plan to use.

5. Save, then open Settings and copy the Client ID. Press View client secret to reveal the secret.

Sign-in uses the user-read-email and user-read-private scopes. Nothing about playback or library access is requested.

Development mode limits you to a list

A new Spotify app only works for users you name

Spotify apps start in development mode, where only accounts added under Settings → User Management can authorise — up to 25 of them. Every other member sees a failure, which reads as a broken button.

Applying for extended quota mode removes the limit. Until then, social sign-in with Spotify works for the people on that list and nobody else.

What to paste into Memberside

Under Memberside → API Keys → Social Login → Spotify:

Field	Value
Client ID	The Client ID
Client secret	The client secret

When it does not work

Symptom	Cause	Fix
Works for you, fails for members	The app is in development mode	Add them under User Management, or apply for extended quota
“INVALID_CLIENT: Invalid redirect URI”	The URI was typed but never added	Add it, then save
The secret is not visible	It is hidden behind View client secret	Press it
A second account is created for an existing member	Spotify’s email is unverified, so matching is refused	Have them sign in first, then link