Integration and Use of Veo Tasks API
The main function of the Veo Tasks API is to query the execution status of a task by inputting the task ID generated by the Veo Videos Generation API.
This document will provide detailed integration instructions for the Veo Tasks API, helping you easily integrate and fully utilize the powerful features of this API. With the Veo Tasks API, you can easily query the execution status of tasks from the Veo Videos Generation API.
¶ Application Process
To use the Veo Videos Generation API, first obtain your API Token from the YuJun Console for future reference.

If you are not logged in or registered, you will be automatically redirected to the login page to invite you to register and log in, and will return to the current page upon completion.
One API Token can call all services on the platform without needing to apply separately for each service. The first application will grant a free quota for a trial experience; when the quota is insufficient, you can recharge the general balance in the console.
📘 Complete Documentation: Veo Videos Generation API →
¶ Request Example
The Veo Tasks API can be used to query the results of the Veo Videos Generation API. For information on how to use the Veo Videos Generation API, please refer to the documentation Veo Videos Generation API.
We will demonstrate how to use this API with an example task ID returned by the Veo Videos Generation API. Suppose we have a task ID: 1ebe4f2b-59ba-4385-a4ea-0ce8a3fe12ed, we will demonstrate how to pass in a task ID.
¶ Task Example Image

¶ Setting Request Headers and Request Body
Request Headers include:
accept: Specifies that the response result should be in JSON format, set toapplication/json.authorization: The key to call the API, which can be selected directly after application.
Request Body includes:
id: The uploaded task ID.action: The operation method for the task.
Set as shown in the image below:

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

Some code examples are as follows:
¶ CURL
curl -X POST 'https://api.acedata.cloud/veo/tasks' \
-H 'accept: application/json' \
-H 'authorization: Bearer {token}' \
-H 'content-type: application/json' \
-d '{
"id": "1ebe4f2b-59ba-4385-a4ea-0ce8a3fe12ed",
"action": "retrieve"
}'
¶ Python
import requests
url = "https://api.acedata.cloud/veo/tasks"
headers = {
"accept": "application/json",
"authorization": "Bearer {token}",
"content-type": "application/json"
}
payload = {
"id": "1ebe4f2b-59ba-4385-a4ea-0ce8a3fe12ed",
"action": "retrieve"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)
¶ Response Example
Upon successful request, the API will return the details of the video task here. For example:
{
"_id": "68834c16550a4144a5112589",
"id": "1ebe4f2b-59ba-4385-a4ea-0ce8a3fe12ed",
"api_id": "52a0fa83-3c78-4793-b45a-c1a5c869ae46",
"application_id": "b7341df0-3a87-40ef-8f3c-a7dda97816a2",
"created_at": 1753435158.509,
"started_at": 1753435158.569,
"finished_at": 1753435250.969,
"elapsed": 92.4,
"credential_id": "1f64eaaa-eff0-4f18-bfc2-8c5b1e7949ae",
"request": {
"callback_url": "https://webhook.site/aed5cd28-f8aa-4dca-9480-8ec9b42137dc",
"action": "text2video",
"model": "veo2-fast",
"prompt": "White ceramic coffee mug on glossy marble countertop with morning window light. Camera slowly rotates 360 degrees around the mug, pausing briefly at the handle."
},
"trace_id": "d1d53c04-58c5-4c40-bb63-f00188540e56",
"type": "videos",
"user_id": "ad7afe47-cea9-4cda-980f-2ad8810e51cf",
"response": {
"success": true,
"task_id": "1ebe4f2b-59ba-4385-a4ea-0ce8a3fe12ed",
"trace_id": "d1d53c04-58c5-4c40-bb63-f00188540e56",
"data": [
{
"id": "2f43ceed37944b4d836e1a1899dad0a1",
"video_url": "https://platform.cdn.acedata.cloud/veo/1ebe4f2b-59ba-4385-a4ea-0ce8a3fe12ed.mp4",
"created_at": "2025-07-25 17:19:20",
"complete_at": "2025-07-25 17:21:45",
"state": "succeeded"
}
]
}
}
The returned result contains multiple fields, with the request field being the request body when the task was initiated, and the response field being the response body returned after the task is completed. The field descriptions are as follows.
id: The ID of the video task generated, used to uniquely identify this video generation task.request: The request information in the video task.response: The return information in the video task.created_at: The task creation time, Unix timestamp (seconds, float).started_at: The task execution start time, Unix timestamp (seconds, float).finished_at: The task completion time, Unix timestamp (seconds, float). This field is not returned if the task is not completed.elapsed: The time taken for task execution, in seconds (float, rounded to 3 decimal places). This field is not returned if the task is not completed.
¶ Batch Query Operation
This is for querying the details of multiple task IDs, and unlike the above, the action needs to be selected as retrieve_batch.
Request Body includes:
ids: An array of uploaded task IDs.action: The operation method for the task.
Set as shown in the image below:

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

