Discord
Members sign in with their Discord account, in the system browser.
Before you start
Section titled “Before you start”| Console | Discord Developer Portal |
| Endpoint group | Social Login |
| Returned, and verified — Discord can match an existing account | |
| Signs in | In the browser |
Create the application
Section titled “Create the application”-
Open the Discord Developer Portal and create a New Application.
Name it what members should see on the authorisation screen.
-
Open OAuth2 in the sidebar.
-
Add a redirect under Redirects: the address from Memberside → API Keys → Social Login → Discord, which looks like
https://yoursite.com/wp-json/memberside/v1/social/callback/discord. -
Save changes. Discord discards an unsaved redirect without complaining.
-
Copy the Client ID, then Reset Secret and copy the client secret.
You do not need a bot, and you should not add one. Sign-in uses the identify
and email scopes; a bot token is a different credential for a different job.
Discord accounts without a verified address
Section titled “Discord accounts without a verified address”Discord requires a verified email on any account that can join servers, so in practice every member you meet has one. An account that has not verified its address is refused rather than let through unverified.
What to paste into Memberside
Section titled “What to paste into Memberside”Under Memberside → API Keys → Social Login → Discord:
| Field | Value |
|---|---|
| Client ID | The Client ID |
| Client secret | The client secret |
When it does not work
Section titled “When it does not work”| Symptom | Cause | Fix |
|---|---|---|
| “Invalid OAuth2 redirect_uri” | The redirect was added but not saved | Add it and press Save changes |
| The authorisation screen shows the wrong name | The application name | Rename the application |
| The secret stopped working | Somebody reset it | Reset it again and paste the new one |
| A member is refused | Their Discord address is unverified | They verify it with Discord |