WordPress.com

Members sign in with their WordPress.com account, in the system browser.

Before you start

Console	WordPress.com applications
Endpoint group	Social Login
Email	Returned, and verified — WordPress.com can match an existing account
Signs in	In the browser

This is not sign-in for your own WordPress site

WordPress.com accounts are Automattic accounts — the same ones used for Jetpack, Gravatar and Tumblr. Members of your own self-hosted WordPress site sign in through Login or Default Login, which need no provider at all.

Offer this when your community already has WordPress.com or Gravatar accounts, not as a way of signing into the site the app is built from.

Create the application

1. Open developer.wordpress.com/apps and create a new application.

2. Fill in the Name and Description. Members read both when authorising.

3. Set the Website URL to your site.

4. Set the Redirect URL to the address from Memberside → API Keys → Social Login → WordPress.com, which looks like https://yoursite.com/wp-json/memberside/v1/social/callback/wordpress.

   Note the last segment is wordpress, not wordpress.com.

5. Choose Web Client as the type.

6. Copy the Client ID and Client Secret.

Memberside requests the auth scope, which restricts the token to reading the member’s own account. Without it, a WordPress.com token reaches every site the member has — far more than signing someone in requires.

What to paste into Memberside

Under Memberside → API Keys → Social Login → WordPress.com:

Field	Value
Client ID	The Client ID
Client secret	The Client Secret

When it does not work

Symptom	Cause	Fix
“redirect_uri is invalid”	The last segment is wordpress.com instead of wordpress	Copy it from the API Keys screen
Members of your own site cannot sign in	This provider signs in WordPress.com accounts	Use Login or Default Login
“unauthorized_client”	The application type is not Web Client	Recreate it as one
A member has no WordPress.com account	Nothing to fix on your side	Offer another provider as well