diff --git a/apps/docs/snippets/api-v5-document-ingestion.mdx b/apps/docs/snippets/api-v5-document-ingestion.mdx
index 7b8049d4..623bfd94 100644
--- a/apps/docs/snippets/api-v5-document-ingestion.mdx
+++ b/apps/docs/snippets/api-v5-document-ingestion.mdx
@@ -25,7 +25,7 @@ POST /ns/user_1/document?dreaming=dynamic
 ```
 </CodeGroup>
 
-The response remains an acceptance result with `id` and `status`. Its `status` is the document's processing state after the request: `queued` when new work was queued, otherwise the document's current state (for example `done` for an unchanged duplicate, or `failed` for a metadata-only update to a failed document). Possible values: `unknown`, `queued`, `extracting`, `chunking`, `embedding`, `indexing`, `done`, `failed`. 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`. Its `status` is the document's processing state after the request: `queued` when new work was queued, otherwise the document's current state (for example `done` for an unchanged duplicate, or `failed` for a metadata-only update to a failed document). Possible values: `unknown`, `queued`, `extracting`, `chunking`, `embedding`, `indexing`, `done`, `failed`. 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
 
diff --git a/apps/docs/snippets/api-v5-document-updates.mdx b/apps/docs/snippets/api-v5-document-updates.mdx
index 5f9a3192..0b24d8f6 100644
--- a/apps/docs/snippets/api-v5-document-updates.mdx
+++ b/apps/docs/snippets/api-v5-document-updates.mdx
@@ -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
 
diff --git a/apps/docs/snippets/api-v5-rollout.mdx b/apps/docs/snippets/api-v5-rollout.mdx
index c9027434..422439c5 100644
--- a/apps/docs/snippets/api-v5-rollout.mdx
+++ b/apps/docs/snippets/api-v5-rollout.mdx
@@ -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