The EcliPanel backend exposes a REST API that the frontend, Wings nodes, and external integrations all use. Every resource in the panel — servers, organisations, nodes, tickets, billing, AI, tunnels — has a corresponding set of JSON endpoints. You can call the API directly with any HTTP client, automate workflows with API keys, or explore it interactively via the built-in OpenAPI playground.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/thenoname-gurl/EcliPanel/llms.txt
Use this file to discover all available pages before exploring further.
Base URL
The backend listens on the port set in yourbackend/.env file. The Next.js frontend automatically proxies all /api/* requests to the backend, so from the browser you always hit the same origin. When calling the API directly — from a script or external service — use the backend’s address:
OpenAPI playground
The backend serves an interactive OpenAPI playground at the/openapi route. You can use it to browse every available endpoint, inspect request schemas, and send test requests without writing any code.
Response format
All responses are JSON. Successful operations return the resource or a confirmation object. Errors always return a JSON body with anerror key:
HTTP status codes
| Code | Meaning |
|---|---|
200 | Success |
201 | Resource created |
400 | Bad request — missing or invalid parameters |
401 | Unauthorized — authentication required or token invalid |
403 | Forbidden — authenticated but not permitted |
429 | Too many requests — rate limit exceeded |
503 | Feature disabled — endpoint is turned off by the panel operator |
Feature-gated endpoints
Some endpoints are controlled by feature flags set in the backend configuration. If a feature is disabled, any request to an endpoint in that group returns503:
| Feature flag | Affected endpoints |
|---|---|
ai | /api/ai/* |
ticketing | /api/tickets/*, /api/admin/tickets/* |
applications | /api/applications/*, /api/public/applications/* |
billing | /api/orders/*, /api/plans/*, /api/billing/* |
oauth | /api/oauth/* |
registration | /api/users/register |
dns | Organisation DNS zone endpoints |
tunnels | /api/tunnel/* |
Rate limiting
The API enforces per-IP and per-account rate limits on sensitive endpoints. When a limit is exceeded, the response is429 with a Retry-After header indicating how many seconds to wait:
WebSocket support
The server console is available over WebSocket for real-time output streaming. Connect using the token obtained from the REST API:Example request
Endpoint groups
Authentication
Log in, manage sessions, set up 2FA, and create API keys
Servers
Create, power, transfer, reinstall, and monitor game servers
Organisations
Manage multi-tenant workspaces, members, roles, and DNS zones
Nodes
Register nodes, view heartbeats, and manage allocations
Billing & orders
Create orders, manage plans, and retrieve invoices
AI endpoints
Chat completions, AI Studio, and model management
Tickets
Create and manage support tickets and replies
Admin
Panel-wide administration, user management, and audit logs