Skip to main content
GET
Use status and processing_status together to distinguish execution completion from document success. For per-node progress, use the get job details endpoint.

Path parameters

string
required
The unique identifier of the job.

Response

string
required
Unique identifier for the job.
string
required
Unique identifier of the workflow that created this job.
string
required
Name of the workflow that created this job.
string
required
Job lifecycle state. One of: SCHEDULED, IN_PROGRESS, COMPLETED, STOPPED, FAILED, REJECTED. COMPLETED means job execution finished. Check processing_status for the document outcome.
string
required
ISO 8601 timestamp when the job was created.
string
ISO 8601 duration of the job run.
array
IDs of input files for this job.
array
Output file metadata objects. Each object includes node_id, file_id, node_type, and node_subtype.
string
Job type. Default: ephemeral.
boolean
true means someone requested a stop for the job. false means no one has requested a stop.
string
Identifier of the user who created the job, when available.
string
Sanitized failure reason for a failed job, when available.
string
Document processing outcome. Use this with status to distinguish execution completion from document success.
integer
Number of documents recorded as failed. A zero on an unfinished job is not a final result.
string
Reason a completed job delivered no documents, if detected: NO_DOCUMENTS_DISCOVERED or NO_DOCUMENTS_SUCCEEDED.