Additional data about structure of the document that references text content nodes by their UIDs

Non-empty list of UIDs of content nodes corresponding to the annotation.

Type of an annotation, (e.g. table structure / row header, etc.).

Text that corresponds to the content node (optional)

Identifier for a content node that is unique across all nodes in a document

Kensho Extract allows users to quickly transform their unstructured documents into a machine-readable format that identifies titles, subtitles, paragraphs, tables, and footers detected within the document in their natural reading order. 
Kensho Extract interprets messy page layout, structuring text into cohesive paragraphs that can be effectively analyzed and searched. The Kensho Extract API V3 has incorporated changes to how users must call the API.
Please note there are more required fields in API V3 than API V2. The following fields are *mandatory* for `/v3/extractions`: file, document_type, ocr and enhanced_table_extraction. API V3 introduces new upload and download functionality, allowing the upload of the original document and retrieval of the extracted document output via pre-signed URLs. The pre-signed URLs expire after 15 minutes. These new endpoints must be called in the following order.
 - `/v3/extractions/upload-url`
 - followed by POST'ing the document to the `url` provided in the response
 - `/v3/extractions/upload-complete`
 - `/v3/extractions/download-url/{request_id}`
 - followed by a calling the GET `output_url` provided in the response

Kensho Extract API

This can be any combination of the required parameters are not provided, a parameter that is invalid, or if a specific pages is requested in the `pages` parameter and that page is not in the document. E.g., requesting page 57 for a 10 page document.

The authentication token is missing or invalid.

GET the `output_url` in the response to download the extracted document.

request_id

The request_id was not provided by the client, or output_format was not specified when the request was created.

The request is on a different API version than the POST request that created the request, the document has not been uploaded, or /v3/extractions/upload-complete has not been called to marked the upload complete.

Retrieve the extracted document's download URL

Call this after the document has been uploaded to the pre-signed URL returned by `/v3/extractions/upload-url`. The extraction process will not begin until this endpoint is called.

The request was marked as uploaded successfully.

The request_id was not provided by the client, or was not created via `/v3/extractions/upload-url`.

The request_id or the uploaded document could not be found.

Mark the upload as complete to start extraction

Creates the request and returns a pre-signed upload URL to upload the document for extraction.

This can be any combination of the required parameters are not provided or parameter value is invalid.

Upload URL to submit a document for extraction.

This can be `structured_document`, `structured_document_with_locations`, or `structured_document_with_char_offsets`. It determines if the response format will include location bounding box information.

output_format

The request_id was not provided by the client, or output_format was specified when the request was created.
 
If output_format was specified when the request was created, /v3/extractions/download-url/{request_id} must be called to get a pre-signed URL to retrieve the extracted output.

The request is on a different API version than the POST request that created the request.

**This is not an Extract API endpoint**. This section outlines the response details for the pre-signed `output_url` obtained from the `/v3/extractions/download-url/{request_id}` endpoint.
 
Refer to the AWS pre-signed URL documentation for detailed information on specific response codes and their meanings.