Changelog

Public API reference 0.6.0: the portal’s operations, and only those

The API reference is now 223 operations, lined up with what the portal offers and with what servers.com, Vultr and E2E Networks expose for the same products.

Removed (25). Operations the portal never used and no provider offers: on cloud and GPU VMs, resize-plan, resize-root-disk, mount-guidance/acknowledge, backups/policy/next-run-at and the manual backups/runs POST; the three VM console session operations; POST /cdn/generate-url; PATCH /networking/vpcs/{vpc_id}/subnets/{subnet_id}; the Secret Store PATCH operations on stores, secret values, identities and permissions; POST /container-registry/registries/{registry_id}/empty; and POST /billing/resource-eligibility (no pre-check: every billable create answers 402 with the reason). The block-storage attachments and detach operations, which needed a storage-node name, are gone too; attach volumes from the VM with POST /compute/cloud-vms/{vm_id}/actions/attach-volume.

Added (31). What the portal has and the API didn’t: bucket lifecycle, CORS, object-lock default, event notifications, custom domains and metrics (16 operations under /object-storage/buckets/{bucket_name}); POST /object-storage/credentials/{access_key_id}/revoke (the DELETE now deletes the record, as the portal does); GET /cdn/distributions/{distribution_id}/metrics; GET /block-storage/plans; workspace-wide snapshot and backup lists (GET /compute/cloud-vm-snapshots, GET /compute/cloud-vm-backups/runs) and backup deletion, with GPU twins; POST /networking/reserved-ips/convert, POST /networking/reserved-ips/{reserved_ip_id}/attach-direct and PUT /networking/vpcs/{vpc_id}/nat-gateways/{nat_gateway_id}/public-ip.

Request bodies. Load balancers take health_check, policy (timeouts, retries, proxy protocol) and observability; NAT gateway delete takes public_ip_action; port-forwarding rules can target a Virtual IP; VPC attach takes requested_private_ip; VM lists take search, sort_by and sort_direction; snapshot restores take VPC and SSH-key fields and target_volume_names; the portal-internal requested_by, admin_username and ssh_key_secret_refs fields are gone.

Clients generated from 0.5.0 keep working for every kept operation; the removed ones answer 404. New SDK, CLI and Terraform releases follow from this contract. See Using the S3 API for the object-storage split.