---
title: "Delete Namespace"
method: DELETE
path: "/v1/namespaces/{namespace_identifier}"
tags: ["Namespaces"]
---

# Delete Namespace

`DELETE /v1/namespaces/{namespace_identifier}`

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/{task_id}.

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

## Path parameters

- `namespace_identifier` string, required — Either the namespace name or namespace ID

## Query parameters

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

## Response `200`

Successful Response

- unknown

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `422` — Validation Error
- `500` — Internal Server Error

---

[API](https://skmtc.net/mixpeek/apis/mixpeek-api.md) · [All operations](https://skmtc.net/mixpeek/apis/mixpeek-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mixpeek/mixpeek-api/versions/5d4c905106b4/schema)
