Requires extractions:write scope.
Use this endpoint for RPA or backend clients that need to submit several extraction jobs and poll for results later. The current backend implementation uses best-effort in-process background tasks; jobs can remain pending if the API process restarts while work is running.
Request Body
extraction_request supports review_contract, prompt, schema, model, extraction_mode, review_threshold, include_citations, agentic_ocr, and confidence_instruction. Prompt-only batch requests are accepted. If schema is provided, pass the extraction schema directly in the schema field with top-level named_entities and required keys.
include_citations is only valid for Advanced extraction. Do not set model or extraction_mode: "vlm" when include_citations is true.
Managed review opt-in
Set extraction_request.review_contract to "decisions_v1" only in an adopting integration. It is nested inside extraction_request, not at the batch body’s top level. Omitting it, or using "legacy", keeps existing robot behavior even in an enabled project with the same API-key owner.
Project activation and trusted caller access are also required. Existing document snapshots never convert on a retry or a new batch request. Inspect review_decision_managed in stored extraction results to select the contract. Managed decision state remains separate from batch technical completion; a completed batch does not approve its documents. See state-aware polling.
Request Example
Response
Returns 202 Accepted with a batch ID and one pending extraction item per document.
Get Batch Status
Requires extractions:read scope.
Poll this endpoint until the aggregate status is completed, failed, or partial_failed.
Path Parameters
Aggregate Status Values
Response
Example
Error Responses