---
title: "Get job status"
method: GET
path: "/v2/{endpoint}/{id}"
tags: ["asyncVideoGeneration"]
---

# Get job status

`GET /v2/{endpoint}/{id}`

Poll the status of an async generation job. Status transitions through `pending` → `processing` → `completed` or `failed`. When completed, the `result` object contains output URLs (see each endpoint's documentation for the available keys). Poll every 5 seconds and stop when the status reaches `completed` or `failed`. Status and output URLs are available for 24 hours after the job reaches a terminal state. After expiry this endpoint returns `404`.

## Path parameters

- `id` string, required
- `endpoint` 'text-to-video' | 'image-to-video' | 'audio-to-video' | 'retake' | 'extend' | 'video-to-video-hdr' | 'video-to-video-reframe', required

## Headers

- `Authorization` string, required

## Response `200`

Current job status

- union — Job status response. The shape depends on the current status: - `pending` — job is queued - `processing` — generation in progress - `completed` — done, `result` contains output URLs (keys depend on the endpoint) - `failed` — error occurred, `error` contains details
  - object — pending variant
    - `status` 'pending', required
    - `id` string, required
    - `created_at` string, date-time, required
  - object — processing variant
    - `status` 'processing', required
    - `id` string, required
    - `created_at` string, date-time, required
  - object — completed variant
    - `status` 'completed', required
    - `id` string, required
    - `created_at` string, date-time, required
    - `completed_at` string, date-time, required — ISO 8601 timestamp of when the job completed.
    - `result` V2JobResult, required — Result object for a completed job. Contains output URLs — the available keys depend on the endpoint. Available for 24 hours after completion.
  - object — failed variant
    - `status` 'failed', required
    - `id` string, required
    - `created_at` string, date-time, required
    - `completed_at` string, date-time, required — ISO 8601 timestamp of when the job failed.
    - `error` V2JobError, required — Error details for a failed job. Uses the same error types as HTTP error responses (`api_error`, `content_filtered_error`, `insufficient_funds_error`, etc.).
      - `type` string, required — Error type for programmatic handling. Same values as HTTP error types.
      - `message` string, required — Human-readable error description.

## Other responses

- `401` — Authentication failed
- `404` — Resource not found
- `500` — An unexpected error occurred

---

[API](https://skmtc.net/ltx/apis/api-reference.md) · [All operations](https://skmtc.net/ltx/apis/api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/ltx/api-reference/versions/4cce82513832/schema)