Admin API
Build integrations against the server’s REST management interface.
A private management API
The dashboard is backed by REST routes under /api/v1. Keep the management listener private and use the authentication mechanism configured for your instance. The current route registrations are the authoritative endpoint inventory.
Useful read endpoints
The route table includes health, system information, server statistics, domain listings and cache statistics. These paths are shown as a reference, without embedding any real credential.
GET /api/v1/health
GET /api/v1/system
GET /api/v1/stats
GET /api/v1/domains
GET /api/v1/cache/stats
GET /api/v1/metrics
Changes are privileged operations
Domain creation and deletion, reloads, cache purges and application deployment change the server. Use narrowly scoped credentials where supported, check response status codes, and avoid exposing the admin API to a public frontend. Never put management credentials into browser-delivered code.
Verify against the running version
Endpoint details and payloads evolve. Use internal/admin/routes.go and the corresponding handlers for your exact version, rather than assuming this introductory guide is a generated API schema.