Integrate

API reference

JSON over HTTPS. Organization-scoped resources. Retry-safe operations.

Internal alpha. See deployment and qualification requirements before student use.

Authorization: Bearer <organization-api-key>
Content-Type: application/json

POST /api/v1/orgs/{org}/disks
{ "name": "workspace", "region": "us-west1", "size_gib": 8 }

POST /api/v1/orgs/{org}/disks/{disk}/checkpoints
{ "operation_id": "your-stable-submission-id" }

Resource routes

Use /api/v1/orgs/{org}/disks for disks, /templates for templates, /keys for API keys and /usage for usage. Disk routes include /fork, /template, /checkpoints, /restore and /attachments. The running control service exposes complete request schemas at /api/reference.

Errors

Errors use {error:{code,message}}. Unconfigured storage returns 503. Authorization failures are not retryable without correcting credentials. Reuse an operation ID when retrying checkpoint or restore requests; use a new ID for a new intended operation.

Attachments

Create a writer with owner and ttl_seconds. Immutable reader attachments currently fail closed pending trusted ext4 journal replay qualification. Renew through /attachments/{id}/renew. DELETE revokes the attachment. Connection material only appears in the create response.

API reference Live OpenAPI schemas