Skip to content

Facebook

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

ConsoleMeta for Developers
Endpoint groupSocial Login
EmailReturned, and treated as verified — Facebook can match an existing account
Signs inIn the browser
  1. Open Meta for Developers and create an app.

    Choose Authenticate and request data from users with Facebook Login when asked what you are building.

  2. Add the Facebook Login product to the app.

  3. Open Facebook Login → Settings.

  4. Add the redirect address under Valid OAuth Redirect URIs: the string from Memberside → API Keys → Social Login → Facebook, which looks like https://yoursite.com/wp-json/memberside/v1/social/callback/facebook.

  5. Leave “Login with the JavaScript SDK” off. The sign-in happens server-side.

  6. Open App settings → Basic and copy the App ID and App secret.

  7. Fill in the Privacy Policy URL. Meta will not let the app go live without one, and the App Store asks for the same URL.

Under Memberside → API Keys → Social Login → Facebook:

FieldValue
Client IDThe App ID
Client secretThe App secret

Facebook requires a confirmed address on the account, and Memberside treats the address it returns as verified on that basis. It is an inference from Facebook’s own account rules rather than a claim Facebook makes in the response. If your community’s security posture makes that inference unacceptable, do not offer Facebook as a way of matching existing accounts.

SymptomCauseFix
Works for you, fails for membersThe app is in Development modeSwitch it to Live
“URL Blocked”The address is not in Valid OAuth Redirect URIsAdd it exactly
No email comes backThe member denied the email permissionThey can re-authorise and allow it
“App Not Setup”Facebook Login was never added as a productAdd it
Cannot switch to LiveThe Privacy Policy URL is emptyFill it in under Basic settings