Set up outgoing webhooks

Administrators configure outgoing webhooks so hostware sends event notifications to their own HTTP(S) endpoint. Each webhook configuration combines a name, a destination URL, a selection of events, and an active or inactive state. This feature is separate from payment-gateway webhooks and from the HTTP Webhook hosting-provisioning module.

Create a webhook configuration

Give the configuration a name, enter the destination URL, and select the events you want delivered.

1. Give the configuration a name.

2. Enter the destination URL.

3. Select the events to deliver.

4. Set the configuration to active.

5. Save the configuration.

A saved configuration can be edited, deactivated, and reactivated at any time. Only active configurations deliver events.

URL requirements

The destination URL must use HTTP or HTTPS and resolve to a public endpoint. URLs that contain credentials are rejected.

Choosing events

Select the events that matter to your integration, grouped by business area:

• Billing: invoice.created, invoice.paid, payment.failed, order.placed

• Domains: domain.registered, domain.transfer_completed

• Services: service.activated, service.renewed, service.suspended, service.unsuspended, service.terminated

• Customers: customer.passkey_added, customer.settings_saved

• Support: ticket.created

The Webhook events and payloads reference documents the payload for each event.

Delivery and delivery history

Deliveries are queued and sent as HTTP(S) requests. A failed delivery is retried up to three times, with approximately one-minute and five-minute backoff intervals.

Each delivery is recorded with its response status, response body, success state, errors, and duration. Delivery records older than 90 days are removed by a scheduled cleanup.