Delete a Memory

Deletes a Memory. Deletion produces a version snapshot with operation=deleted. Historical version content is retained and remains available through the version endpoints. To physically remove the stored content bytes of a version, use Redact a Memory version.

Path

DELETE /api/v1/forward/memory_stores/{memory_store_id}/memories/{memory_id}

Headers

Header	Required	Description
`Authorization`	Yes	`Bearer <PAT or admin SAT>`

Path parameters

Parameter	Type	Required	Description
`memory_store_id`	string	Yes	Memory Store ID (`memstore_...`).
`memory_id`	string	Yes	Memory ID (`mem_...`).

Example request

curl -X DELETE "https://api.qoder.com/api/v1/forward/memory_stores/memstore_00mc7mukn7lkxr454tjd/memories/mem_00mc7mvag5u68kkfvxhy" \
  -H "Authorization: Bearer $QODER_ACCESS_TOKEN"

Example response

HTTP 200 OK

{
  "id": "mem_00mc7mvag5u68kkfvxhy",
  "type": "memory_deleted",
  "deleted": true
}

Response fields

Field	Type	Description
`id`	string	ID of the deleted Memory.
`type`	string	Always `memory_deleted`.
`deleted`	boolean	Whether the Memory was deleted.

Notes

After deletion, the same path can be used to create a new Memory with a new mem_ ID. Memories in an archived Memory Store cannot be deleted. The endpoint returns 409.

Errors

HTTP	Type	Trigger
400	`invalid_request_error`	A path parameter is invalid.
401	`authentication_error`	The authentication token is missing or invalid.
403	`permission_error`	The caller cannot access the resource.
404	`not_found_error`	The Memory Store or Memory does not exist, or is not visible across users.
409	`conflict_error`	The Memory Store is archived.
500/502/503	`api_error`	Forward or a dependent service failed.

​Path

​Headers

​Path parameters

​Example request

​Example response

​Response fields

​Notes

​Errors