Webhooks and Real-time Events

WebSocket

Airlink includes a WebSocket server for real-time communication. The WebSocket connection is authenticated via the user’s session cookie.

Connection

ws://your-panel.com/socket.io/

The Socket.IO client library handles reconnection and heartbeat automatically.

Events

Server Console

Real-time console output from game server containers:

Event: server:console
Payload: { serverId: string, line: string }

Server Status

Status change notifications:

Event: server:status
Payload: { serverId: string, status: string, running: boolean }

Activity

Activity log notifications for admins:

Event: activity
Payload: { event: string, actor: string, server?: string, metadata?: object }

Activity Logging

All significant actions are logged to the ActivityLog database table. This is not a webhook system but provides an audit trail.

Logged Events

Activity Log Fields

Each log entry contains:

• actorId (user who performed the action, nullable for system events)
• serverId (server the action relates to, nullable for non-server events)
• event (event type string)
• metadata (JSON string with additional context)
• ip (IP address of the actor)
• createdAt (timestamp)

Querying Activity

Activity logs are viewable in the admin panel under Activity. The V2 API does not currently expose a public activity endpoint (activity data is managed through the admin UI).

Future: Webhook Support

The panel architecture supports adding outbound webhooks. The ActivityLog table and event taxonomy make this possible. A webhook system would:

1. Let admins register HTTP endpoints to receive event notifications
2. POST event data as JSON to registered URLs
3. Support event filtering (only certain event types)
4. Include retry logic for failed deliveries

This is not yet implemented.