Delete Context

client.context.delete(
    type="knowledge",
    database="acme_corp",
    collection="team_docs",
    ids=["policy_main", "runbook_deploy"],
)

await client.context.delete({
  type: "knowledge",
  database: "acme_corp",
  collection: "team_docs",
  ids: ["policy_main", "runbook_deploy"],
});

curl -X DELETE 'https://api.hydradb.com/context' \
  -H "Authorization: Bearer <your_api_key>" \
  -H "API-Version: 2" \
  -H "Content-Type: application/json" \
  -d '{
    "database": "acme_corp",
    "collection": "team_docs",
    "ids": ["policy_main", "runbook_deploy"],
    "type": "knowledge"
  }'

{
  "success": true,
  "data": {
    "success": true,
    "message": "Delete completed",
    "results": [
      { "id": "policy_main", "deleted": true, "error": null },
      { "id": "runbook_deploy", "deleted": true, "error": null }
    ],
    "deleted_count": 2
  },
  "error": null,
  "meta": {
    "request_id": "9d13aef4-02f4-4e73-8c62-4c2601d04f9d",
    "latency_ms": 12.3
  }
}

DELETE

context

client.context.delete(
    type="knowledge",
    database="acme_corp",
    collection="team_docs",
    ids=["policy_main", "runbook_deploy"],
)

await client.context.delete({
  type: "knowledge",
  database: "acme_corp",
  collection: "team_docs",
  ids: ["policy_main", "runbook_deploy"],
});

curl -X DELETE 'https://api.hydradb.com/context' \
  -H "Authorization: Bearer <your_api_key>" \
  -H "API-Version: 2" \
  -H "Content-Type: application/json" \
  -d '{
    "database": "acme_corp",
    "collection": "team_docs",
    "ids": ["policy_main", "runbook_deploy"],
    "type": "knowledge"
  }'

{
  "success": true,
  "data": {
    "success": true,
    "message": "Delete completed",
    "results": [
      { "id": "policy_main", "deleted": true, "error": null },
      { "id": "runbook_deploy", "deleted": true, "error": null }
    ],
    "deleted_count": 2
  },
  "error": null,
  "meta": {
    "request_id": "9d13aef4-02f4-4e73-8c62-4c2601d04f9d",
    "latency_ms": 12.3
  }
}

Specify the resource category with the type parameter:

type=knowledge (default) - delete knowledge sources.
type=memory - delete memories.

Pass one or more IDs in ids. Send database, collection, ids, and type as top-level fields in the request body.

Knowledge deletion

Use type: "knowledge" and pass knowledge ids in the ids array. Include the same collection you used when ingesting the knowledge; omitting it targets the default collection.

client.context.delete(
    type="knowledge",
    database="acme_corp",
    collection="team_docs",
    ids=["policy_main", "runbook_deploy"],
)

await client.context.delete({
  type: "knowledge",
  database: "acme_corp",
  collection: "team_docs",
  ids: ["policy_main", "runbook_deploy"],
});

curl -X DELETE 'https://api.hydradb.com/context' \
  -H "Authorization: Bearer <your_api_key>" \
  -H "API-Version: 2" \
  -H "Content-Type: application/json" \
  -d '{
    "database": "acme_corp",
    "collection": "team_docs",
    "ids": ["policy_main", "runbook_deploy"],
    "type": "knowledge"
  }'

{
  "success": true,
  "data": {
    "success": true,
    "message": "Delete completed",
    "results": [
      { "id": "policy_main", "deleted": true, "error": null },
      { "id": "runbook_deploy", "deleted": true, "error": null }
    ],
    "deleted_count": 2
  },
  "error": null,
  "meta": {
    "request_id": "9d13aef4-02f4-4e73-8c62-4c2601d04f9d",
    "latency_ms": 12.3
  }
}

Memory deletion

Use type: "memory" and pass memory ids in the ids array. Include the same collection you used when ingesting the memories; omitting it targets the default collection.

client.context.delete(
    type="memory",
    database="acme_corp",
    collection="user_alex",
    ids=["mem_user_alex_tone"],
)

await client.context.delete({
  type: "memory",
  database: "acme_corp",
  collection: "user_alex",
  ids: ["mem_user_alex_tone"],
});

curl -X DELETE 'https://api.hydradb.com/context' \
  -H "Authorization: Bearer <your_api_key>" \
  -H "API-Version: 2" \
  -H "Content-Type: application/json" \
  -d '{
    "database": "acme_corp",
    "collection": "user_alex",
    "ids": ["mem_user_alex_tone"],
    "type": "memory"
  }'

{
  "success": true,
  "data": {
    "success": true,
    "user_memory_deleted": true
  },
  "error": null,
  "meta": {
    "request_id": "9d13aef4-02f4-4e73-8c62-4c2601d04f9d",
    "latency_ms": 12.3
  }
}

{
  "success": false,
  "data": null,
  "error": {
    "code": "SOURCE_NOT_FOUND",
    "message": "Source not found"
  },
  "meta": {
    "request_id": "9d13aef4-02f4-4e73-8c62-4c2601d04f9d",
    "latency_ms": 4.8
  }
}

Some additional notes

Partial-success semantics: For type=knowledge, each ID is reported independently in results[]. A failure on one ID does not stop the rest. For type=memory, the response reports an aggregate user_memory_deleted reflecting all listed IDs.
Retrieval drops the source immediately: Even before background cleanup finishes, deleted IDs disappear from /query and /context/list responses.
Mixed deletes need two calls: To delete both knowledge and memory items, send two requests - one with type=knowledge, one with type=memory.

Related Resources

Find IDs: List Documents
Perform a query: Query
Re-add content: Ingest Context
Bigger hammer: Delete Database - removes the entire database
Read more: Context Management - Overview

Authorizations

Authorization

string

header

required

API key sent as a Bearer token: "Bearer prefix.secret"

Body

application/json

Delete request

collection

string

Collection scope. Defaults to the default collection when omitted. Formerly sub_tenant_id; the sub_tenant_id alias is still accepted (deprecated).

Example:

"team_docs"

database

string

Database/Collection are the canonical v2 names; TenantID/SubTenantID are their deprecated aliases, reconciled by the TenantAliases middleware before binding so TenantID is always populated.

Example:

"acme_corp"

ids

string[]

IDs of the sources or memories to delete.

Example:

["HydraDoc1234", "HydraDoc4567"]

sub_tenant_id

string

deprecated

deprecated: use collection

Example:

"sub_tenant_4567"

tenant_id

string

deprecated

deprecated: use database

Example:

"tenant_1234"

type

enum<string>

Bucket to delete from: knowledge (default) or memory.

Available options:

knowledge,

memory

Example:

"knowledge"

Response

data

object

Show child attributes

Example:

{
  "deleted_count": 1,
  "message": "Success",
  "results": [
    {
      "deleted": true,
      "error": "",
      "id": "HydraDoc1234"
    }
  ],
  "success": true,
  "user_memory_deleted": 1
}

error

object

Error message, empty string on success.

Show child attributes

Example:

{
  "code": "DATABASE_NOT_FOUND",
  "message": "Database not found"
}

API Documentation

Databases

Context

Query

Connectors

Miscellaneous

Knowledge deletion

Memory deletion

Some additional notes

Authorizations

Body

Response

​Knowledge deletion

​Memory deletion

​Some additional notes

Authorizations

Body

Response

Knowledge deletion

Memory deletion

Some additional notes