Get the results of a completed automation app run.
The results from this endpoint are paginated. The has_more field in the response indicates if there are more results to fetch and the file_offset query parameter can be used to specify the starting point for the next set of results.
For an example of using file_offset to fetch all results, see the Retrieving paginated results code sample.
This API operation might return field names that differ from those in the automation project. The operation converts field names to valid Python variable names by:
Examples:
due date → due_datedriver's license → driver_s_license3rd category → _3rd_categorysecret_id → secret__idThese changes apply only to field names in the API response. The field names in the automation project are not changed.
Typically your organization ID. See Authorization and context identification for details.
The initial file index to start returning results from. Defaults to 0.
Status of the run. Possible values and meanings:
CANCELLED — A user cancelled the runCOMPLETE — The run successfully completed. A human review completed if it was required. Results are retrievable, but some fields may have failed and have the value ERROR.FAILED — The run failed to completePAUSED — This status is reserved for future useRUNNING — The run is in progress and is not pausedSTOPPED_AT_CHECKPOINT — A validation error has paused the run for human reviewWhen the run finished, in Unix time nanoseconds. null if run is still in progress.
Packet-level information (also known as case-level information) captured for the run, including optional edit history per cross-class field when include_review_results=true.
Cross-class fields consolidate data extracted from standard fields within a packet. For more information about packets and cross-class fields, see Extracting data from packets.
Indicates whether additional results are available beyond those included in the current response. Use the file_offset query parameter to specify the starting point when fetching the next set of results.
Whether to include human review details in the results. When set to true, various human review details are returned.
The following values are returned at the document level (files/documents/...):
review_completedclass_edit_historyclass_edit_history/timestampclass_edit_history/user_idclass_edit_history/modificationsclass_edit_history/modifications/messageThe following values are returned at the field level (files/documents/fields/...):
edit_historyedit_history/timestampedit_history/user_idedit_history/modificationsedit_history/modifications/messageThe following values are returned at the packet level (also known as case level) (case_info/fields/...):
edit_historyedit_history/timestampedit_history/user_idedit_history/modificationsedit_history/modifications/messageSee the response schema for details and descriptions.
Whether to include confidence scores in the results. When set to true, various confidence scores are returned.
The following values are returned at the document level (files/documents/...):
classification_confidenceThe following values are returned at the field level (files/documents/fields/...):
confidence/modelconfidence/ocrSee the response schema for details and descriptions.
Whether to include validation status in the results. When set to true, various validation results are returned.
The following values are returned at the document level (files/documents/...):
validations/final_result_passThe following values are returned at the field level (files/documents/fields/...):
validations/validvalidations/alertsThe following values are returned at the packet level (also known as case level) (case_info/fields/...):
validations/validvalidations/failuresCross-class validation ensures data quality and consistency across documents within a packet.
See the response schema for details and descriptions.
Whether to include source information in the results. When set to true, various source details are returned.
The following values are returned at the document level (files/documents/...):
post_processed_paths
post_processed_pdf_path
A post_processed_pdf_path is populated when settings/runtime_config/generate_post_process_pdf=true. Paths to PDFs are generated from each document, with separate PDF paths for documents split during classification.
page_layouts
The following values are returned at the field level (files/documents/fields/...):
source_coordinates/top_xsource_coordinates/top_ysource_coordinates/bottom_xsource_coordinates/bottom_ysource_coordinates/page_numberSee the response schema for details and descriptions.
Run results retrieved successfully.
If errors occur at the class, field, or document levels, the response status code is 200 and the response body includes error details.