Delete a memory

POST 
/api/v1/llm/delete-memory

Requests deletion of a memory by ID. Full project/user ownership checks are not currently enforced for these by-ID operations. They are not a supported access boundary for an untrusted end-user client. Deletion does not remove copies already included in conversation context or confirm backup erasure. See Memory.

The following access conditions are preserved as declared intent and are not implemented by generated code: Authorized scoped domain action.

Use this in a guide: Use remembered preferences in a returning user’s conversation

Request

Responses

200

Memory deleted

Schema-valid request illustration; replace example identifiers and confirm operation prerequisites.

Section ID: DOC-MA-conversations-api-deleteMemory#example-conversations-deleteMemory-request

Request example

{
  "memoryId": "example_123"
}

Guide request for Remove the selected record. Replace example resource identifiers with your own authorized values.

Section ID: DOC-MA-conversations-api-deleteMemory#example-cookbook-managed-agents-memory-knowledge-index-05-request

Request example

{
  "memoryId": "mem_abc123"
}

Illustrative response shape; omitted default fields and actual outcomes depend on the operation.

Section ID: DOC-MA-conversations-api-deleteMemory#example-conversations-deleteMemory-response

Response example

{
  "success": true
}

Document ID: DOC-MA-conversations-api-deleteMemory. Section identities and revisions.

Section	Stable reference
Delete a memory	DOC-MA-conversations-api-deleteMemory#overview
Request	DOC-MA-conversations-api-deleteMemory#request
Responses	DOC-MA-conversations-api-deleteMemory#responses