A REST API that covers the whole community
Jetonomy is built to be driven from outside itself. Every part of the community is reachable over REST under the jetonomy/v1 namespace: 80 or more routes in the free plugin for categories, spaces, posts, replies, votes, search, notifications, subscriptions, moderation, users, bookmarks, and more, with about 60 more added by Jetonomy Pro. Responses are JSON. Public reads work without authentication, and writes authenticate with the standard WordPress wp_rest nonce, the same mechanism the bundled frontend uses.
That means another application, a companion plugin, a mobile client, or an agent can create a post, cast a vote, run a search, or work the moderation queue through documented routes with documented payloads, instead of scraping HTML or poking at the database.
Extend and override without forking
Reading data is only half a platform. Jetonomy fires hooks and filters throughout its flow, so you can react to community events and reshape responses from your own code. When you need to change how something looks, you copy the relevant template into your theme’s jetonomy/ directory and Jetonomy renders yours, which keeps your customization safe across plugin updates because you never edited a plugin file.
There are lighter-touch options too. The —jt-* CSS custom properties let you rebrand the community without overriding a single template, template hooks let you inject content into post cards, reply cards, and the single-post view, and documented recipes cover the common jobs: add a profile tab, add a space tab, add a nav item, extend the frontend store, or add fields to REST responses.
Embed, script, and automate
To surface community content elsewhere, Jetonomy ships 8 Gutenberg blocks and 8 shortcodes, alongside classic widgets, so spaces, posts, and leaderboards drop onto any page, post, sidebar, or page-builder canvas. The blocks add login and navigation, and the shortcodes add a space members list and a user profile card, so pick whichever set covers the view you need.
For operations and integration, the adapter pattern lets you swap the back-end service behind membership, email, or AI with your own implementation of a documented interface, without rewriting the plugin. A search adapter interface is defined too, while the built-in search endpoint runs on MySQL full-text search. WP-CLI drives and tests the community from the command line, and the WordPress Abilities API exposes the whole thing to AI agents and automation through a standard surface. Taken together, that is what makes Jetonomy something an agency or developer can build a real product on, not just configure.
