Get File
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
ID for the file. It will always start with "file_".
Example: "file_Xj8mK2pL9nR4vT7qY5wZ"
Headers
API version to use for the request. If you’re using an SDK, you can ignore this parameter. If you are not using an SDK and do not specify a version, you will either receive a 400 Bad Request or be set to a previous legacy version. See API Versioning for more details.
Query parameters
Deprecated: Use POST /parse_runs instead to parse file contents.
If set to true, the raw text content of the file will be included in the response.
Deprecated: Use POST /parse_runs instead to parse file contents.
If set to true, the markdown content of the file will be included in the response.
Only available for files with a type of PDF, IMG, or DOCX files that were auto-converted to PDFs.
Deprecated: Use POST /parse_runs instead to parse file contents.
If set to true, the html content of the file will be included in the response.
Only available for files with a type of DOCX.
Response
The type of object. Will always be "file".
ID for the file.
Example: "file_xK9mLPqRtN3vS8wF5hB2cQ"
The name of the file
Example: "Invoices.pdf"
The type of the file.
Availability: Present when the file type could be determined.
A presigned URL to download the file. Expires after 15 minutes.
Availability: Present on GET /files/{id}. Not present on POST /files/upload or when the file is embedded in other resources (e.g., in run responses).
ID of the parent file.
Availability: Present for files created via a Splitter in a workflow.
The time (in UTC) at which the object was created. Will follow the RFC 3339 format.
Example: "2024-03-21T16:45:00Z"
The time (in UTC) at which the object was last updated. Will follow the RFC 3339 format.
Example: "2024-03-21T16:45:00Z"

