Skip to main content
POST /openapi/memorylake/api/v2/projects/{id}/memories/conflicts/{conflictId}/resolve
Records the user’s decision on a conflict. Depending on the strategy, one or more of the conflicting memories may be forgotten — those IDs come back in forgotten_memory_ids so your UI can update the corresponding memory rows.
Permission required: project:mem_conflict_resolve · instance

​
Path Parameters

​
id
string
required
Project ID
​
conflictId
string
required
Conflict ID

​
Request Body

​
strategy
string
required
Resolution strategy. Each strategy fits a particular conflict shape:
StrategyWhat it doesMemories forgotten
keep_memoryKeep one memory from the conflict set; drop the rest. Requires keep_memory_id. Typical for memory-vs-memory.The memories not chosen
trust_memoryKeep the memory and treat the file-side disagreement as resolved. Typical for memory-vs-document.None
trust_documentDrop the conflicting memory in favor of the document. Typical for memory-vs-document.The conflicting memory
dismissMark as resolved without changing any memories — use when the conflict is a false alarm.None
​
keep_memory_id
string
The memory_id to keep. Required when strategy is keep_memory; ignored otherwise.
curl -X POST 'https://app.memorylake.ai/openapi/memorylake/api/v2/projects/proj-a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6/memories/conflicts/conf-abc123/resolve' \
  -H 'Authorization: Bearer sk_xxxxxx' \
  -H 'Content-Type: application/json' \
  -d '{
    "strategy": "keep_memory",
    "keep_memory_id": "mem-002"
  }'

​
Response

​
data
object
{
  "success": true,
  "data": {
    "id": "conf-abc123",
    "resolved": true,
    "strategy": "keep_memory",
    "resolve_id": "resv-0001",
    "forgotten_memory_ids": ["mem-001"]
  }
}