List Parse Runs
List a company’s parse runs, newest-first and paginated. Use this to poll the outcome of a parse you kicked with Trigger Parse.
A run record is one logical parse run — the extract stage and the
create_<flow>_v<N> parse stage of a single trigger, reported together:
runIdis the logical run’s stable id.flowis the flow the run implements (submissionorpolicy).targetis the{ kind, id }file or folder the run parsed.statusis the overall run status, collapsed to one ofrunning,succeeded, orfailed(every internalfailed_*retry state reads asfailed; a run that will still be retried reportsfailedhere — checkstagesforretryingdetail. A run holding for a precondition reads asrunning, because it has not failed).stagesbreaks the run into itsextractandparsestages, each with its ownstatus(including the distinctretrying, the not-yet-startedpending, andwaiting— holding for a precondition, not a failure),attempts, optionalerror, andfinishedAt.createdEntitieslists the entities the run created (entityType+entityId); an entity deleted after the run reportsdeleted: true.extractionReadysays whether the run’s merged extraction artifact was persisted.erroris present only on a run that recorded a failure message.
Runs that predate run grouping are reported as legacy records
(legacy: true): one record per pipeline task, target: null, no
stages/createdEntities.
Pagination uses the standard 1-based page / pageSize query params.
Required permission: company.file:read
Authorizations
API key authentication. Send your raw API key as the Authorization header value with NO scheme prefix — Authorization: YOUR-API-KEY. Do NOT prefix it with Bearer or ApiKey, and do not use an X-API-Key header; those are not accepted.
Path Parameters
Company identifier
Query Parameters
1-based page number. Defaults to the first page.
x >= 1Number of runs per page. Defaults to the API page size.
x >= 1