Parse Document
Parse runs a file through the same parsing and chunking Captain uses for indexing and returns the chunks without storing them in a collection. The output is meant to be taken into another database or pipeline and managed there.
Accepts PDF, DOCX and DOC files. Send the file as input: a direct download link, or the captain:// id from Upload File for a local file. Parsing runs as a job: this request returns 202 with a job_id, and the chunks come back from Get Parse Job once the job completes. Pages are billed at the indexing rates for the chosen processing_type. A failed or cancelled job is not billed.
Headers
Request
The file to parse, as one of:
- A direct download link: a public HTTPS URL, or a presigned URL from S3, Google Cloud Storage, Azure Blob Storage or any other store.
- A
captain://id returned by Upload File, for a file sent from local disk.
For a link, Captain copies the file into its own storage right after accepting the job, so the link only needs to work for a few seconds. A link that cannot be read, a file over 100 MB, or a file type the endpoint does not accept ends the job as failed with download_failed, file_too_large or unsupported_file_type, and nothing is billed.
advanced extracts tables, figures and charts and bills advanced pages. basic extracts text and layout and bills basic pages. auto inspects the file and uses advanced when it has photos, drawings, tables or scanned pages (logos and signatures do not count), otherwise basic, and bills the tier it used. Same meaning and rates as indexing.