Skip to main content
DELETE
JavaScript

Overview

Permanently delete a corpus and all its associated resources. This operation cascades through all files, strings, URLs, and social media imports, removing storage objects and vector embeddings from Qdrant.
Irreversible Operation: This action cannot be undone. All indexed data, resources, and query history will be permanently deleted.
Alternative: If you want to temporarily disable access, set is_published: false via PATCH instead of deleting.

Authentication

Requires valid JWT token or session authentication. You must own the target corpus.

Path Parameters

UUID
required
Identifier of the corpus to delete.Example: 8d0f0a5d-4b5e-4c09-9db6-0e9d2aa8a9fd

Example request

Response Codes

No Content
Deletion successful. No response body is returned.
Forbidden
The corpus belongs to another user. Cannot delete corpora you don’t own.
Not Found
Corpus doesn’t exist or you don’t have access to it.
Conflict
Backend failed to remove remote index or storage objects. Retry once and contact support if the issue persists.Possible causes:
  • Vector database connection timeout
  • Storage service unavailable
  • Partial deletion occurred

What Gets Deleted

The delete operation removes:
  • Corpus metadata - Name, description, settings
  • All resources - Files, strings, URLs, social media imports
  • Storage objects - Uploaded files and processed content
  • Vector embeddings - All chunks removed from Qdrant
  • Query history - All past queries and retrievals for this corpus
  • Index data - Vector database collections and metadata
Total data loss: Everything associated with the corpus is permanently deleted across all storage systems.

Safe Deletion Workflow

Verify what will be deleted before proceeding:
Export data before permanent deletion:
Instead of deleting, make the corpus private and add an archive marker:
Benefits:
  • Reversible operation
  • Data preserved for future reference
  • Can restore if needed
  • Maintains audit trail
Handle 409 errors gracefully:
Delete multiple corpora safely:
Security: Deletion requests for corpora owned by other users return 403 Forbidden without revealing whether the corpus exists.
Production Best Practice: Implement a two-step deletion process: mark for deletion first, then actually delete after a grace period (e.g., 30 days).

Client examples

Authorizations

Authorization
string
header
required

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

Path Parameters

id
string<uuid>
required

A UUID string identifying this Corpora.

Response

204

No response body