Twitch
Members sign in with their Twitch account, in the system browser.
Before you start
Section titled “Before you start”| Console | Twitch Developer Console |
| Endpoint group | Social Login |
| Returned, and verified — Twitch can match an existing account | |
| Signs in | In the browser |
Create the application
Section titled “Create the application”-
Open the Twitch Developer Console and choose Register Your Application.
-
Name it. Twitch requires the name to be unique across all of Twitch, so a generic community name may be taken.
-
Add the OAuth Redirect URL: the address from Memberside → API Keys → Social Login → Twitch, which looks like
https://yoursite.com/wp-json/memberside/v1/social/callback/twitch. -
Choose a category. Website Integration fits a community site.
-
Create, then open Manage and copy the Client ID.
-
Press New Secret and copy the client secret.
Sign-in uses the user:read:email scope, which returns the member’s address
alongside their profile.
What to paste into Memberside
Section titled “What to paste into Memberside”Under Memberside → API Keys → Social Login → Twitch:
| 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 |
|---|---|---|
| The application cannot be registered | Two-factor is not enabled on your Twitch account | Enable it, then reload the console |
| “The name is already taken” | Twitch names are globally unique | Pick another |
| “redirect_uri does not match” | The address differs from the registered one | Copy it again |
| No email comes back | An older application without the email scope | Recreate the secret and try again |