GET /documents/{job_id}/structured, exposed in the SDKs as get_structured_result. The result is a ParseStructuredDocument: a set of pages, each holding its elements in reading order, with tables, chart data, recognized labels, positions, and confidence carried on the elements themselves. For the readable and interchange formats and how to choose among them, see choosing an output format.
Document
The top-level object of a structured parse.Confidence scores
The document-level summary carried onconfidence.
Page
One page of the document. Elements sit inelements, already in reading order.
Element
One piece of content.label, text, bbox, reading_order, and confidence are always present; the rest appear when they apply.
Treat
label as an open set. New roles can appear, so branch on the values you handle and fall through gracefully on the rest.Table
The grid held by aTable element.
Table cell
One cell within a table.Bounding box
A rectangle on a page. An element’sbbox is in pixel coordinates with a top-left origin; a page’s page_bbox is in PDF points with a bottom-left origin.
Chart data
The digitized plot carried by aChart element’s chart_data.
Series
One plotted series within a chart.Data point
One digitized value on a series.Axis
Calibration of one axis, including the fit from pixels to data values.Chart text
Each entry in an element’socr_text array is one recognized label from a chart, such as an axis title or a data label.
Reading these in code is covered in extracting chart data.
Job status
Returned byGET /documents/{job_id}. Reports where a job is and, once complete, a summary of what was found.
Related
The parsed document
The model these fields express.
Formats and capabilities
Supported inputs, formats, and job statuses.