CloseConsoleSession
Authorization
BearerAuth A namespace-scoped API key (cpk_…) for machines, or a Xeonr Auth OIDC
token for humans. The key's namespace and role are pinned server-side.
In: header
Header Parameters
Define the version of the Connect protocol
1Define the timeout, in ms
Request Body
application/json
Signal the process group and wait briefly for it to exit; the api escalates to KILL if it does not. Interactive shells ignore SIGTERM, so a close that does not escalate is a close that silently does nothing. skip the grace window entirely
Response Body
application/json
application/json
curl -X POST "https://containers.xeonr.io/containers.api.v1.ConsoleService/CloseConsoleSession" \ -H "Connect-Protocol-Version: 1" \ -H "Content-Type: application/json" \ -d '{}'{
"session": {
"sessionId": "string",
"sandboxId": "string",
"namespace": "string",
"name": "string",
"argv": [
"string"
],
"env": {
"property1": "string",
"property2": "string"
},
"cwd": "string",
"cols": 0,
"rows": 0,
"state": "CONSOLE_SESSION_STATE_UNSPECIFIED",
"exitCode": 0,
"createdAtUnix": 0,
"lastActivityUnix": 0,
"headOffset": 0,
"tailOffset": 0,
"attached": 0,
"idleTtlSec": 0,
"createdBy": "string"
}
}{
"code": "not_found",
"message": "string",
"details": [
{
"type": "string",
"value": "string",
"debug": {}
}
]
}AttachConsole POST
AttachConsole is the interactive path: first message selects the session, subsequent messages are stdin/resize, and the server streams output from the requested offset (replaying scrollback first). Browsers can't do bidi over connect-web, so the console reaches this through the api's /ws/console bridge; native clients use it directly.
CreateConsoleSession POST
Next Page