API reference
Every route the Interlaken orchestrator serves.
The reference below is generated from the spec the orchestrator itself emits, so it never drifts from what the control plane actually accepts. Each page covers one operation and carries a playground you can fire a real request from.
Every request needs a bearer token. Authentication covers how to get one, and Permissions and scopes covers what it is then allowed to do.
Identity and access
Sign in, second factors, machine credentials, and the roles and permissions that decide what a caller may do. 57 operations.
Compute
Virtual machines, microVMs and containers, together with the images, instance types and keys they are built from. 96 operations.
Storage
Block devices, their snapshots, object storage buckets and backup repositories. 27 operations.
Networking
Tenant VPCs and everything attached to them: subnets, interfaces, addresses, load balancers, gateways and policy. 75 operations.
Kubernetes
Managed Kubernetes clusters and their node pools. 9 operations.
Applications
Deploying from a Git repository: build servers, environments, connectors, runs and the webhooks that trigger them. 132 operations.
Agents and workflows
Agent definitions, the sessions they run in, the skills and tools they may call, and the workflows that sequence them. 118 operations.
Managed services
Databases, caches and queues the platform runs on your behalf. 14 operations.
Billing and support
Credit, invoices, usage, published prices, account limits and support tickets. 41 operations.
Platform
Which zone you are talking to, and the live event stream. 2 operations.
The spec itself
The prepared OpenAPI 3.0 document is served at /openapi/interlaken.json. Point a code generator at it to build a client in your own language.