Integration and Usage of SeeDance Tasks API

The main function of the SeeDance Tasks API is to query the execution status of a task by inputting the task ID generated by the SeeDance Video Generation API.

This document will provide detailed instructions on integrating the SeeDance Tasks API, helping you easily integrate and fully utilize the powerful features of this API. With the SeeDance Tasks API, you can easily query the execution status of tasks from the SeeDance Video Generation API.

Application Process

To use the SeeDance Video Generation API, first obtain your API Token from the 辰汐ai Console for backup.

If you are not logged in or registered, you will be automatically redirected to the login page to register and log in, and after completion, you will be automatically returned to the current page.

One API Token can call all services on the platform, no need to apply separately for each service. The first application grants free quota for trial; when the quota is insufficient, you can recharge the general balance in the Console.

📘 Full documentation: SeeDance Video Generation API →

Request Example

The SeeDance Tasks API can be used to query the results of the SeeDance Video Generation API. For how to use the SeeDance Video Generation API, please refer to the document SeeDance Video Generation API.

We take a task ID returned by the SeeDance Video Generation API service as an example to demonstrate how to use this API. Suppose we have a task ID: 20068983-0cc9-4c6a-aeb6-9c6a3c668be0, next we demonstrate how to pass in a task ID.

Task Example Image

Setting Request Headers and Body

Request Headers include:

  • accept: specifies receiving the response in JSON format, here set to application/json.
  • authorization: the API key for calling the API, which can be selected directly after application.

Request Body includes:

  • id: the uploaded task ID.
  • action: the operation mode for the task.

Set as shown in the figure below:

Code Example

You can see that various language codes have been automatically generated on the right side of the page, as shown:

Partial code example as follows:

CURL

curl -X POST 'https://api.acedata.cloud/seedance/tasks' \
-H 'accept: application/json' \
-H 'authorization: Bearer {token}' \
-H 'content-type: application/json' \
-d '{
  "id": "a6e0d456-189b-4c78-9232-2fe72166ab39",
  "action": "retrieve"
}'

Response Example

After a successful request, the API will return detailed information about the task here. For example:

{
    "_id": "69480c5cff2676299c7b351d",
    "id": "9462ca25-468b-45a5-9e75-6f516dedcc80",
    "api_id": "44e45d2b-8754-4a93-b793-c63271335f6f",
    "application_id": "1456a4bf-e2f4-4247-9b2d-fb49effc6eca",
    "created_at": 1766329436.091,
    "started_at": 1766329436.151,
    "finished_at": 1766329518.051,
    "elapsed": 81.9,
    "credential_id": "3e20b461-f750-48d3-a1f7-3aea48d15d77",
    "request": {
        "model": "doubao-seedance-1-0-pro-250528",
        "content": [
            {
                "type": "text",
                "text": "Multiple shots. A detective enters a dimly lit room. He inspects clues on the table, picking up an item from the table. The camera shifts to him thinking. --ratio 16:9"
            }
        ],
        "callback_url": "dummy"
    },
    "trace_id": "24b1b09c-5649-4290-98db-eab23e5efcac",
    "type": "videos",
    "user_id": "ad7afe47-cea9-4cda-980f-2ad8810e51cf",
    "response": {
        "success": true,
        "task_id": "9462ca25-468b-45a5-9e75-6f516dedcc80",
        "trace_id": "24b1b09c-5649-4290-98db-eab23e5efcac",
        "data": {
            "task_id": "cgt-20251221230356-sxgt7",
            "status": "succeeded",
            "video_url": "https://platform.cdn.acedata.cloud/seedance/d1c2e49e-d854-4a2e-b0c0-88e520f82e2e.mp4",
            "last_frame_url": null,
            "model": "doubao-seedance-1-0-pro-250528"
        }
    }
}

The returned result contains multiple fields. The request field is the request body when initiating the task, and the response field is the response body returned after the task is completed. Field descriptions are as follows.

  • id: the ID of the generated task, used to uniquely identify this generation task.
  • request: the request information in the queried task.
  • response: the return information in the queried task.
  • created_at: task creation time, Unix timestamp (seconds, float).
  • started_at: task start execution time, Unix timestamp (seconds, float).
  • finished_at: task completion time, Unix timestamp (seconds, float). This field is not returned if the task is not completed.
  • elapsed: task execution duration, in seconds (float, 3 decimal places). This field is not returned if the task is not completed.

Batch Query Operation

This is for querying task details for multiple task IDs. Unlike above, the action needs to be selected as retrieve_batch.

Request Body includes:

  • ids: array of uploaded task IDs.
  • action: the operation mode for the task.

Set as shown in the figure below:

Code Example

You can see that various language codes have been automatically generated on the right side of the page, as shown:

Partial code example as follows:

Response Example

After a successful request, the API will return detailed information for all batch tasks this time. For example:

