From dbf143f330092d1a292641d51b5c7fb1b3e15e48 Mon Sep 17 00:00:00 2001 From: James Yang Date: Wed, 2 Sep 2026 20:09:41 -0400 Subject: [PATCH] fix(docs): point backfill guide at real ingest API pages Mintlify only sees static files, so the invented OpenAPI child paths were failing the broken-link check. --- apps/docs/ingestion/batch-ingest-historical-data.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/apps/docs/ingestion/batch-ingest-historical-data.mdx b/apps/docs/ingestion/batch-ingest-historical-data.mdx index 17ff4e1b..10230dd9 100644 --- a/apps/docs/ingestion/batch-ingest-historical-data.mdx +++ b/apps/docs/ingestion/batch-ingest-historical-data.mdx @@ -15,7 +15,7 @@ Use `POST /v3/documents/batch` to backfill exports, emails, messages, or other d Backfill dated content by setting `documentDate` on each document, sorting the source records oldest to newest, and sending them in batches. Each request can contain up to 600 documents. -**Endpoint:** [`POST /v3/documents/batch`](/api-reference/ingest/batch-add-documents) +**Endpoint:** [`POST /v3/documents/batch`](/api-reference/ingest) @@ -93,7 +93,7 @@ def backfill_historical_data(source_documents: list[dict[str, str]]) -> None: ## Optional: wait for processing to finish -**Endpoint:** [`GET /v3/documents/{id}`](/api-reference/documents/get-document) +**Endpoint:** [`GET /v3/documents/{id}`](/api-reference/ingest) The batch endpoint returns after accepting the documents. If a later step depends on completed memory generation, poll the returned document IDs until both `status` and `dreamingStatus` are `done`.