Skip to main content
Recallio Memory stores conversational or assistant-derived facts so your automations can reference prior interactions. Use these pages to understand how the Memory endpoints complement the Knowledge Base.

​
Core capabilities

  • Store user-specific memories with /api/Memory/write, tagging and scoping them per user or project.
  • Retrieve relevant facts in real time with /api/Memory/recall and refine results with thresholds and tags.
  • Summarize & explore topics with /api/Memory/recall-summary and /api/Memory/recall-topics to power profile views.
  • Administer the dataset with /api/Memory/delete and /api/Memory/export (Manager role required).
All Memory endpoints require an API key from Dashboard → API Keys. Use a key with the Manager role for delete or export operations.

​
Endpoint quick reference

​
Before you start

  1. Generate an API key and store it securely. Keys map to a role; choose Manager if you need deletion or export access.
  2. Align on consent. The consentFlag field must be true for every stored memory to meet compliance requirements.
  3. Decide on scoping. Use projectId to partition memories per environment, and unique userId values for personalized recall.

​
Where to go next

Memory Kick Start

Learn how to write your first memory and retrieve it with /api/Memory/recall.

Memory Deep Dive

Explore payload schemas, query tuning, and admin workflows for Memory.
Need the full schema? Refer to the Recallio Swagger reference.