Extract File (Sync)
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
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.
Request
Reference to an existing extractor. One of extractor or config must be provided.
Inline extract configuration. One of extractor or config must be provided.
Response
The type of object. Will always be "extract_run".
The unique identifier for this extract run.
Example: "exr_Xj8mK2pL9nR4vT7qY5wZ"
The extractor that was used for this run.
Availability: Present when an extractor reference was provided. Not present when using inline config.
The version of the extractor that was used for this run.
Availability: Present when an extractor reference was provided. Not present when using inline config.
The initial output from the extract run, before any review edits.
Availability: Present when reviewed is true.
The output after human review.
Availability: Present when reviewed is true.
A detailed message about the failure.
Availability: Present when status is "FAILED".
Any metadata that was provided when creating the extract run.
Availability: Present when metadata was provided during creation.
Details of edits made during review.
Availability: Present when edited is true.
The ID of the parse run that was used for this extract run.
Availability: Present when a parse run was created.
Usage credits consumed by this run.
Availability: Present when status is "PROCESSED".
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"

