Delete Cluster

curl --request DELETE \
  --url https://api.mixpeek.com/v1/clusters/{cluster_id} \
  --header 'Authorization: Bearer <token>'

{
  "status": 123,
  "error": {
    "message": "<string>",
    "type": "<string>",
    "code": "<string>",
    "details": {}
  },
  "success": false
}

Clusters

Delete Cluster

This endpoint deletes a cluster and all its resources including:

Running Ray jobs (cancels active jobs)
Cluster triggers
Execution history (clustering_results)
S3 artifacts (parquet files, documents, members)
Related tasks
Clustering jobs
MongoDB cluster metadata
Output collections created by the cluster (by default)

By default, output collections created by the cluster are cascade-deleted along with the cluster. Pass cascade_output_collections=false to preserve them (useful when the cluster output documents were enriched / promoted into user-managed data).

The deletion is performed synchronously and returns when complete.

DELETE

clusters

{cluster_id}

Delete Cluster

curl --request DELETE \
  --url https://api.mixpeek.com/v1/clusters/{cluster_id} \
  --header 'Authorization: Bearer <token>'

{
  "status": 123,
  "error": {
    "message": "<string>",
    "type": "<string>",
    "code": "<string>",
    "details": {}
  },
  "success": false
}

Authorizations

Authorization

string

header

required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

cluster_id

string

required

Cluster ID

Query Parameters

cascade_output_collections

boolean

default:true

When true (default), the cluster's output collections are deleted alongside the cluster. Set to false to preserve them.

Response

Successful Response

Stream cluster data Create Cluster Trigger