parse_id
field. You can query the status and results of the parse operation
with the Get Parse Result endpoint.
Using a file
When submitting a parse job, you can provide the content of the file in one of three ways:file_id
: The ID of a file that has been previously uploaded to the Upload Files. This is the most common method.file_url
: A publicly accessible URL that points to the file you want to parse. The API will download the file from this URL. Redirects are also supported, but the URL and theLocation
header must point to a file that is publicly accessible.raw_text
: Raw text content, if you want to perform structured extraction from non-file sources; such as emails, HTML, CSV, XML, etc.
mime_type
field to override the inferred mime-type. This is useful if you know the content type of the file and want to ensure the model interprets it correctly.
Page classification
You can classify pages of a document into categories, or tags. Pass in an array of categories along with their descriptions to guide the classifier in thepage_classifications
field. The API will return the page class for each page of the document.
Structured extraction
For structured extraction, you can provide one or more schemas to guide the extraction process. The schema must be in the form of a JSON Schema object. The JSON Schema object can be provided in thestructured_extraction_options
array, which can contain multiple objects.
Known limitations include:
- The schema can only be at most 5 levels deep
- All fields must be required
- Root level fields must be objects
Authorizations
Bearer authentication header of the form Bearer <token>
, where <token>
is your auth token.
Body
- file_id
- file_url
- raw_text
File source - must be exactly one of: file_id, file_url, or raw_text
ID of the file previously uploaded to Tensorlake. Has tensorlake- (V1) or file_ (V2) prefix.
"file_abc123xyz"
The properties of this object define the configuration for the document parsing process.
Tensorlake provides sane defaults that work well for most documents, so this object is not required. However, every document is different, and you may want to customize the parsing process to better suit your needs.
The properties of this object define the configuration for structured data extraction.
If this object is present, the API will perform structured data extraction on the document.
The properties of this object define the configuration for page classify.
If this object is present, the API will perform page classify on the document.
The properties of this object help to extend the output of the document parsing process with additional information.
This includes summarization of tables and figures, which can help to provide a more comprehensive understanding of the document.
This object is not required, and the API will use default settings if it is not present.
Additional metadata to identify the parse request. The labels are returned in the parse response.
{ "priority": "high", "source": "email" }
Comma-separated list of page numbers or ranges to parse (e.g., '1,2,3-5'). Default: all pages.
"1-5,8,10"
Name of the file. Only populated when using file_id.
"document.pdf"
application/pdf
, application/vnd.openxmlformats-officedocument.wordprocessingml.document
, application/msword
, application/vnd.openxmlformats-officedocument.presentationml.presentation
, application/vnd.apple.keynote
, image/jpeg
, text/plain
, text/html
, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
, application/vnd.ms-excel.sheet.macroenabled.12
, application/vnd.ms-excel
, text/xml
, text/csv
, image/png
, application/octet-stream
Response
Created parse job details
The unique identifier for the parse job
This is the ID that can be used to track the status of the parse job.
Used in the GET /documents/v2/parse/{parse_id}
endpoint to retrieve
the status and results of the parse job.
The creation date and time of the parse job.
The date is in RFC 3339 format.