Docs · LLMs and developers
Reviewed2026-07-07Version3.12.1User memory
Session-authenticated routes for the signed-in user's memory surface.
User memory routes power the signed-in account memory view. They are workspace routes, not public token-authenticated API routes.
Routes
| Method | Path | Purpose |
|---|---|---|
GET | /api/user/memory | Return the signed-in user's memory summary in the current organization. |
PUT | /api/user/memory/candidates/:weaviateId | Approve or reject a user-scoped core memory candidate. |
POST | /api/user/memory/automation-rules/:templateId/unsuppress | Clear the caller's personal suppression cooldown for one habit. |
POST | /api/user/memory/automation-rules/:templateId/require-approval | Require or remove personal approval for one habit. |
Candidate review
const response = await fetch("/api/user/memory/candidates/mem_123", {
method: "PUT",
credentials: "include",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
action: "approve",
collection: "UserPreferences",
}),
});
const result = await response.json();
action must be approve or reject. collection is required because candidates can live in different memory collections.
For shared candidate behavior, see Core memory candidates. For personal habit controls, see Habit memory API.