Overview

The Backend Install API is a legacy compatibility surface that returns installation status and progress information without performing real provisioning. WebSocket installation streaming has been removed; new integrations should use the canonical SSH and runtime backend flows instead.

Base URL

Authentication

All Backend Install routes are protected and require a valid bearer token in the Authorization header. See Authentication for details.

Endpoints

Get install status

Returns a simple health/status payload for the legacy backend-install surface.

Example request

Example response

Response fields

Get install progress

Returns metadata describing the legacy install flow and points callers to the canonical replacement routes.

Example request

Example response

Response fields

Report install progress

Legacy install completion stub. The endpoint accepts any JSON body (or an empty body) and returns a success message.

Example request

Example response

Response fields

Test backend connection

Returns a stubbed system-info payload for a legacy connection test. Real connectivity tests should use the SSH connections surface.

Example request

Example response

Response fields

Migration

This surface is preserved only for backwards compatibility. New code should target the canonical routes returned by GET /api/v1/backend-install/progress:
  • POST /api/v1/ssh-connections — register an SSH connection.
  • POST /api/v1/ssh-connections/:id/connect — open a connection.
  • POST /api/v1/ssh-connections/:id/install-agent — install an agent remotely.
  • POST /api/v1/runtime/backend — register or update a runtime backend.
See SSH Connections, SSH Keys, Runtime Backend, and Runtime Discovery for the current surfaces.

Error codes