Skip to main content
DELETE
JavaScript

Overview

Permanently delete a URL resource along with its crawled content, metadata, and vector embeddings. This immediately removes the web page content from search results and retrieval operations.
Irreversible: Deletion cannot be undone. The URL record, crawled content, and all vector embeddings are permanently removed.
Use cases: Removing outdated web content, refreshing stale pages, managing dead links, or retracting content from sources that no longer exist.

Authentication

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

Path Parameters

UUID
required
URL resource identifier returned when the URL was created.Example: f0d6fe08-87c8-4eb0-80d8-7a2de638514b

Example request

Response Codes

No Content
URL successfully deleted. No response body returned.
Not Found
URL does not exist, was already deleted, or belongs to a corpus you don’t own.

What Gets Deleted

  • URL record - Database entry with URL and metadata
  • Crawled content - Extracted text and page information
  • Vector embeddings - All chunks removed from Qdrant
  • Crawl metadata - Content type, title, description, and sitemap info
Storage impact: Corpus size reported by GET /api/corpora/ decreases after background cleanup completes.

Common Use Cases

Delete and re-add URLs to fetch updated content:
Refresh strategy: Schedule periodic refreshes for documentation sites that update frequently (e.g., weekly or monthly).
Remove multiple URLs from a specific domain or pattern:
Replace URLs from old domain with new domain:
Remove URLs based on age or relevance:
Remove all URLs added via sitemap scraping:
Use case: Useful when sitemap scraping added too many irrelevant pages.
Content freshness: Set up automated workflows to periodically refresh documentation URLs (delete old → re-add new) for sources that update frequently.
Other resources unaffected: Removing URLs does not affect files or strings in the same corpus. Each resource type is independent.

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 URL.

Response

204

No response body