MemorySync
API Reference

Forget Memory

Forget one or more integer memory IDs in the current project and end-user scope.

Endpoint and request fields

DELETE/memory/forget
200 OK
FieldTypeContract
memory_ids / memoryIdsinteger[]Required list of memory IDs. The official SDKs reject an empty list before sending.
reasonstringOptional application reason.

Forget selected memories

import os
from memorysync import MemorySyncClient
client = MemorySyncClient(
api_key=os.environ["MEMORYSYNC_API_KEY"],
base_url="https://api.memorysync.io",
project_id=os.environ["MEMORYSYNC_PROJECT_ID"],
end_user_id="usr_7f3a9c2e",
)
forgotten_ids = client.forget(
[101, 102],
reason="User requested deletion",
)

Result paths

ClientResult
Pythonforgotten_ids is list[int].
Node.jsforgottenIds is number[].
RESTThe response body is an array of integer IDs.
200-response.json
[101,102]

Errors and next action

The official SDKs reject an empty ID list before sending. Correct 4xx credentials, scope, IDs, or fields before trying again. For an interrupted request, reconcile through customer-visible records rather than assuming deletion did or did not occur.

Safety notes

Destructive-operation workflow

Safe forget workflow
  1. 01

    Select

    1

    Choose memory IDs through trusted application state.

  2. 02

    Authorize

    2

    Confirm the current user and product action may remove them.

  3. 03

    Submit

    3

    Send the IDs with an optional non-sensitive reason.

  4. 04

    Verify

    4

    Compare returned integer IDs with the requested set.

  5. 05

    Reconcile

    5

    If the response was interrupted, inspect customer-visible state before repeating.

Deletion boundaries

  • The operation accepts selected memory IDs; it is not a substitute for deleting records in your source systems.
  • Use the same trusted scope that was used to access the records.
  • Do not accept arbitrary destructive IDs directly from an untrusted client.
  • Keep user-facing completion language aligned with the IDs actually returned.
  • Coordinate broader privacy or account-erasure workflows in your application where required.
Was this page helpful?