JDSS/mem0
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(docs): add Token prefix to Events API code examples (#3927)

Browse Source
This commit is contained in:
Agam Pandey
2026-03-28 20:38:42 +05:30
committed by GitHub
parent 13d42a99e9
commit ece654811a
3 changed files with 59 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/api-reference/events/get-events.mdx
+1 -2
View File
@@ -10,5 +10,4 @@ List recent events for your organization and project.
- **Dashboards**: Summarize adds/searches over time by paging through events.
- **Alerting**: Poll for `FAILED` events and trigger follow-up workflows.
- **Audit**: Store the returned payload/metadata for compliance logs.
- **Audit**: Store the returned payload/metadata for compliance logs.
docs/api-reference/memory/add-memories.mdx
+4
View File
@@ -52,6 +52,10 @@ Provide at least one message or direct memory string. Most callers supply `messa
> \* Provide at least one `messages` entry to describe what you are storing. For scoped memories, include `user_id`. You can also attach `agent_id`, `app_id`, `run_id`, `project_id`, or `org_id` to refine ownership.
<Tip>
Need more details? See [all request parameters](#body-messages) below for complete field descriptions, types, and constraints.
</Tip>
## Response
Successful requests return an array of events queued for processing. Each event includes the generated memory text and an identifier you can persist for auditing.