Redirect URLs

Every provider needs to know where to send a member back to after they approve your app. That address is on your own site, and it differs between providers only in its last segment.

The address

https://yoursite.com/wp-json/memberside/v1/social/callback/PROVIDER

Replace yoursite.com with your site and PROVIDER with the provider’s id — the same word as the last segment of its documentation page. For Google:

https://yoursite.com/wp-json/memberside/v1/social/callback/google

You do not have to assemble it by hand. Each provider’s section under Memberside → API Keys → Social Login shows the exact string for your site with a copy button beside it.

Copy it rather than typing it

Providers compare this string character for character. A trailing slash, http where you registered https, www. on one side and not the other, or a permalink structure that gives your site a different REST prefix — each produces the same unhelpful error, and none of them look wrong when you read them back.

What each provider calls the field

The address is the same; the label above the box is not.

Called	At
Authorized redirect URI	Google
Return URL	Apple
Valid OAuth Redirect URI	Facebook
Callback URI	X, LinkedIn
Redirect URI	Microsoft, Discord, Slack, Amazon, Spotify, Dropbox, Patreon
Authorization callback URL	GitHub
Redirect URI	GitLab
OAuth Redirect URL	Twitch
redirect uri	Reddit
Redirect URI	Yahoo, Pinterest, WordPress.com

Several providers accept a list. Adding your staging site’s address alongside your live one is fine and saves maintaining two applications.

Your site must be reachable over HTTPS

The provider’s servers open this address themselves. A site behind a firewall, on a local hostname, or with an expired certificate cannot complete a sign-in, and the failure appears on the provider’s side where the message is least useful.

This is why social sign-in cannot be tested against a purely local development site for most providers.

Apple asks for a second address

Apple verifies that you control the domain before it will accept it in a Services ID. It offers a file to download and expects to find it at a fixed path on your site.

The plugin serves that file for you once you paste its contents into the Domain verification file field — you do not have to upload anything. The address Apple checks is shown next to the field, with its own copy button. See the Apple guide.

When it does not work

Symptom	Cause	Fix
“redirect_uri_mismatch” or similar	The registered address differs from the one sent	Copy it again from the API Keys screen
The address contains index.php?rest_route=	Your permalinks are set to Plain	Either register that address, or change permalinks
It works on the web and not in the app	The app uses the same address; the fault is elsewhere	Check the provider’s credentials
Apple rejects the domain	The verification file is not being served	Paste its contents into the Domain verification field
A change to the address has no effect	Some providers cache for a few minutes	Wait, then try in a fresh browser session

Next

Pick your provider from the grid on Social sign-in.