What This Extension Adds #
Core DDLS fires internal WordPress action hooks when licenses, subscriptions, and payments change state. These are not delivered to external systems.
>
With DMSI Webhooks, you can subscribe external endpoints to receive JSON payloads whenever any of these 9 built-in events (or custom-registered events) occur.
Event Categories #
Events are grouped by category:
| Category | Events | Requires |
|---|---|---|
| license | license.created, license.activated, license.expired, license.renewed | DMSI DDLS Core |
| subscription | subscription.created, subscription.renewed, subscription.cancelled | DMSI Subscriptions Pro |
| payment | payment.received, payment.failed | DMSI DDLS Core |
How Events Are Triggered #
DMSI Webhooks listens for DDLS Core WordPress action hooks. When DDLS fires one of these actions, the EventListener normalizes the data and calls dmsi_trigger_webhook(), which enqueues async deliveries to all subscribed endpoints.
Browsing Events in Admin #
Go to DDLS > Webhooks > Events to see:
- All registered event names and categories
- Description of when each event fires
- Sample payload for each event
Custom Events #
You can register custom events using the dmsi_register_webhook_event WordPress filter. Custom events appear in the admin Events list and are available for endpoint subscriptions. See Registering Custom Events.
Caching #
The event registry is cached in a WordPress transient for 24 hours to avoid recalculating on every request. Call EventRegistry::invalidate_cache() programmatically or use the admin Refresh Events button if you need the cache cleared after adding a custom event.
Related Topics #
- License Events
- Subscription Events
- Payment Events
- Registering Custom Events