Skip to navigation

November 15, 2026

Public API 0.11.0: Object Storage and Container Registry are back; Secret Manager and regional load balancers

The public API manages resources. Files, images, secret values and load balancer traffic stay on each product’s own endpoint, with the clients that already exist for them: S3 tools at <workspace>.blob.ibeestorage.com, docker at registry.ibee.ai, and bao or vault at your Secret Manager endpoint. Every call goes through the API gateway to the same portal logic the console uses.

Object Storage and Container Registry resume. The 3 November pause is over: bucket, bucket setting, custom domain, metrics and S3 key operations, and registry, plan, access token, repository, image, scan, security, SBOM and metrics operations answer again. Two operations are new:

  • POST /object-storage/buckets/{bucket_name}/empty-jobs starts a server-side job that permanently deletes every object in a bucket, so the bucket can be deleted. List, read and cancel jobs under the same path.
  • POST /container-registry/registries/{registry_id}/empty permanently deletes every repository and image in a registry, so the registry can be deleted. Send the registry’s name in confirm_registry_name.

Secret Manager replaces Secret Store. The /secret-store operations are removed. The new /secret-manager operations enable Secret Manager for a workspace, list and search secret names, create and update a secret’s metadata, show version history, delete, undelete or destroy versions, and manage app credentials (create, list, issue a secret ID, revoke). No operation reads or writes a secret value: use the Vault API at the workspace endpoint with an app credential. Scopes are secret-manager.read and secret-manager.write; app credentials also need workspace admin.

Regional load balancers. Load balancer operations now follow the regional load balancer service the console uses. Create and update take one full specification (POST /networking/load-balancers, PUT /networking/load-balancers/{load_balancer_id} with the current version), and every change needs an Idempotency-Key and answers 202 with an operation (GET /networking/load-balancers/operations/{operation_id}). New: GET /networking/load-balancers/regions and metrics. Removed: the separate L4 and L7 create and update operations and /status; the state is on the load balancer itself. Targets are private addresses in your VPC.

The active reference has 225 operations.