Skip to main content

HTTP API

The canonical HTTP contract is the OpenAPI 3.1 specification in the Core repository. Client libraries, examples, and this documentation must all follow that file.

Control-plane endpoints​

MethodPathPurpose
GET/api/healthCheck whether Core is available.
POST/api/v1/workers/heartbeatReport a worker snapshot and receive commands.
PUT/api/processes/{id}/desired-stateStart or stop one process.
GET/api/stateRead the paginated console state and history.
POST/api/auth/loginOpen an operator browser session.
GET/api/auth/sessionCheck the current operator session.
POST/api/auth/logoutClose the operator session.
GET, POST/api/auth/worker-tokensList token metadata or create a named worker token.
DELETE/api/auth/worker-tokens/{id}Revoke a worker token.
GET/api/executions/{id}/logsRead captured output for one execution.

heartbeatInterval is a positive whole number of seconds everywhere in v1. Names are unique per worker, so operator commands address a process by id.

The heartbeat endpoint is the only endpoint a worker needs and requires bearer authentication. Operator endpoints use the browser session created by login; unsafe requests also carry the console's CSRF token. GET /api/health is public.

See the Raw API manual for an implementation guide and the OpenAPI document for complete schemas and status codes.