Paginated List Responses
Endpoints that return multiple items use a paginated wrapper:File-Collection Results
The shape returned byGET /v2/workflows/{workflow_id}/files/{collection_id}/results/ once processing completes (HTTP 200). While processing is still in progress the endpoint returns 412 Precondition Failed — see Error Handling for the polling pattern.
Top-level fields
The keys
parse and extraction are always present — they are explicitly null when the corresponding node didn’t produce results. New code should read extractions[] instead; extraction is retained for back-compat but will be removed.
parse object
See Parse-Only Workflow for an example of the markdown structure.
extraction object — ExtractedField shape
The extraction object is keyed by field name. Each value is an ExtractedField:
evidence entries
Reading results — recommended pattern
Run Response
POST /v2/workflows/{wid}/run/ returns this shape on 202 Accepted:
status is the initial run state — the run was accepted and enqueued, not that extraction is complete. Poll the results endpoint or wait for the webhook before reading results.
The id field is the collection_id — pass it as {collection_id} to the results endpoint. Keep this consistent in your client code.
Error Responses
All error responses share a single shape:Identifier Format
All UUIDs in the API are hyphenated UUIDv7 (RFC 4122 form:8-4-4-4-12):
