Jobs

Get job status (lightweight)

Changed on

Minimal status projection — cheaper to poll than the full job view.

get/jobs/{id}/status

Request

  • Base URL: https://api.varg.ai/v2
  • URL: https://api.varg.ai/v2/jobs/{id}/status
  • Auth: HTTP bearer

Path parameters

idstring required

Response

Status

idstring
status'queued' | 'running' | 'awaiting_confirmation' | 'completed' | 'failed' | 'cancelled'

The status only moves forward: queued → running → completed, failed or cancelled. Everything a running job goes through — sending to the provider, uploading references, switching to another provider — is a stage of running; a job never goes back to queued. (Older API builds also reported submitting; treat it as running.)

awaiting_confirmation (multi-step pipelines only): the job finished a step that asks for review and waits for POST /jobs/{id}/confirm. It is not terminal.

stage'queued' | 'submitting' | 'uploading_references' | 'rendering' | 'retrying' | 'finalizing' | 'null' nullable

What the job is doing right now. null once the job is terminal, and while the job is awaiting_confirmation.

  • queued — waiting for a slot; no attempt yet
  • submitting — being sent to the provider
  • uploading_references — the provider is taking the reference files into its asset library (progress_message shows n/m)
  • rendering — the provider accepted the task and is generating
  • retrying — an attempt failed (the provider refused, failed or rate limited it); the job waits for its next attempt, usually on another provider. See attempts.
  • finalizing — the result is being saved and billed
provider_statusstring nullable
progress_messagestring nullable
progressnumber nullable

Numeric fraction 0..1 for a progress bar

errorstring nullable

Human-readable failure message. null unless the job failed or was cancelled.

Example response

{
  "progress_message": "uploading references to ByteDance (1/2)"
}

Changes