{
    "items": [
        {
            "_id": "69480c5cff2676299c7b351d",
            "id": "9462ca25-468b-45a5-9e75-6f516dedcc80",
            "api_id": "44e45d2b-8754-4a93-b793-c63271335f6f",
            "application_id": "1456a4bf-e2f4-4247-9b2d-fb49effc6eca",
            "created_at": 1766329436.091,
            "started_at": 1766329436.151,
            "finished_at": 1766329518.051,
            "elapsed": 81.9,
            "credential_id": "3e20b461-f750-48d3-a1f7-3aea48d15d77",
            "request": {
                "model": "doubao-seedance-1-0-pro-250528",
                "content": [
                    {
                        "type": "text",
                        "text": "Multiple shots. A detective enters a dimly lit room. He examines the clues on the table, picking up an item from the table. The shot turns to him as he is deep in thought. --ratio 16:9"
                    }
                ],
                "callback_url": "dummy"
            },
            "trace_id": "24b1b09c-5649-4290-98db-eab23e5efcac",
            "type": "videos",
            "user_id": "ad7afe47-cea9-4cda-980f-2ad8810e51cf",
            "response": {
                "success": true,
                "task_id": "9462ca25-468b-45a5-9e75-6f516dedcc80",
                "trace_id": "24b1b09c-5649-4290-98db-eab23e5efcac",
                "data": {
                    "task_id": "cgt-20251221230356-sxgt7",
                    "status": "succeeded",
                    "video_url": "https://platform.cdn.acedata.cloud/seedance/d1c2e49e-d854-4a2e-b0c0-88e520f82e2e.mp4",
                    "last_frame_url": null,
                    "model": "doubao-seedance-1-0-pro-250528"
                }
            }
        },
        {
            "_id": "69480e0dff2676299c7cb98b",
            "id": "d9e576bd-ca14-4c6f-a541-f4734e941dbe",
            "api_id": "44e45d2b-8754-4a93-b793-c63271335f6f",
            "application_id": "1456a4bf-e2f4-4247-9b2d-fb49effc6eca",
            "created_at": 1766329436.091,
            "started_at": 1766329436.151,
            "finished_at": 1766329518.051,
            "elapsed": 81.9,
            "credential_id": "3e20b461-f750-48d3-a1f7-3aea48d15d77",
            "request": {
                "model": "doubao-seedance-1-0-pro-250528",
                "content": [
                    {
                        "type": "text",
                        "text": "Multiple shots. A detective enters a dimly lit room. He examines the clues on the table, picking up an item from the table. The shot turns to him as he is deep in thought. --ratio 16:9"
                    }
                ],
                "callback_url": "dummy"
            },
            "trace_id": "e3da01aa-5026-4653-8d07-c68c4fcf466a",
            "type": "videos",
            "user_id": "ad7afe47-cea9-4cda-980f-2ad8810e51cf",
            "response": {
                "success": true,
                "task_id": "d9e576bd-ca14-4c6f-a541-f4734e941dbe",
                "trace_id": "e3da01aa-5026-4653-8d07-c68c4fcf466a",
                "data": {
                    "task_id": "cgt-20251221231109-cnkhp",
                    "status": "succeeded",
                    "video_url": "https://platform.cdn.acedata.cloud/seedance/eb99ba03-178c-4616-8d19-e625fee2e884.mp4",
                    "last_frame_url": null,
                    "model": "doubao-seedance-1-0-pro-250528"
                }
            }
        }
    ],
    "count": 2
}

The return result contains multiple fields, among which items include the specific details of batch tasks, and the specific information of each task is the same as the fields in the previous single task return result.

  • items, all specific detail information of batch tasks. It is an array, and each element of the array has the same format as the previous query single task return result.
  • count, the number of tasks in this batch query.

CURL

curl -X POST 'https://api.acedata.cloud/seedance/tasks' \
-H 'accept: application/json' \
-H 'authorization: Bearer {token}' \
-H 'content-type: application/json' \
-d '{
  "ids": ["9462ca25-468b-45a5-9e75-6f516dedcc80","d9e576bd-ca14-4c6f-a541-f4734e941dbe"],
  "action": "retrieve_batch"
}'

Error Handling

When calling the API, if an error occurs, the API will return the corresponding error code and message. For example:

  • 400 token_mismatched: Bad request, possibly due to missing or invalid parameters.
  • 400 api_not_implemented: Bad request, possibly due to missing or invalid parameters.
  • 401 invalid_token: Unauthorized, invalid or missing authorization token.
  • 429 too_many_requests: Too many requests, you have exceeded the rate limit.
  • 500 api_error: Internal server error, something went wrong on the server.

Error Response Example

{
  "success": false,
  "error": {
    "code": "api_error",
    "message": "fetch failed"
  },
  "trace_id": "2cf86e86-22a4-46e1-ac2f-032c0f2a4e89"
}

Conclusion

Through this document, you have learned how to use the SeeDance Tasks API to query all specific detail information of single or batch tasks. We hope this document can help you better integrate and use this API. If you have any questions, please feel free to contact our technical support team.