Skip to main content
GET
/
volc
/
v3
/
contents
/
generations
/
tasks
/
{id}
Query a ByteDance video task
curl --request GET \
  --url https://api.cometapi.com/volc/v3/contents/generations/tasks/{id} \
  --header 'Authorization: Bearer <token>'
{
  "id": "021773297205999example",
  "model": "doubao-seedance-1-5-pro-251215",
  "status": "succeeded",
  "content": {
    "video_url": "https://example.com/generated.mp4"
  },
  "created_at": 1773297205,
  "updated_at": 1773297260,
  "resolution": "720p",
  "duration": 5,
  "ratio": "16:9",
  "framespersecond": 24
}
Use this endpoint after you create a ByteDance Jimeng task. It does not start a render. It only reports the current task state and, when the job finishes, the generated video URL and output metadata.

​
Watch these fields

  • status for the current provider state
  • content.video_url when the render is done
  • resolution, duration, ratio, and framespersecond if your application needs output metadata

​
Polling loop

1

Create a task first

Start with ByteDance Video Generation.
2

Poll by task id

Keep calling this endpoint until the status reaches a terminal state.
3

Persist the result

When content.video_url appears, copy the result to your own storage if you need long retention.

​
Result URLs

The ByteDance workflow is still create first, then query by task id. CometAPI keeps that structure and normalizes authentication. Treat the returned video URL as a delivery URL, not permanent storage.

Authorizations

​
Authorization
string
header
required

Bearer token authentication. Use your CometAPI key.

Path Parameters

​
id
string
required

Task id returned by the create endpoint.

Response

200 - application/json

Current task state.

​
id
string
required
​
model
string
required
​
status
string
required

Provider task status.

​
created_at
integer
required
​
updated_at
integer
required
​
content
object
​
usage
object
​
seed
integer
​
resolution
string
​
duration
integer
​
ratio
string
​
framespersecond
integer