Documentation · Developer Documentation

REST API For Developers

This page intentionally does not list internal REST routes, parameters, controllers, nonces or response payloads.

Why no public REST contract

The plugin exposes a small number of REST endpoints to support its own admin, importer and front-end JavaScript. These endpoints are internal — they exist to make the plugin work, not to provide a public integration API. Route names, parameters and responses may change between releases without notice.

If you need to integrate an external system with the plugin, do not call these internal endpoints. Instead use the supported integration surfaces listed below, or open a feature request describing the integration you need.

Supported public integration surfaces

When integrating with the plugin, prefer these stable surfaces:

Internal class names, option keys, database tables, REST and AJAX endpoints, cron hook names, capability and nonce identifiers, and release / update infrastructure are treated as implementation details. They may change between releases without notice and are not part of the public integration contract.

Stability and change policy

Anything not listed as a supported public surface above is considered an internal implementation detail. Internal APIs, storage layout and security implementation may change between releases. Do not depend on them from third-party code, themes or external systems. Direct database writes are not supported.

Public documentation notice. This page provides a high-level integration overview only. Internal implementation details, private APIs, storage internals and security-sensitive release infrastructure are maintained separately and are not part of the public documentation. Supported integration surfaces are the documented shortcodes, template overrides, settings UI and any extension points explicitly published in this section.