GET
Get a file upload processing steps for that uploadId
Request · Response · Guide: Upload files
Use status to know when processing is done: poll until it is processed (every document is done and its values are ready), action_required or failed. statuses lists the individual processing steps for progress display only — it does not include extraction and is not a completion signal. A document blueprintId may change until status is processed.

Authorizations

x-api-key
string
header
required

API key for authentication

Path Parameters

uploadId
string
required

Response

Get a file upload processing steps for that uploadId

status
enum<string>

Overall progress of the upload. uploading: the file bytes have not arrived yet. processing: still working, including extraction. processed: every document is done and its values are ready. action_required: processing stopped and needs review. failed: processing failed. For a ZIP, combines the status of every extracted file.

Available options:
uploading,
processing,
processed,
action_required,
failed
aiProcessingProvider
string

The engine that actually processed the file: "capybara" or "orchestrator" (Beethoven). Read-only, and not an echo of the requested ocrModel — a Capybara request can still be served by Beethoven when the ingest contract is not met. Absent until the file has been stamped.

statuses
object[]

Processing step events as they were reported; a step can appear more than once (for example waiting, then completed). For progress display only; use status to know when processing is done.

files
object[]

For regular uploads: document objects (a document blueprintId may change until status is processed). For ZIP uploads: per-file status objects with uploadId, fileName, status, statuses, and files (documents).