Webhooks explained: notify other systems of server events

For server administrators · Updated 2026-10-29

On this page
  1. Add a webhook
  2. Events
  3. What your system receives
  4. Delivery and retries
  5. Good to know
  6. Common questions

A webhook tells another system what happens on the server. For each event you choose, the server sends a signed JSON message to your address — for example to update your billing system when an account is suspended, or to post in a chat channel when a task fails.

Add a webhook

  1. Log in to the administrator panel (https://<server>:2087).
  2. Open Webhooks in the menu (section Account).
  3. Under Add webhook, enter the Address, for example https://billing.example.com/hooks/hosting.
  4. Tick the Events you want (the account events are ticked by default).
  5. Click Add webhook.
  6. The Signing secret is shown. Copy it into the receiving system.

Click Send test to send a test message, Show secret to see the secret again and Remove to delete the webhook.

Events

EventWhen
account.createdAccount created
account.suspended / account.unsuspendedAccount suspended or unsuspended
account.terminatedAccount terminated
account.changedPackage, contact email, domain or username changed
account.passwordAccount password changed
domain.added / domain.removedAddon, subdomain or alias added or removed
domain.movedDomain moved to another account
email.created / email.deletedMailbox created or deleted
disk.limitAccount near or over its disk space
bandwidth.limitAccount over its monthly bandwidth
task.failedA server task failed
ticket.opened / ticket.repliedA customer opened or replied to a support ticket

What your system receives

A POST request with a JSON body:

Content-Type: application/json
X-Sahaab-Event: account.created
X-Sahaab-Signature: sha256=<HMAC-SHA256 of the body with the secret>

{"event": "account.created", "id": "…", "time": "…", "server": "server1.example.com",
 "data": {"account": {"username": "…", "domain": "…", "owner": null}, "package": "…", "email": "…"}}

To check that a message is genuine, compute the HMAC-SHA256 of the raw body with the signing secret and compare it with X-Sahaab-Signature.

Delivery and retries

  • Answer with any 2xx status.
  • Other answers and timeouts (10 seconds) are tried again after 1, 5, 30 and 120 minutes; after that the delivery is given up.
  • Recent deliveries on the page shows each message with its status and, for failures, the error and the number of attempts.

Good to know

  • Up to 20 webhooks.
  • The address must be complete, starting with https:// (or http://), and its name must resolve.
  • Resellers can add their own webhooks for events of their accounts.

Common questions

My endpoint receives nothing. What should I check?

Click Send test and look at Recent deliveries: the error shows whether the address could not be reached, timed out or answered with an error status.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.