The following WordPress filters are used by DMSI Advanced API. Filters marked “registered by extension” are called with apply_filters() and can be used by third-party code. Filters marked “hooked by extension” are standard WordPress filters that the plugin attaches its own callbacks to.
| Filter | Type | Priority | Purpose |
|---|---|---|---|
dmsilm_admin_shell_sections | Registered by extension | — | Registers the Developer section in the DDLS admin shell navigation |
dmsilm_admin_shell_pages | Registered by extension | — | Registers all Developer sub-pages: API Keys, OAuth Clients, Monitoring, Rate Limits, Sandbox, Documentation, Playground, and Changelog |
dmsilm_register_extension_licenses | Registered by extension | — | Registers the DMSI Advanced API license entry with the DDLS unified license management page |
rest_pre_dispatch | Hooked by extension | 5 | Enforces HTTPS in production mode — rejects HTTP requests with 403 before they reach any controller |
rest_pre_dispatch | Hooked by extension | (middleware chain) | Runs the rate limiter check and IP whitelist check as part of the middleware chain |
rest_post_dispatch | Hooked by extension | 10 | Reformats WordPress’s default 401 authentication error responses to the DMSI error format |
rest_post_dispatch | Hooked by extension | 99 | Injects X-RateLimit-* headers, CORS headers, and X-DMSI-Environment header into all responses |
determine_current_user | Hooked by extension | 20 | Validates Bearer tokens — API key, JWT, OAuth access token, and sandbox key |
rest_authentication_errors | Hooked by extension | 20 | Returns a WP_Error on authentication failure, preventing further request processing |
Note on Webhook Events #
There is no dmsi_aapi_supported_webhook_events filter. The supported webhook events list is defined as a PHP class constant (DMSI_AAPI_Webhook_Manager::EVENTS) and cannot be modified via WordPress hooks. See the Supported Webhook Events section above for instructions on adding custom events in a fork.