Skip to main content
DELETE
Delete memory

When to use it

  • Right-to-deletion – remove a specific user’s memory upon request
  • Cleanup – delete outdated or incorrect memories
  • Privacy controls – let end users delete their own data through your app
To remove documents (knowledge) instead of user memories, use POST /knowledge/delete_knowledge.
This operation is irreversible. Once deleted, the memory cannot be recovered.

Endpoint

  • Auth: Bearer token
  • Idempotency: Idempotent - re-sending for an already-deleted memory returns 200 with user_memory_deleted: false
  • Async: No

Example

Query parameters

Response

  • Before this: List data (kind: "memories") – browse memories before deleting
  • Alternative: Delete tenant – delete all memories in a tenant at once

Errors

Common codes: 400 INVALID_PARAMETERS, 404 MEMORY_NOT_FOUND. See Error Responses for the full list.

Authorizations

Authorization
string
header
required

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

Query Parameters

tenant_id
string
required

Tenant ID

Example:

"tenant_1234"

memory_id
string
required

Unique identifier of the memory to delete

Example:

"memory_1234"

sub_tenant_id
string | null

Sub-tenant ID

Example:

"sub_tenant_4567"

Response

Successful Response

Response model for deleting a user memory.

user_memory_deleted
boolean
required

Confirms whether the specific memory was successfully deleted

Example:

true

success
boolean
default:true

Indicates whether the memory deletion operation was successful

Example:

true