Connect your WordPress site

Connecting tells an app which site it belongs to. Once connected, the builder reads your active plugins to decide which features you can place, and the preview renders against your real content.

Create an application password

Memberside signs in as a WordPress user using an application password. It never asks for, and cannot use, your account password.

1. In WordPress, go to Users → Profile.

2. Scroll to Application Passwords.

3. Enter a name — Memberside is a good one — and select Add New Application Password.

4. Copy the value that appears. It is shown once. It looks like six groups of four characters separated by spaces, and the spaces are part of it.

Use a dedicated application password rather than reusing one. You can revoke it at any time from the same screen, which cuts the app’s access without changing your own password or affecting anything else.

Which user to connect as

Connect as an administrator. The builder reads your active plugin list and your appearance settings, which needs administrative capability. This is the identity the builder uses to configure the app — it is not the identity your members sign in as.

Connect the app

1. In the builder, open the app and go to the connection step. On a new app this is step two of onboarding; on an existing one it is Settings → Connection.

2. Enter your Site URL, including https://. Use the exact address your site answers on, matching www or its absence.

3. Enter your WordPress username — the username, not the email address.

4. Paste the application password.

5. Select Test & continue.

A green Connected as… panel naming the user means the plugin answered and the credentials were accepted. The builder stores the connection and moves on.

Connecting a WordPress site to an app

record → src/assets/media/connect-wordpress.mp4

Connecting a WordPress site to an app

What the builder reads

On connecting, and on each reload afterwards, the builder asks your site for:

• Active plugins, which decide which feature cards are available.
• Plugin versions, checked against the range Memberside has been tested with.
• Capabilities — whether push, OneSignal and Turnstile keys are configured.
• Forms, directories and account tabs that have opted into the API.

Secrets are never returned. The capabilities response says whether a key is present, not what it is.

Changing or revoking access

To point an app at a different site, or to rotate the password, return to the same screen and connect again. To cut access entirely, revoke the application password in WordPress under Users → Profile → Application Passwords. The app stops being able to read your site immediately; builds already downloaded keep working until they next need the API.

When it does not work

Symptom	Cause	Fix
Ultimate Member REST API not found	The Memberside plugin is not active on the site you entered	Install the plugin, and check the URL for a typo
Those credentials were rejected	Wrong username, or the application password was mistyped	Use the username rather than the email, and paste the password including its spaces
Connection failed or Could not reach that site	The URL is wrong, the site is not public, or it is behind HTTP auth	Open the URL in a browser from outside your network
Connects, but every feature card is greyed out	The Site endpoint group is off, so the plugin list cannot be read	Enable it under Memberside → REST API
Connects as the wrong person	The application password belongs to another user	Create one under the administrator account you intend to use

A local site on localhost, or one reachable only over a VPN, cannot be connected. Memberside calls your site from its own servers.

Next

Place your first features.