Extraction
Get Extraction Result
Retrieve the results of a completed processing job
GET
Overview
The Get Job Results endpoint retrieves the processed data from a completed job. This endpoint should only be called after confirming the job status is “completed” using the status endpoint.Results are only available for completed jobs. Check job status first to ensure processing has finished.
Path Parameters
The unique identifier of the extraction job
Response
The response structure depends on the job type (extraction, parsing, classification, etc.).Extraction Job Results
Unique identifier for the extraction job
Current status of the job, lowercase: “queued”, “processing”, “completed”, “review”, or “failed”. The result field is populated when status is “completed” or “review”.
Original filename of the uploaded document
Presigned download URL for the uploaded document. Expires roughly an hour after the response is generated; re-issue this request to get a fresh URL.
ISO 8601 timestamp when the job was created
ISO 8601 timestamp when the job was last updated
Job metadata containing:
order: Array of extracted field names in orderschema: The JSON schema used for extractionpage_count: Number of pages in the document
The extracted data matching the provided JSON schema. Present when status is “completed” or “review”. Each field contains:
value: The extracted value, matching the schema typescore: Confidence object with:grounding_score: Confidence (0-1) that the value was located in the document;0.0when citations are disabledextraction_score: Confidence (0-1) in the extracted value itself, ornull
citation: Where the value was found, ornullwhen citations are disabled or the value could not be grounded:bbox:[left, top, right, bottom]in PDF point space (origin: top-left)page: Page number where the value was found (1-indexed)page_width: Width of the source page in pointspage_height: Height of the source page in points
value is an array of objects whose sub-fields each carry their own value, score, and citation; the array field itself also carries an aggregated score and citation: null. Arrays nested below the top level omit the citation key entirely.The nested score/citation shape applies to citation-enabled jobs and to the default
gamma model tier. Jobs run with enable_citations=false on the alpha, beta, or delta tiers return a legacy flat shape instead: each field is {"value": ..., "score": <number>} with no citation key.Complete Workflow Example
Here’s a complete example of submitting a job, monitoring its progress, and retrieving results:Result Data Structure
Extracted Field Format
Each extracted field in theresult object contains:
value: The extracted value, matching the schema type (string, number, boolean, or an array of objects for array fields)score: A confidence object withgrounding_score(0-1 confidence the value was located in the document;0.0when citations are disabled) andextraction_score(0-1 confidence in the value itself, ornull)citation: A citation object indicating where the value was found, ornullwhen citations are disabled or the value could not be grounded
value is an array of objects whose sub-fields each carry their own value, score, and citation.
Citation Format
Each citation object contains:bbox:[left, top, right, bottom]coordinates in PDF point space (origin: top-left)page: The page number where the value was found (1-indexed)page_width: Width of the source page in pointspage_height: Height of the source page in points
Confidence Scores
- 0.9-1.0: Very high confidence, extraction is very likely correct
- 0.8-0.9: High confidence, extraction is likely correct
- 0.7-0.8: Good confidence, may warrant review for critical applications
- 0.6-0.7: Medium confidence, should be reviewed
- Below 0.6: Low confidence, likely needs manual verification
Error Handling
Job Still Processing (200)
Job Still Processing (200)
The endpoint always returns 200 for an existing job. While the job is queued or processing, the response simply has no
result field; keep polling until the status is “completed” or “review”.Job Failed (200)
Job Failed (200)
A failed job also returns 200, with status “failed” and the failure reason in the
error field.Job Not Found (404)
Job Not Found (404)
The job ID is invalid, belongs to another organization, or the job has been deleted. Verify you’re using the correct job ID.

