Skip to main content

Registration API

Register self-hosted (Home) and linked (Link) agent installations. These endpoints are backend-only and support the Home and Link deployment modes alongside the default Cloud mode.
Home mode runs the agent container on your own hardware via Docker. Link mode connects an existing OpenClaw instance to the Agentbot platform. Cloud mode (the default) runs the agent on Agentbot infrastructure.

Validate API key

Validates a bearer token by computing a SHA-256 hash of the raw key and looking it up in the api_keys database table. Raw keys are never stored or compared directly. No session authentication is required — the API key is passed in the Authorization header.
The web application’s key validation endpoint uses a separate bcrypt-based lookup with the sk_ prefix convention. The backend endpoint documented here uses SHA-256 hashing and does not require the sk_ prefix.

Headers

Response

Errors

Register Home installation

Registers a Home mode installation. Requires bearer token (API key) authentication.
The web proxy forwards identity headers (x-user-email, x-user-id, x-user-role) from the active session, but the backend authenticates the request using the bearer token, not these headers.

Request body

Response

Errors

Registers a Link mode installation that connects an existing OpenClaw instance. Requires bearer token (API key) authentication.
The web proxy forwards identity headers (x-user-email, x-user-id, x-user-role) from the active session, but the backend authenticates the request using the bearer token, not these headers.

Request body

Response

Errors

List installations

Returns all registered installations across all deployment modes. Requires bearer token (API key) authentication.

Response

Errors

Registration heartbeat

Reports the status of a registered installation. When the userId matches a known registration, the lastSeen timestamp is updated and the status is set to active. No authentication is required.
This is a backend registration heartbeat for Home and Link installations. It is separate from the web heartbeat settings endpoint, which configures heartbeat scheduling for the web dashboard.

Request body

Response