Internal API and health endpoints
Portal is UI-first; only narrow, documented endpoints should be treated as integration surfaces.
No general public API
The dashboard uses an internal session-cookie and CSRF API. Its routes, payloads, and error strings are implementation detail and may change with the UI. Portal does not publish API v1, bearer scopes for project management, generic REST automation, or a public webhook registration contract.
Health endpoint
GET /api/healthThe installer and operators use this unauthenticated endpoint to confirm the Portal service. In production, test it through HTTPS as well as locally on 127.0.0.1:3100.
Narrow monitoring endpoint
Monitor Logs Tokens are the purpose-built bearer-token interface: GET /api/monitor/v1/projects/<slug>/deployments. It returns safe deployment/job status for the token’s single project and excludes repository URLs, runtime logs, and secrets. Do not use it as a deploy trigger.
Automation status
Inbound GitHub/GitLab auto-deploy webhooks and a general automation API are planned, not available. Trigger deployment manually from the dashboard today.