scriptoriumadmin/supermemory
1
0
Fork 0
mirror of https://github.com/supermemoryai/supermemory.git synced 2026-10-10 03:28:14 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

docs(api): document 202 for v5 async ingest

Browse source
This commit is contained in:
Soham Daga 2026-10-05 16:12:03 -07:00
parent 8f8af5edff
commit a0b059a886
3 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
apps/docs/snippets/api-v5-document-ingestion.mdx
View file

@ -25,7 +25,7 @@ POST /ns/user_1/document?dreaming=dynamic
```
</CodeGroup>
The response remains an acceptance result with `id` and `status`. Repeating the v5 request with `id: "conv_1"` adds or diffs the new content into that document; it does not silently replace the canonical source.
The response remains an acceptance result with `id` and `status`, now returned as `202 Accepted` instead of `200`. Repeating the v5 request with `id: "conv_1"` adds or diffs the new content into that document; it does not silently replace the canonical source.
### Batch ingestion

2
apps/docs/snippets/api-v5-document-updates.mdx
View file

@ -59,7 +59,7 @@ The path `id` may be the Supermemory document ID or your caller-defined ID. It i
### Processing and conflicts
Content or file replacement is accepted before downstream processing completes. A document still processing, a namespace conflict, or a conflicting internal file path can return `409`; retry only after the conflicting operation reaches a terminal state.
Content or file replacement returns `202 Accepted` before downstream processing completes. A document still processing, a namespace conflict, or a conflicting internal file path can return `409`; retry only after the conflicting operation reaches a terminal state.
### Verification

2
apps/docs/snippets/api-v5-rollout.mdx
View file

@ -11,7 +11,7 @@ Record each legacy request, v5 request, expected semantic result, and intentiona
- Repeated POST appends or diffs; PATCH replaces canonical content.
- Batch outcomes preserve input order and surface partial failures.
- Metadata-only updates leave source content unchanged.
- Accepted writes are polled until processing reaches a terminal state.
- Accepted writes return `202` and are polled until processing reaches a terminal state.
### Compare reads and recall