Delete a CoreCluster
Deletes the CoreCluster for good, with its capacity and SSH address; read GET / first. Without allow_non_empty only an empty CoreCluster is deleted; with it, every site, environment and deleted site in its grace period goes too, with no final snapshot, and so do their snapshots, except the ones the preview counts in kept_snapshots, which stay until their retention ends. The CoreCluster reads state deleting until it is gone, then answers 404.
Path parameters
The id of a CoreCluster. Digits only. At least 1.
Body
True to delete everything that is still on the CoreCluster with it. Defaults to false.
The CoreCluster's name, exactly.
Returns
202 The deletion has started. Poll the operation until it finishes.
Fields of the 202 answer
A change the Control Panel is making or has made. A save or an action that starts work answers one in operation; read it again by id with GET / until status is completed or failed. Both answers have this shape; the few endpoints that answer a different one say so.
Fields
The cluster the operation runs on.
Why the operation failed, in plain words. Null unless status is failed.
A stable code for the failure.
True when the change applies without a maintenance window.
What the operation did differently on purpose. Empty when nothing.
Fields of each item
Who asked for the change.
Present on some site creations and copies.
Always null here. A one-time result is read once with the reveal endpoint.
nonependingavailableviewedWhat a retry needs first, if anything.
Who revealed a one-time result and when, when there was one.
siteclusterbatchThe website the operation belongs to. Null for a cluster's own operation.
Where a change is. completed and failed are final; every other status means the change is still running and blocks another change to the same site.
pendingcommittedrolling_outexecutingcompletedfailedThe key of the step the operation is at. Null once it has completed.
Fields of each item
One of done, current, todo, failed or skipped.
The kind of change, such as crons_change or redirects_change.
If it is refused
| Status | Reason | What to do |
|---|---|---|
401 | none | Send a valid token as Authorization: Bearer <token>. |
403 | company_unavailable | Your company is unavailable. |
403 | scope_required | Use a token with the scope named in scope. |
403 | two_factor_required | Turn on two-factor on your account, then send again. |
404 | feature_off | This feature is not on for your organisation yet. |
409 | cluster_deleting | The cluster is being deleted. Nothing can be changed on it. |
409 | cluster_not_empty | The cluster still holds sites, environments or snapshots. Show the person what would be removed and call again only with their agreement. |
409 | legacy_cluster | Corefinity manages this cluster. Contact support to change its package or delete it. |
409 | cluster_busy | Another change to the cluster is running. Wait for it to finish, then try again. |
409 | staff_removal | The cluster holds something only Corefinity can remove. Contact support to delete it. |
422 | confirm_mismatch | Send the confirmation exactly as the field named in field asks for it. |
422 | invalid | Fix the field named in field; errors says why. |
429 | rate_limited | Wait for the seconds in Retry-After. |
502 | none | Read the message; it says what happened. |
503 | switched_off | Corefinity has switched this action off for the moment. Try again later. |
Reasons are listed by name in Errors and refusals.
The same task elsewhere
curl -X DELETE https://manage.corefinity.com/api/corestack/clusters/1017 \
-H "Authorization: Bearer $COREFINITY_TOKEN" \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-d '{
"confirm_name": "Northwind spare"
}'use Illuminate\Support\Facades\Http;
$response = Http::withToken(env('COREFINITY_TOKEN'))
->acceptJson()
->delete('https://manage.corefinity.com/api/corestack/clusters/1017', [
'confirm_name' => 'Northwind spare',
]);
$data = $response->json();const res = await fetch('https://manage.corefinity.com/api/corestack/clusters/1017', {
method: 'DELETE',
headers: {
Authorization: `Bearer ${process.env.COREFINITY_TOKEN}`,
Accept: 'application/json',
'Content-Type': 'application/json',
},
body: JSON.stringify({
confirm_name: 'Northwind spare',
}),
});
// An answer with no body (204) has nothing to parse.
const text = await res.text();
const data = text && JSON.parse(text);import os
import requests
res = requests.delete(
"https://manage.corefinity.com/api/corestack/clusters/1017",
headers={
"Authorization": f"Bearer {os.environ['COREFINITY_TOKEN']}",
"Accept": "application/json",
},
json={
"confirm_name": "Northwind spare",
},
)
data = res.json() if res.content else None{
"operation": {
"applied_at": null,
"can_retry": false,
"cluster": {
"id": 1017,
"name": "Northwind UK 1"
},
"committed_at": null,
"completed_at": null,
"created_at": "2026-11-14T10:00:00Z",
"environment": null,
"error": null,
"failure_reason": null,
"from_version": null,
"hot": false,
"id": 5140,
"install": null,
"label": "Sites removed",
"notes": [],
"parent_operation_id": null,
"requested_by": {
"id": 2041,
"name": "Eleanor Finch"
},
"result": null,
"result_state": "none",
"retried_by_operation_id": null,
"retries_operation_id": null,
"retry_requires": null,
"scope": "cluster",
"site": null,
"status": "pending",
"status_label": "Removing the sites, 1 site left",
"step": "sites_removed",
"steps": [
{
"key": "requested",
"label": "Requested",
"state": "done"
},
{
"key": "sites_removed",
"label": "Sites removed",
"state": "current"
},
{
"key": "snapshots_deleted",
"label": "Snapshots deleted",
"state": "todo"
}
],
"subject": null,
"summary": "Delete cluster",
"to_version": null,
"type": "cluster_delete",
"type_label": "Delete cluster"
}
}{
"message": "Unauthenticated."
}{
"code": "company_unavailable",
"message": "Your company is unavailable.",
"reason": "company_unavailable"
}{
"code": "feature_off",
"message": "Not found.",
"reason": "feature_off"
}{
"code": "cluster_deleting",
"message": "This cluster is being deleted",
"reason": "cluster_deleting"
}{
"code": "confirm_mismatch",
"errors": {
"confirm_name": [
"Type the cluster's name to confirm"
]
},
"field": "confirm_name",
"message": "Type the cluster's name to confirm",
"reason": "confirm_mismatch"
}{
"code": "rate_limited",
"message": "Too many requests. Try again in 60 seconds.",
"reason": "rate_limited",
"retry_after_seconds": 60
}{
"message": "The change could not be saved. Contact support."
}{
"code": "switched_off",
"message": "Deleting is switched off at the moment",
"reason": "switched_off",
"switch": "delete"
}Try it is off for this endpointIt deletes data that cannot be brought back. Copy the request and run it yourself when you are sure.