Retry document indexing
Re-queue a failed knowledge-base document for indexing. Use when a document upload reported an error indexing status and you fixed the underlying cause — the document’s chunks are re-extracted and re-indexed so the AI agent can retrieve them again. The retry is asynchronous: the endpoint returns 202 immediately with an empty body, and the document’s status transitions through pending to indexed (or back to error if it fails again) — poll GET /knowledge-bases/:id/documents for the outcome. Only failed documents are meaningfully retried. Requires an admin-class role and the knowledge:write scope; the call is audit-logged.
Authorizations
Dashboard JWT token from Clerk
Headers
Stripe-style idempotency token. Pass a stable, client-generated value (1-255 chars) to dedupe retries on transient timeouts. The same key+credential+path replays the original response for 24h on 2xx (5min on 4xx, 30s on 5xx). Returns 409 if a concurrent request with the same key is already in flight; replayed responses include the Idempotency-Replay: true response header.
1 - 255Sandbox opt-in for Clerk-session-authenticated requests. Set to true to route the call through the test-mode pipeline: no real provider delivery, no credits deducted, response meta.test_mode: true. Ignored for live API keys (dv_live_sk_*) — server-to-server clients must use a test-prefixed key (dv_test_sk_*) to exercise sandbox. Test-prefixed keys unconditionally enable sandbox regardless of this header.
true, false Path Parameters
Knowledge base id, as returned by GET /knowledge-bases.
Document id within that knowledge base, as returned by GET /knowledge-bases/:id/documents.
Response
Retry accepted — the document was queued for re-indexing and the outcome arrives asynchronously on the document's indexing status. The response body is empty.
Retry accepted — the document was queued for re-indexing and the outcome arrives asynchronously on the document's indexing status. The response body is empty.