Documentation · Developer Documentation

AJAX Actions For Developers

This page intentionally does not list internal admin AJAX action names, payloads, capability checks or nonce identifiers.

Why no public AJAX contract

The plugin uses admin-AJAX actions internally for its own admin screens, import controls and lead workflows. They are not public integration points. Action names, the JavaScript that triggers them and the server-side nonce and capability requirements may change between releases without notice.

External systems must not invoke these actions directly. To trigger imports on a schedule, configure the plugin's own automation from the admin UI. For external automation use the integration surfaces listed below.

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.