Xeonr Developer Docs
API SpecificationEnvironments

Delete Environment

POST
/containers.api.v1.EnvironmentService/DeleteEnvironment

Deletes an Environment record.

Access: namespace OPERATOR or above (write)

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

Connect-Timeout-Ms?number

Define the timeout, in ms

Request Body

application/json

environmentId?string
Length1 <= length <= 64
[key: string]?never

Response Body

application/json

application/json

curl -X POST "https://containers.xeonr.io/containers.api.v1.EnvironmentService/DeleteEnvironment" \  -H "Connect-Protocol-Version: 1" \  -H "Connect-Timeout-Ms: 1000" \  -H "Content-Type: application/json" \  -d '{}'
{}
{
  "code": "not_found",
  "message": "string",
  "details": [
    {
      "type": "string",
      "value": "string",
      "debug": {}
    }
  ]
}

Build Environment POST

Builds a content-addressed image from an install spec on the shared BuildKit and registers it, streaming build log frames and ending with either the new Environment or a build failure. install.base_image or stages is required, every stage needs a base_image, and apt package names must be plain tokens (InvalidArgument). Base images given as tags are pinned to digests first. A context_snapshot_id builds over that workspace snapshot. shared_cache dedupes identical specs across namespaces. Unimplemented without a build backend. **Access:** namespace OPERATOR or above (write)

Get Environment POST

Returns one Environment. NotFound for an unknown id. **Access:** namespace VIEWER or above (read)