Skip to main content
GET
/
runwayml
/
v1
/
tasks
/
{id}
Poll a Runway official-format task
curl --request GET \
  --url https://api.cometapi.com/runwayml/v1/tasks/{id} \
  --header 'Authorization: Bearer <token>'
{
  "code": "success",
  "message": "",
  "data": {
    "task_id": "3d957031-9a2a-45e2-9dc7-bc8513059c50",
    "action": "IMAGE_TO_VIDEO",
    "status": "QUEUED",
    "fail_reason": "",
    "submit_time": 1773366766,
    "start_time": 0,
    "finish_time": 0,
    "progress": "0%",
    "data": {
      "id": "3d957031-9a2a-45e2-9dc7-bc8513059c50",
      "status": "PENDING",
      "createdAt": "2026-03-13T09:52:46+08:00"
    }
  }
}
Use this endpoint to inspect a Runway task by id through the official-format wrapper.

​
Check these fields first

  • Outer code and message for wrapper-level status
  • data.status and data.progress for the current task state
  • Nested data.data for provider-specific task metadata

​
When to use it

  • After calling an official-format Runway task creation page such as text-to-image, image-to-video, video-to-video, or upscale
  • When you need the unified wrapper response instead of the reverse-format feed route

​
Retry behavior

  • A freshly created task may briefly return task_not_exist
  • Wait a few seconds and retry before treating the task id as invalid
  • Once the task is visible, this route and the reverse feed wrapper can return the same queued or in-progress envelope
Live validation on 2026-03-13 returned a wrapped response with code: success, status: QUEUED, and a nested data object rather than a bare Runway task object.

Authorizations

​
Authorization
string
header
required

Bearer token authentication. Use your CometAPI key.

Headers

​
X-Runway-Version
string

Optional Runway version header, for example 2024-11-06.

Path Parameters

​
id
string
required

Runway task id returned by the create endpoint.

Response

200 - application/json

Current wrapper task state or not-yet-visible error.

​
code
string | null
required
​
message
string
required
​
data
object