Dark enterprise featured image for how to use the jetonomy rest api to build a headless community on bpcustomdev

Most WordPress forum plugins render HTML on the server and call it done. If you want to build a custom frontend, a mobile app, or integrate forum data into an external dashboard, you are stuck scraping HTML or reverse-engineering undocumented AJAX endpoints.

Jetonomy takes a different approach. It exposes a comprehensive REST API under jetonomy/v1 with 42+ endpoints covering every major feature: topics, replies, votes, spaces, users, search, notifications, and analytics. The same API that powers the built-in frontend is available for your custom integrations.

API Overview

All endpoints follow WordPress REST API conventions: JSON request/response, standard HTTP methods, cookie or application password authentication, and consistent error formats.

Core Endpoints

Resource Endpoints Methods
Spaces /spaces, /spaces/{id} GET, POST, PATCH, DELETE
Categories /categories, /categories/{id} GET, POST, PATCH, DELETE
Posts (Topics) /posts, /posts/{id} GET, POST, PATCH, DELETE
Replies /posts/{id}/replies GET, POST
Votes /votes POST, DELETE
Users /users, /users/{id} GET
Search /search GET
Tags /tags GET, POST
Notifications /notifications GET, PATCH

Pro Endpoints (Jetonomy Pro)

Resource Endpoints Extension
Conversations /conversations, /conversations/{id}/messages Private Messaging
Analytics /analytics/overview, /analytics/top-spaces Analytics
Unread count /conversations/unread-count Private Messaging

Authentication

The API supports three authentication methods:

  • Cookie authentication, For same-domain requests (the built-in frontend uses this)
  • Application passwords, For server-to-server integrations (WordPress 5.6+)
  • JWT tokens, For headless/mobile apps (via a JWT plugin)

All endpoints respect the same permission system as the web interface. A user can only access data through the API that they can access through the frontend. Private spaces, trust level restrictions, and moderation rules all apply.

Use Cases

Custom Mobile App

Build a React Native or Flutter app that reads and writes forum data through the REST API. Users can browse topics, post replies, vote, and receive push notifications, all through API calls.

Headless Frontend

Build a Next.js or Nuxt.js frontend that fetches forum data from the API and renders it with your own design system. The WordPress backend handles data, permissions, and business logic. Your frontend handles the presentation.

Dashboard Integrations

Pull forum analytics data into your business dashboard. The /analytics/overview endpoint returns daily post counts, active users, engagement rates, and top contributors, data you can visualize in Grafana, Metabase, or a custom dashboard.

Chatbot Integration

Build a chatbot that searches the forum for answers before routing to human support. The /search endpoint returns matching topics ranked by relevance. If a match is found, the bot links the user to the existing answer.

External Content Display

Display recent forum topics on your homepage, in your app’s help section, or in a sidebar widget on non-WordPress pages. The /posts endpoint with sorting and filtering gives you exactly the content you need.

Pagination

The API uses cursor-based pagination for consistent performance at any scale. Instead of page numbers, responses include a next_cursor value. Pass it as a query parameter to fetch the next page:

GET /jetonomy/v1/posts?space_id=5&per_page=20
GET /jetonomy/v1/posts?space_id=5&per_page=20&cursor=abc123

This approach performs identically whether you are fetching page 1 or page 100. See our database architecture guide for why cursor-based pagination matters.

WordPress Abilities API Integration

Jetonomy registers 18 abilities through the WordPress Abilities API (WP 6.9+). This means AI assistants, external tools, and client applications can discover and invoke forum capabilities programmatically:

  • create-topic, Create a new forum topic
  • search-topics, Search across all forum content
  • get-analytics, Retrieve community analytics data
  • And 15 more covering replies, votes, moderation, and messaging

Webhooks for Real-Time Events

The REST API lets you pull data. Webhooks push data to you. Together, they provide complete two-way integration between your forum and external services.

Getting Started with the API

  1. Install Jetonomy (setup guide)
  2. Enable application passwords for API authentication (WordPress Settings → Users)
  3. Explore endpoints at yoursite.com/wp-json/jetonomy/v1/
  4. Test with Postman or curl: curl -u user:app-password yoursite.com/wp-json/jetonomy/v1/posts
  5. Build your integration using any HTTP client in any language

The API is the same one that powers Jetonomy’s built-in Interactivity API frontend. If the web interface can do it, the API can do it. Build whatever your community needs.

Implementation details that make the rollout smoother

How to Use the Jetonomy REST API to Build a Headless Community fits into the broader forums category through launch plans, migration steps, and setup choices. That matters because the technical setup is only one part of success. The way you structure spaces, roles, onboarding, and follow-up is what determines whether the forum becomes a searchable asset or just another neglected section of the site.

  • Start with one public space and one private operator space so you can test permissions before the wider launch.
  • Seed the first discussions yourself using the exact questions customers already ask in email, pre-sales chat, or onboarding calls.
  • Define who can create spaces, who can moderate them, and what counts as an accepted answer before the first wave of members arrives.

Why teams evaluating this setup should look at Jetonomy Pro

Jetonomy Pro is useful here because it gives you Q&A, discussion spaces, trust levels, private areas, and a cleaner launch path than stitching together older forum plugins. If you want to know more and try Jetonomy, take a closer look at Jetonomy Pro. It is the most direct next step for teams that want to move from theory to an actual working WordPress community experience.

For articles like this one, the practical question is not only whether the approach works in theory. It is whether your chosen forum stack gives you the moderation depth, user experience, and extensibility to keep the system useful six months after launch. That is where a more complete product decision starts to matter.