Delete files

Removes one of the caller's org files from the index — its table of contents, passages, full-text rows, mentions and links — and its record.

DELETE /v1/knowledge/files/{id}

Knowledge → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/knowledge/files/{id}`
Method	`DELETE`
Operation	`delete_knowledge_files_by_id`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Removes one of the caller's org files from the index — its table of contents, passages, full-text rows, mentions and links — and its record. The file is gone from every read when this answers: its listing, its contents, search and retrieval. What the index held of it is removed after, a batch at a time, so forgetting a file of any size answers at once. The object itself stays in its bucket; delete it there. Drive calls this when it deletes a file.

Request

1 field.

Field	In	Type	Required	Description
`id`	path	string	yes	ID is the file's id, as POST /v1/knowledge/files answered it.

Response

Status	Body	Meaning
`200`	knowledge.forgotten	ok
`default`	problem-details	refused

200 body — 1 field.

Field	In	Type	Always	Description
`id`	body	string	—	ID is the file whose index was removed.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.

.ts

.py

.go

.rs

.java

import { Configuration, KnowledgeApi } from 'hanzoai';

const api = new KnowledgeApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.deleteKnowledgeFilesById({ id: 'id' });

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import KnowledgeApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = KnowledgeApi(client).delete_knowledge_files_by_id(id='id')

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.KnowledgeAPI.DeleteKnowledgeFilesById(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, knowledge_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = knowledge_api::delete_knowledge_files_by_id(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.KnowledgeApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new KnowledgeApi(client).deleteKnowledgeFilesById();

curl -X DELETE https://api.hanzo.ai/v1/knowledge/files/<id> \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches knowledge through the knowledge tool, which names its 9 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_knowledge_connectors"
         }
       }
     }'

Knowledge API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousDelete connectors NextList callback