Delete Namespace

curl --request DELETE \
  --url https://api.mixpeek.com/v1/namespaces/{namespace_identifier}

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

Namespaces

Delete Namespace

This endpoint deletes a namespace and ALL its resources including:

All buckets (with S3 objects, batches, uploads)
All collections (with Qdrant points, cache, webhooks)
All clusters (with Ray jobs, executions, triggers, S3 artifacts)
All retrievers (with executions, evaluations, interactions, cache)
Remaining MongoDB collections (tasks, uploads, taxonomies, API keys, etc.)
All S3 objects with namespace prefix
Qdrant collection (namespace’s vector database)
All namespace cache (across all scopes)
Analytics data (ClickHouse tables)
Namespace metadata

The deletion is performed asynchronously. Returns a task_id that can be used to poll for deletion progress via GET /v1/tasks/.

⚠️ WARNING: This operation is irreversible and will delete ALL data in the namespace!

DELETE

namespaces

{namespace_identifier}

Delete Namespace

curl --request DELETE \
  --url https://api.mixpeek.com/v1/namespaces/{namespace_identifier}

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

Headers

Authorization

string

Bearer token authentication using your API key. Format: 'Bearer sk_xxxxxxxxxxxxx'. You can create API keys in the Mixpeek dashboard under Organization Settings.

Example:

"Bearer YOUR_MIXPEEK_API_KEY"

Path Parameters

namespace_identifier

string

required

Either the namespace name or namespace ID

Examples:

"my_namespace"

"ns_1234567890"

Query Parameters

force

boolean

default:false

Force deletion even if batches are still processing. Without this flag, the endpoint returns 409 when active batches exist.

Response

Successful Response

Get Namespace Stats Clone Namespace