Every meaningful change on a hosting server is an event: an account is created, a certificate is renewed, a backup fails, disk usage crosses a threshold. Panelica's Webhooks turn those events into structured, signed notifications delivered to your systems in real time — so your billing platform, monitoring stack, security tooling and internal applications stay synchronized with the server without polling, custom agents or manual checks. Here is why we built it, how it works, and where it fits in a professional environment.
Why we built it
Servers do not operate in isolation. The panel that hosts your customers also feeds your invoicing, your support desk, your monitoring dashboards and your compliance records — and historically, keeping those systems in sync meant polling APIs on a schedule, writing custom scripts, or worse, finding out about a failed backup days later. Polling is wasteful, always out of date, and silent exactly when something goes wrong.
Webhooks invert the model: the panel tells you, the moment it happens. When an account is suspended, your billing system knows. When a certificate is about to expire, your operations channel knows. When a backup fails at three in the morning, the right people know at three in the morning — not at the Monday review.
How it works
on the server
structured JSON
HMAC secret per webhook
endpoint or messaging platform
logs, retries, analytics
Configuration lives under Developer > Webhooks and is organized in four tabs:
- Webhooks — create and manage subscriptions. Each webhook has a name, a destination, a selection of events (searchable, with select-all per category), and delivery settings: HTTP method, timeout, retry count and an optional delay. Every webhook can be tested with one click, paused and resumed, and its signing secret can be regenerated at any time.
- Available Events — the full catalog of events with descriptions and payload examples, so integration teams can see exactly what they will receive before writing a line of the consumer.
- Examples — ready-made integration patterns to start from.
- Recent Calls — delivery observability: success rate, average, fastest and slowest response times, pending retries and a per-delivery history. When an integration misbehaves, the evidence is on screen, not in a log file on the server.
Deliveries go to any HTTPS endpoint you operate — or directly to your team's messaging platform for human-facing alerts. Every HTTP delivery carries a signature header computed with the webhook's secret, an event-type header and a unique delivery ID, so receiving systems can verify authenticity, route by type and deduplicate reliably. Failed deliveries are retried automatically up to three times with scheduled backoff.
What you can subscribe to
| Category | Representative events |
|---|---|
| Account lifecycle | user.created, user.updated, user.suspended, user.login, user.login_failed |
| Domains | domain.created, domain.updated, domain.suspended, domain.deleted |
| SSL certificates | ssl.issued, ssl.renewed, ssl.expiring_soon, ssl.expired |
| Security | security.ip_blocked, security.ip_unblocked |
| Email, databases, FTP | email.created, database.created, ftp.created and their deletion counterparts |
| Backups | backup.created, backup.failed, backup.restored |
| System health | system.cpu_warning, system.disk_warning, system.service_started, system.service_stopped, system.backend_started |
Where it fits
| Scenario | How webhooks are used |
|---|---|
| Billing and provisioning sync | user.created and user.suspended keep your invoicing platform aligned with the server automatically — accounts never drift between systems. |
| Operations alerting | backup.failed, system.disk_warning and system.service_stopped reach the on-call channel the moment they fire, with retry-backed delivery. |
| Security monitoring | security.ip_blocked and user.login_failed stream into your SIEM or logging pipeline, adding panel-level visibility to your security posture. |
| Certificate governance | ssl.expiring_soon feeds your ticketing system before expiry becomes an outage; ssl.renewed closes the loop. |
| Audit and compliance | A webhook consumer that archives every lifecycle event gives you an independent, timestamped record of administrative activity. |
| Custom internal tooling | Any application that should react to the server — dashboards, reconciliation jobs, customer notifications — subscribes to exactly the events it needs. |
Webhooks pair naturally with the panel's new Python Application Hosting: the same server that emits the events can host the service that consumes them — an integration loop with no third-party platform in the middle.
Frequently asked questions
How do receiving systems verify that a delivery is genuine?
Every delivery is signed with the webhook's secret and carries the signature, the event type and a unique delivery ID in dedicated headers. Consumers verify the signature, route by event type and use the delivery ID for deduplication.
What happens if our endpoint is down?
Deliveries are retried automatically up to three times on a backoff schedule, and every attempt is visible in the Recent Calls tab.
Can we subscribe different systems to different events?
Yes. You can create multiple webhooks, each with its own destination, its own event selection and its own secret — billing listens to account events, operations listens to system health, security listens to security events.
Do we have to write a consumer to get value from this?
No. Deliveries can go straight to your team's messaging platform for human-facing alerts; custom HTTP consumers are there when you want machine-to-machine integration.
How do we see whether an integration is healthy?
The Recent Calls tab shows delivery success rate, response-time statistics and per-delivery history — integration health is a dashboard, not a guess.
Availability: update your panel
Webhooks ship with the current Panelica release under Developer > Webhooks. If the section is not visible in your panel yet, apply your panel update first — it is one click from the update screen. For the recommended procedure, see One-Click Update All: the safest way to keep Panelica current.
Connect your server to the rest of your business. Webhooks join the panel's developer platform alongside the API and Python Application Hosting. Review the full feature set, see plans and pricing, or discuss your integration scenarios on the community forum.