287 endpoints and 408 operations across two namespaces, buddynext/v1 (Free) and buddynext-pro/v1 (Pro), spanning 29 domains from the feed to membership, payments, AI, and analytics. WordPress Application Password auth, an App Shell bootstrap, and outgoing webhooks. It is the same layer the BuddyNext front end uses, and the one a native app will use.
The buddynext/v1 namespace ships with every install; buddynext-pro/v1 activates with BuddyNext Pro. This reference covers both.
POST /wp-json/buddynext/v1/posts Authorization: Basic <app-password> Content-Type: application/json { "content": "Hello, community", "space_id": 128 } 201 Created { "data": { "id": 9013, "status": "published", "created_at": "2026-07-14T10:42:00Z" } }
287
REST endpoints
Free + Pro
408
operations
GET / POST / PUT / DELETE
What you get
No API add-on, no separate activation. Every BuddyNext install ships the full free REST layer, Application Password auth, and the webhook system from the start; BuddyNext Pro extends it with the buddynext-pro/v1 namespace.
Every data type - feed, posts, members, profiles, spaces, messaging, moderation, notifications - is reachable over REST. Free ships 218 endpoints under buddynext/v1; Pro adds the buddynext-pro/v1 namespace for 287 in total. It is the same layer the BuddyNext front end uses, and the one a native app will use.
Non-browser clients authenticate with a WordPress Application Password over HTTP Basic. Logged-in browser clients use the WordPress auth cookie plus an X-WP-Nonce header. No custom token server to run.
One call to the App Shell surface returns the navigation and context a client needs to render its first screen, so app startup is a single round trip instead of a waterfall.
Register webhook endpoints, then read a full per-endpoint delivery log and fire a test delivery, all from the API. Diagnose an integration without guessing what your server received.
The Auth domain covers registration, login, lost password, email and password changes, and two-factor with backup codes, so a companion app never has to reimplement account security.
The front end is built on the WordPress Interactivity API - ES modules, no React, no jQuery, no build step. It consumes the exact same REST surface documented here.
29 API domains
The 408 operations are organized into 29 domains across two namespaces. The numbers below are the exact operation counts from the live spec, not estimates. Domains marked Pro require BuddyNext Pro.
Profiles, custom fields, the member directory, member types, avatars, and account settings. The largest surface in the API.
Public, private, and secret communities: create them, set privacy, manage members and moderators, and run the built-in forum.
The activity feed and everything in it: composer, reactions, comments, polls, shares, bookmarks, and mentions.
Registration, login, lost password, two-factor, email and password changes, and Application Password management.
The report button, the moderation queue, user actions, appeals, and content safeguards, all over REST.
In-app notifications and preferences: read state, counts, channels, and per-type delivery settings.
Site-wide search across members, posts, and spaces, plus hashtag discovery and trending topics.
Following, connections, follow requests, blocking, and presence, the relationships that make a community.
Uploads, albums, and media attachments for posts and profiles, with per-item access control.
Register outgoing webhook endpoints, inspect the delivery log, and fire a test delivery from the API.
App config and string bundles a client reads on launch, community-admin role changes, and a member’s own standing.
The bootstrap surface a client calls on launch, including navigation, to hydrate the whole app in one place.
Owner-only utilities such as slug availability checks, used by the front-end management screens.
Broadcast campaigns and multi-step drip sequences to members, with scheduling, segments, and delivery tracking over REST.
Moderation rules, keyword filters, bulk actions, and automated enforcement beyond the free report queue.
Paid membership plans, checkout, entitlements, and content protection, so access tiers are driven entirely by the API.
Richer discovery with saved searches and expanded filters across members, posts, and spaces.
Community metrics and reporting: growth, engagement, and activity trends read straight from the API.
Native mobile push tokens, delivery, and per-device preferences for a companion app.
Owner-side member administration: roles, bulk operations, and lifecycle actions from the API.
Event RSVPs and headcounts by member or space, plus plan-change quotes and switches for a member’s own subscription.
Bridges to the rest of the Wbcom suite, wired and toggled over REST.
Pro extensions to the member surface, layered on top of the free profile API.
Pro additions to the activity feed, available when BuddyNext Pro is active.
Pro trust-and-safety endpoints that extend the free moderation surface.
Payment and gateway endpoints backing membership and monetization.
Realtime presence and live-update endpoints for responsive clients.
Owner-side member search, backing the Pro management screens.
Schedule a post to publish to the feed at a future time.
Authentication
BuddyNext uses the auth WordPress already ships. A native app or integration sends an Application Password over HTTP Basic. A logged-in browser sends the auth cookie plus an X-WP-Nonce header. Nothing custom to run or rotate.
# Non-browser client: Application Password GET /wp-json/buddynext/v1/notifications Authorization: Basic base64(user:app_pw) # Logged-in browser: cookie + nonce GET /wp-json/buddynext/v1/feed X-WP-Nonce: <wp_rest nonce> 200 OK { "data": [ ... ], "meta": { ... } }
Outgoing webhooks
Register webhook endpoints over the API, then read a full delivery log per endpoint and fire a test delivery on demand. Build an integration you can actually debug, without guessing at what your server received.
Webhook operations
9 in Free/webhooks /webhooks /webhooks/{id} /webhooks/{id} /webhooks/{id} /webhooks/{id}/log /webhooks/{id}/test Register endpoints, inspect the delivery log, and send a test delivery, all over REST.
Platform depth
The reference is generated from the live routes, the response envelopes are consistent, and the whole surface is designed for external consumers, from a mobile client to a moderation dashboard.
The OpenAPI document is generated from the plugin route registry by bin/gen-openapi.php, so the reference never drifts from what the server actually registers.
List, single, and error responses follow a predictable shape across every domain, so a client can parse any endpoint the same way.
Application Password auth, an App Shell bootstrap, and full account security make a mobile or desktop client a first-class consumer, not an afterthought.
The report queue, user actions, appeals, and safeguards are all API-driven, so trust and safety tooling can be built on the same contract.
Every webhook endpoint keeps a delivery log you can read back over the API, plus a one-call test delivery to validate your receiver.
BuddyNext is GPL-2.0-or-later and runs on your own WordPress. The API is yours to extend with standard register_rest_route hooks.
Two ways. Non-browser clients (a native app, a server integration) send a WordPress Application Password over HTTP Basic auth. Logged-in browser clients send the WordPress auth cookie plus an X-WP-Nonce header for the wp_rest action. There is no separate token server to run.
The free buddynext/v1 API is active as long as BuddyNext is installed and activated. Its 218 endpoints register automatically on rest_api_init, with no add-on and no toggle. The buddynext-pro/v1 namespace and its Pro endpoints register only when BuddyNext Pro is also active.
The base is your site REST root plus the namespace: https://your-site.com/wp-json/buddynext/v1 for the free surface, or https://your-site.com/wp-json/buddynext-pro/v1 for the Pro surface. In the interactive reference, set your host in the Servers dropdown, then use Authorize before running a request.
Register one or more webhook endpoints through the Webhooks domain. Each endpoint keeps a delivery log you can read back over the API, and you can trigger a test delivery to confirm your receiver is reachable before relying on it in production.
Yes. The REST surface is the same layer the BuddyNext front end uses, with Application Password auth, a single App Shell bootstrap call, and full account security including two-factor. It is designed for external consumers, not only the built-in UI.
Yes. The reference now covers both namespaces: buddynext/v1 (Free) and buddynext-pro/v1 (Pro), which adds membership, payments, AI, analytics, broadcast and drip email, push notifications, and advanced moderation and search. The Pro namespace registers only when BuddyNext Pro is active, so those endpoints appear against a site that runs Pro.
287 endpoints across two namespaces, standard WordPress auth, and outgoing webhooks. The free buddynext/v1 layer ships with every install; buddynext-pro/v1 activates with Pro. No add-on, no extra configuration step.
WBComDesigns is amazing. The WP plugins and themes are of top notch quality with lots of features and updated very frequently. Supports are very responsive and helpful. I use Reign with TutorLMS, and the experience is surprisingly smooth. The recently launched BuddyNext Pro and MediaShield Pro are…
WBCOM Designs has constantly updated and supported their plugins and themes. Recently the new BuddyNext project is Amazing! - and the new line of addons like Mediaverse, Jetonomy, Mediashield, and Listora.. are likewise Amazing! - and very well built. Today their online Chat solved a download…
I am really glad to have known BuddyX Pro Team led by Mr.Varun Dubey. I had a challenge of mobile responsiveness and after I brought the issue to their attention, they were able to address it promptly. They also made a follow-up on my experience after resolving the issue. I highly recommend WBcom…
Its response rate and working very well I appreciate and am very happy to work with this webmaster.
I've been developing a relatively complex website for my business, and my development experience is pretty limited. As expected, I ran into a number of difficulties, and ach time, the Wbcom team helped me resolve my issues quickly and patiently. I can't recommend their products and support enough!
I recently had a fantastic experience with the Wbcom Designs support team. They were incredibly prompt, warm, patient, and friendly as they helped me resolve an issue with my website. I truly appreciate the complexity of troubleshooting website-related issues, as each one is unique, and users often…
Great support; the issue was resolved perfectly well.
Fantastic 6 star support. I wanted to setup a membersite and tried many solutions. I contacted Wbcom for BuddyX and tried the theme with Buddypress. I am not a webdesigner or a coder, but had a requirement that was not standaard. I contacted WBcom and Pallavi helped me from start to finish with…
Great way of support! Thanks a lot! Direct responding, open for questions and very fast to the right solution!
Fast Respond & Troubleshooting With technical insight