Get Parse Run
Retrieve the status and results of a parse run.
Use this endpoint to get results for a parse run that has already completed, or to check on the status of a parse run initiated by the Create Parse Run endpoint.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
The unique identifier for the parse run.
Example: "pr_xK9mLPqRtN3vS8wF5hB2cQ"
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
Response
The type of object. Will always be "parse_run".
A unique identifier for the parse run.
Example: "pr_xK9mLPqRtN3vS8wF5hB2cQ"
The file that was parsed. This file can be used as a parameter for other Extend endpoints, such as POST /workflow_runs.
A human-readable description of the failure.
Availability: Present when status is "FAILED".
The parse run output.
Availability: Present when status is "PROCESSED" and the request was made without the responseType=url query parameter. Contains the parsed chunks.
A presigned URL to download the parse run output as a JSON file. The object shape is the same as the output field. Expires after 15 minutes.
Availability: Present when status is "PROCESSED" and the request was made with responseType=url query parameter.
Metrics about the parsing process.
Availability: Present when status is "PROCESSED".
Usage credits consumed by this run.
Availability: Present when status is "PROCESSED", the run was created after October 7, 2025, and the customer is on the current billing system.

