Webhooks mean that whenever an important event occurs in your AuthVaultix app
(such as login, register, license redeem, HWID mismatch, payment, ban, etc.),
the system automatically sends an HTTP request to the Endpoint URL you configured,
so external services can be instantly notified.In simple words: “An event happens → your server instantly notifies another server.”
Where Can Webhooks Be Used?#
1) Discord / Telegram Notifications#
You can connect your webhook endpoint to a Discord or Telegram relay service to receive alerts such as:- New user registration alerts
- New license redeemed alerts
- Failed login or brute force alerts
- HWID changed or spoof attempt alerts
- Payment success or failure alerts
2) Admin Audit + Logging Systems#
You can send events to external logging systems such as ELK, Grafana Loki, custom panels, or database loggers:- API activity logs
- Security events
- Staff actions tracking
- Seller actions tracking
3) Anti-Abuse / Auto-Blocking#
Webhook events can be used to trigger automated security rules:- Repeated failed logins → automatic IP blacklist
- Invalid signature attempts → automatically flag account
- Too many requests → rate limit or block
4) Integrations (Payments / CRM / Email)#
Payment or user lifecycle events can be pushed to external systems:- Payment gateway confirmation → activate subscription
- Create a “new customer” entry in a CRM
- Trigger automatic emails using services like SendGrid or Mailgun
5) Auto-Update / File Delivery Workflows#
If you run a loader or update system, webhooks can help automate workflows:- Start update pipelines when a new build is uploaded
- Track release events
- Real-time notifications (no need for polling)
- Automation — reduces manual work
- Security monitoring — suspicious activity becomes visible instantly
- Better operations — logs and alerts help detect issues quickly
What the UI Contains (Based on This Code)#
- Title: Webhooks
- Subtitle: Send secure event notifications to external services
- Delete All (visible only if webhooks exist)
- Link:
win/app/?page=webhook&delete_all=1 - Confirmation prompt: “Are you sure you want to delete ALL webhooks?”
- Add Webhook
- Opens modal:
#createWebhookModal
If a session message is set ($_SESSION['msg']), a toast notification appears:- Message:
SESSION[′msg′]</code></li><li>Type:<code>_SESSION['toast_type'] (default: success)
On desktop, the webhooks appear in a list with these columns:- Endpoint URL
- User Agent (if empty, “Default” is displayed)
- Created date
- Action (three-dot dropdown)
Action dropdown includes:- Delete →
win/app/?page=webhook&delete_id=ID (with confirmation)
If the list is empty, an empty state appears:No webhooks configured yet.
On mobile devices, webhooks are displayed as cards:- Endpoint (truncated)
- User Agent row
- Three-dot dropdown → Delete
The modal contains the following fields:- Endpoint URL (required, type=url)
- User Agent (optional)
- “Ensure your endpoint can verify signatures.”
- Add Webhook → POST submission with
create_webhook=1
Typical Webhook Events (Examples)#
- auth.login.success / auth.login.failed
- user.register
- license.redeem / license.expired
- hwid.mismatch / hwid.reset
- blacklist.added / whitelist.added
- payment.success / payment.failed
(The exact event names depend on your backend implementation, but the concept remains the same.)Modified at 2026-03-04 16:40:03