Webhook events and payloads

Hostware sends a JSON payload to your configured endpoint whenever one of the subscribed business events occurs. This reference lists the event keys you can subscribe to, the envelope each request carries, and how deliveries are recorded and retried.

JSON envelope

Every webhook request carries a JSON envelope containing the event key, the time the event occurred, and the event-specific data for that occurrence.

Events

Each delivery carries the key of the event that triggered it and that event's payload. Events are grouped below by business area.

Billing

Event	When it fires	Payload contents
`invoice.created`	An invoice was created.	Identifiers and billing fields for the invoice.
`invoice.paid`	An invoice was paid.	Identifiers and billing fields for the invoice.
`payment.failed`	A payment failed.	Identifiers and fields for the failed payment.
`order.placed`	An order was placed.	Identifiers and fields for the order.

Domains

Event	When it fires	Payload contents
`domain.registered`	A domain was registered.	Identifiers and fields for the registered domain.
`domain.transfer_completed`	A domain transfer completed.	Identifiers and fields for the transferred domain.

Services

Event	When it fires	Payload contents
`service.activated`	A service was activated.	Identifiers and fields for the service.
`service.renewed`	A service was renewed.	Identifiers and fields for the service.
`service.suspended`	A service was suspended.	Identifiers and fields for the service.
`service.unsuspended`	A service was unsuspended.	Identifiers and fields for the service.
`service.terminated`	A service was terminated.	Identifiers and fields for the service.

Customers

Event	When it fires	Payload contents
`customer.passkey_added`	A passkey was added to a customer account.	Identifiers for the customer; no credential IDs, public keys, or credential hashes.
`customer.settings_saved`	Customer settings were saved.	Identifiers and settings fields for the customer.

Support

Event	When it fires	Payload contents
`ticket.created`	A support ticket was created.	Identifiers and fields for the ticket.

Delivery and retries

Deliveries are queued and retried, so a transient failure on your side does not lose the event. Hostware retries a failed delivery up to three times, with roughly a one-minute gap and then a five-minute gap between attempts. Each delivery records the response status and body returned by your endpoint, whether the delivery succeeded, any errors, and the delivery duration. Delivery records older than 90 days are removed by scheduled cleanup.

Sales channel scope

Only active subscriptions for the relevant sales channel receive matching events; a webhook record that has no sales channel is not treated as a global subscription. If a delivery you expect never arrives, check that the webhook is active and assigned to the sales channel the event belongs to.

Security

Payloads can contain customer and billing data, so treat every endpoint you register as sensitive. The passkey-added payload carries no credential IDs, public keys, or credential hashes; those values are never included in a delivery.

See Set up outgoing webhooks for configuration steps.

Was this helpful?