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

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. <br><br> 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*: file, document_type, ocr and enhanced_table_extraction.


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.

request_id

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

output_format

The request_id was not provided by the client.

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