compute

DELETE /v1/compute/clusters/{clusterId}

Delete a cluster and every machine in it.

All compute endpoints

All developer docs

Authentication

Send an API key as a bearer token. The key must carry the sites.delete permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X DELETE https://api.zinndigital.com/v1/compute/clusters/{clusterId} \
  -H "Authorization: Bearer zdk_live_…"

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

202. ⛔ Irreversible: every node is deleted with its disk, its floating IPs are released, its meter is settled, and the network and the cluster's keys are removed. Refused while the cluster is still being built. Requires sites.delete.

Parameters

NameTypeRequiredWhat it is
clusterId (path)UuidYesThe cluster's id, as listComputeClusters reports it.

Response

NameTypeRequiredWhat it is
idUuidYesUUIDv7 identifier — sortable by creation time (docs/02 §8).
namestringYes
deploy_targetstringYes
zonestringYes
plan_codestringYes
imagestringYes
worker_countintegerYes
install_argocdbooleanYes
deploy_sample_appbooleanYes
statusstring<pending, provisioning, bootstrapping, ready, failed, terminating, terminated>Yes
messagestringYes
kubernetes_versionstringYes
argocd_versionstringYes
ready_nodesintegerYes
sample_app_healthstringYesArgo CD's sync/health for the sample application, e.g. Synced/Healthy.
api_addressstringYesThe Kubernetes API's public address (port 6443).
network_idstringYes
nodesComputeServer[]Yes
created_atstringYes
ready_atobjectYes

Errors this endpoint can return

401 · 403 · 404 · 422 · 429 · 503