Some code examples are as follows:
¶ Response Example
Upon successful request, the API will return the specific details of all batch video tasks this time. For example:
{
"items": [
{
"_id": "68834c16550a4144a5112589",
"id": "1ebe4f2b-59ba-4385-a4ea-0ce8a3fe12ed",
"api_id": "52a0fa83-3c78-4793-b45a-c1a5c869ae46",
"application_id": "b7341df0-3a87-40ef-8f3c-a7dda97816a2",
"created_at": 1753435158.509,
"started_at": 1753435158.569,
"finished_at": 1753435250.969,
"elapsed": 92.4,
"credential_id": "1f64eaaa-eff0-4f18-bfc2-8c5b1e7949ae",
"request": {
"callback_url": "https://webhook.site/aed5cd28-f8aa-4dca-9480-8ec9b42137dc",
"action": "text2video",
"model": "veo2-fast",
"prompt": "White ceramic coffee mug on glossy marble countertop with morning window light. Camera slowly rotates 360 degrees around the mug, pausing briefly at the handle."
},
"trace_id": "d1d53c04-58c5-4c40-bb63-f00188540e56",
"type": "videos",
"user_id": "ad7afe47-cea9-4cda-980f-2ad8810e51cf",
"response": {
"success": true,
"task_id": "1ebe4f2b-59ba-4385-a4ea-0ce8a3fe12ed",
"trace_id": "d1d53c04-58c5-4c40-bb63-f00188540e56",
"data": [
{
"id": "2f43ceed37944b4d836e1a1899dad0a1",
"video_url": "https://platform.cdn.acedata.cloud/veo/1ebe4f2b-59ba-4385-a4ea-0ce8a3fe12ed.mp4",
"created_at": "2025-07-25 17:19:20",
"complete_at": "2025-07-25 17:21:45",
"state": "succeeded"
}
]
}
},
{
"_id": "68834c16550a4144a5112589",
"id": "1ebe4f2b-59ba-4385-a4ea-0ce8a3fe12ed",
"api_id": "52a0fa83-3c78-4793-b45a-c1a5c869ae46",
"application_id": "b7341df0-3a87-40ef-8f3c-a7dda97816a2",
"created_at": 1753435158.509,
"started_at": 1753435158.569,
"finished_at": 1753435250.969,
"elapsed": 92.4,
"credential_id": "1f64eaaa-eff0-4f18-bfc2-8c5b1e7949ae",
"request": {
"callback_url": "https://webhook.site/aed5cd28-f8aa-4dca-9480-8ec9b42137dc",
"action": "text2video",
"model": "veo2-fast",
"prompt": "White ceramic coffee mug on glossy marble countertop with morning window light. Camera slowly rotates 360 degrees around the mug, pausing briefly at the handle."
},
"trace_id": "d1d53c04-58c5-4c40-bb63-f00188540e56",
"type": "videos",
"user_id": "ad7afe47-cea9-4cda-980f-2ad8810e51cf",
"response": {
"success": true,
"task_id": "1ebe4f2b-59ba-4385-a4ea-0ce8a3fe12ed",
"trace_id": "d1d53c04-58c5-4c40-bb63-f00188540e56",
"data": [
{
"id": "2f43ceed37944b4d836e1a1899dad0a1",
"video_url": "https://platform.cdn.acedata.cloud/veo/1ebe4f2b-59ba-4385-a4ea-0ce8a3fe12ed.mp4",
"created_at": "2025-07-25 17:19:20",
"complete_at": "2025-07-25 17:21:45",
"state": "succeeded"
}
]
}
}
],
"count": 2
}
The returned result contains multiple fields, among which items includes the specific details of batch video tasks, and the specific information of each video task is the same as the fields in the previous single task query result.
items, all specific detail information of batch video tasks. It is an array, and each element of the array has the same format as the previous single task return result.count, the number of video tasks in this batch query.
¶ CURL
curl -X POST 'https://api.acedata.cloud/veo/tasks' \
-H 'accept: application/json' \
-H 'authorization: Bearer {token}' \
-H 'content-type: application/json' \
-d '{
"ids": ["1ebe4f2b-59ba-4385-a4ea-0ce8a3fe12ed","1ebe4f2b-59ba-4385-a4ea-0ce8a3fe12ed"],
"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 Veo Tasks API to query all specific detail information of single or batch video 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.