Re-ingest an existing document
POST/v1/projects/:project_id/documents/:document_id/ingest
Re-runs ingestion for an existing document against its already-stored
source file. Existing chunks are discarded and the document is reset to
status=pending before re-processing. Use this to recover a document
stuck in processing/failed or to re-chunk with a different strategy
without re-uploading the file. Background by default (202); pass
?wait=true to run synchronously (201).
Request
Responses
- 201
- 202
- 400
- 401
- 403
- 404
- 409
- 413
- 429
- 500
- 502
- 4XX
Re-ingestion completed synchronously (only when ?wait=true).
Re-ingestion accepted. The document was reset to status=pending and processing runs in the background. Poll GET /v1/projects/{project_id}/documents/{document_id}/status.
The request was malformed or failed validation.
Unauthorized
Forbidden
Document not found
The project's storage_bytes quota is exceeded (QUOTA_STORAGE_EXCEEDED). Delete stored content, or raise the quota — no window reset clears a stored total, so no Retry-After is sent.
The file is too large to re-ingest synchronously (?wait=true). Retry in background mode.
QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens
Response Headers
Seconds until the quota window admits a request again
Unexpected server error — INTERNAL_ERROR, with the raw message never forwarded
The deployment's admission service is asked about this write and did not answer — ADMISSION_UNAVAILABLE; the write did not happen
The deployment's admission service refused this write — answered under the service's own 4xx status, with its code (matching ^[A-Za-z_][A-Za-z0-9_]{0,63}$, not necessarily an ERROR_CODES key), message and meta; the write did not happen. A status this operation also declares on its own is documented there