Xeonr Developer Docs
API SpecificationSandboxes

SyncWorkspace

POST
/containers.api.v1.SandboxService/SyncWorkspace

Authorization

BearerAuth
AuthorizationBearer <token>

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

Connect-Protocol-Version*number

Define the version of the Connect protocol

Value in1
Connect-Timeout-Ms?number

Define the timeout, in ms

Request Body

application/json

sandboxId?string
workspaceId?string

Flush only this workspace. Empty flushes every read-write mount the sandbox has, which is the pre-multi-mount behaviour and stays the default.

[key: string]?never

Response Body

application/json

application/json

curl -X POST "https://containers.xeonr.io/containers.api.v1.SandboxService/SyncWorkspace" \  -H "Connect-Protocol-Version: 1" \  -H "Content-Type: application/json" \  -d '{}'
{
  "filesFlushed": 0,
  "bytesFlushed": 0,
  "conflicts": [
    "string"
  ]
}
{
  "code": "not_found",
  "message": "string",
  "details": [
    {
      "type": "string",
      "value": "string",
      "debug": {}
    }
  ]
}

SuspendSandbox POST

Previous Page

TailSandboxLogs streams the sandbox's RUN LOG: what its workload command printed, as one continuous record across the sandbox's whole life. POST

It cannot come from the pod. A suspend DELETES the pod and a resume schedules a fresh one, so pod logs would lose everything the sandbox ever emitted at the first suspend — the same reason an App's logs are collected centrally, arrived at from the opposite direction. The control plane follows each live pod and retains what it emits. The stream carries typed lifecycle MARKERS interleaved with the output, in the same cursor space, so "where did it crash / suspend / restart?" is a record to switch on rather than a banner to pattern-match out of the bytes.