Skip to main content
GET
Get job status (lightweight)

Authorizations

Authorization
string
header
required

varg API key (varg_...). Get one at app.varg.ai or run bunx vargai login. App sessions may alternatively send a Supabase JWT.

Path Parameters

id
string
required
Pattern: ^job_

Response

Status

id
string
status
enum<string>

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.

Available options:
queued,
running,
awaiting_confirmation,
completed,
failed,
cancelled
stage
enum<string> | null

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
Available options:
queued,
submitting,
uploading_references,
rendering,
retrying,
finalizing,
null
provider_status
string | null
progress_message
string | null
Example:

"uploading references to ByteDance (1/2)"

progress
number | null

Numeric fraction 0..1 for a progress bar

error
string | null

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