request and response are omitted).
GET /v1/jobs/{job_id}/status. It avoids request/response restoration work and returns only lifecycle metadata.client.jobs.retrieve(job_id) defaults to lightweight polling.client.jobs.retrieve_full(job_id) fetches full request/response payloads.client.jobs.retrieve(jobId) defaults to lightweight polling.client.jobs.retrieveFull(jobId) fetches full request/response payloads."job".validating - Request is being validatedqueued - Waiting in the processing queuein_progress - Currently being processedcompleted - Successfully finishedfailed - Execution failedcancelled - Cancelled by userexpired - Job data has expiredinclude_request=false.status is completed. Contains:status is failed. Contains:include_request=true restores any request-side file artifacts that were offloaded during job creation.
include_response=true restores response payloads or document artifacts for completed jobs.
If restoration fails for a specific artifact, the job is still returned and Retab may attach a warning describing the degraded restore.
wait_for_completion/waitForCompletion polls with lightweight retrieves and returns a final job with include_response=true and include_request=false. Override these with options when needed.Whether to restore request MIME documents from GCS in the response.
Whether to restore response payload/documents from GCS in the response.
Successful Response
Core Job object following OpenAI-style specification.
Represents a single asynchronous job that can be polled for status and result retrieval.
/v1/documents/extract, /v1/documents/parse, /v1/documents/split, /v1/documents/classify, /v1/schemas/generate, /v1/edit/agent/fill, /v1/edit/templates/fill, /v1/edit/templates/generate, /v1/evals/extract/process, /v1/evals/split/process, /v1/evals/classify/process, /v1/evals/extract/extract, /v1/evals/extract/split "job"validating, queued, in_progress, completed, failed, cancelled, expired Error details when job fails.
Response stored when job completes successfully.