Webhooks x Virto Commerce

Virto Commerce includes a native webhooks module that automatically discovers all domain events raised by installed modules and delivers HTTP POST notifications with JSON serialized event data to user configured endpoints. It supports selective payload composition, multiple authentication schemes, and resilient delivery with configurable retry logic.

Webhooks in Virto are configured through the admin interface, where each webhook is set up with a name, a specific event to monitor, optional additional fields to include in the payload, and the destination URL. One event per webhook is the standard configuration, meaning separate webhooks are created for each event type that needs to be monitored.

Any event, any module — Virto’s webhooks module discovers domain event types from the platform and every installed module at runtime. There’s no manual registration required, so if a module raises an event, it’s available for subscription automatically.

Control over what gets sent — Each webhook can be configured to include specific entity properties in the notification payload, including previous field values for change tracking. This means the receiving system gets exactly the data it needs, not a full object dump it has to filter through.

Works with how your systems authenticate — Destination endpoints can require different authentication methods. Virto’s webhooks support None, HTTP Basic, Bearer Token, and Custom Header, so the connection works with whatever the receiving system expects without custom middleware just to handle auth.

Reliable delivery without manual monitoring — Failed deliveries retry automatically using exponential backoff — three attempts at 1, 2, and 4-minute intervals by default. Every attempt is logged in an audit feed with full request and response detail, so teams can see exactly what was sent, what came back, and when, without building a separate logging layer.

Webhooks are a built-in capability available through Virto’s admin interface without additional module installation beyond the webhooks module itself. Business users or administrators with appropriate permissions can create and manage webhooks directly in the admin interface.

Key considerations: which domain events need to trigger notifications, what data fields the destination system needs in the payload, which authentication method the destination endpoint requires, and whether the default retry policy is sufficient for your reliability requirements.