System Requirements #
| Component | Requirement |
|---|---|
| WordPress | 6.0 or higher |
| PHP | 8.0 or higher, with the openssl extension enabled |
| DMSI DDLS | 1.2.0 or higher (required — plugin will not activate without it) |
| WooCommerce | Current release (required by DMSI DDLS) |
| MySQL | 5.7 or higher |
| MariaDB | 10.3 or higher (alternative to MySQL) |
Optional Components #
| Component | Benefit |
|---|---|
| Action Scheduler (WordPress plugin) | Provides reliable async webhook delivery with retry support. Without it, webhooks fall back to WP-Cron, which is not real-time on low-traffic sites. |
HTTPS Requirement #
HTTPS is required for production use. When the environment is detected as production, the plugin returns HTTP 403 for any API request arriving over plain HTTP. This enforcement protects API keys and tokens from being transmitted in cleartext.
For local development, set the environment to development via the dmsi_aapi_environment WordPress option or an environment.php overlay file at the plugin root.
PHP OpenSSL Note #
The plugin uses PHP’s openssl_pkey_new() to generate the RS256 key pair on activation. On some Windows server environments, this call may fail if the OPENSSL_CONF environment variable is not set. If JWT authentication fails with HTTP 500 errors after activation, check the dmsi_aapi_jwt_key_error WordPress option for a diagnostic message. The plugin’s installer includes a workaround that searches for openssl.cnf alongside PHP_BINARY.
Compatibility #
DMSI Advanced API loads at WordPress plugins_loaded priority 15, after DMSI DDLS (which loads at priority 10). The plugin’s activation gate checks for the presence of the DMSILM_Core class. If DDLS is not active, DMSI Advanced API will deactivate itself and display an admin notice.
Part of the DMSI Advanced API v1.0.1 documentation set.
Cross-reference: For core DDLS documentation, see the DMSI DDLS BetterDocs.