Enable the endpoints you need
Every endpoint the plugin registers is disabled by default. A disabled endpoint returns 404, exactly as though it did not exist. This page is the one to read before you conclude something is broken.
Why they ship off
Section titled “Why they ship off”Your site’s members, their profile fields, their private messages and their orders are all reachable through these routes. Shipping them all open would mean installing a plugin and silently exposing member data over the public internet. So the plugin opens nothing, and you allow exactly what your app uses.
Switch them on
Section titled “Switch them on”- In WordPress, go to Memberside → REST API.
- Find the group for the feature you are placing.
- Switch on the endpoints in it. Groups can be toggled whole.
- Save.
Changes apply immediately. There is no cache to clear and no rebuild needed — the app reads live, so a screen that was empty a moment ago works on the next pull-to-refresh.
Enabling endpoint groups in Memberside → REST API
record → src/assets/media/enable-endpoints.mp4
A sensible starting set
Section titled “A sensible starting set”If you are working through the Quickstart, enable these five and add more as you place features:
| Group | Covers |
|---|---|
| Authentication | Sign in, register, forgot password, sign out |
| Users | Reading and updating profiles, a member’s posts and comments |
| Directory | The member directory listing and its filters |
| Forms | Ultimate Member profile and registration forms |
| Appearance | Profile tabs, account tabs and other layout the app reads from your site |
The full catalogue
Section titled “The full catalogue”Thirty groups, each tied to a plugin or a feature area. Groups whose backing plugin is not installed do not appear at all.
| Authentication | Default Authentication | Social Login |
| Users | Uploaders | Account |
| Directory | Search | Content |
| Forms | Appearance | Site |
| Messaging | Better Messages | ACF |
| Followers | Friends | Groups |
| BuddyPress Groups | BuddyPress Activity | Notes |
| Notifications | Photos | Badges |
| Billing | Payment Methods | Products |
| Cart | Realtime | Wall |
Default Authentication is deliberately separate from Authentication. Authentication is sourced to Ultimate Member; Default Authentication is WordPress core sign-in and works on a site that has never had Ultimate Member installed. The Default Login feature needs the second, not the first.
Wall is the memberside/v2 namespace rather than v1. It backs the news
feed, activity threads and group discussions.
The full feature-to-endpoint matrix lists which groups each feature needs.
Enabling more later
Section titled “Enabling more later”You do not have to plan this up front. Place a feature, find its screen empty, come back and switch its group on. The builder also tells you: a feature whose backing plugin is missing is greyed out in the sidebar, which is a different problem from an endpoint being off — see A feature is greyed out.
When it does not work
Section titled “When it does not work”| Symptom | Cause | Fix |
|---|---|---|
| A screen is empty, and the API returns 404 | The endpoint group is off | Switch it on under Memberside → REST API |
| A group you expected is not in the list | Its backing plugin is not active | Activate the plugin, then reload the screen |
| Everything returns 404, including enabled routes | Permalinks are set to Plain | Settings → Permalinks, choose any other option |
| A form-driven screen is empty although Forms is on | The form itself is still hidden from the API | Make forms and directories visible |
Make your forms and member directories visible — a separate switch that catches people who have done everything on this page.