Application Process
To use the Fish Audios Generation API, first obtain your API Token from the Ace Data Cloud Console for future use.
If you are not logged in or registered, you will be automatically redirected to the login page inviting you 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 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: Fish Audios Generation API →
Request Example
The Fish Tasks API can be used to query the results of the Fish Audios Generation API. For information on how to use the Fish Audios Generation API, please refer to the documentation Fish Videos Generation API. We will take a task ID returned by the Fish Audios Generation API as an example to demonstrate how to use this API. Suppose we have a task ID: 2725a2d3-f87e-4905-9c53-9988d5a7b2f5, and 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, filled in asapplication/json.authorization: The key to call the API, which can be selected directly after application.
id: The uploaded task ID.action: The operation method for the task.

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:
CURL
Response Example
After a successful request, the API will return the detailed information of the task here. For example:id: The ID that generated this task, used to uniquely identify this generation task.request: The request information in the task query.response: The return information in the task query.created_at: The task creation time, Unix timestamp (seconds, float).started_at: The task start execution 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 task details for multiple task IDs, and unlike the above, the action needs to be selected as retrieve_batch. Request Body includes:ids: The uploaded array of task IDs.action: The operation method for the task.

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:
Response Example
After a successful request, the API will return the specific details of all batch tasks this time. For example:items includes the specific details of batch tasks, and each task’s specific information is the same as the fields mentioned above.
items, all specific details of the batch tasks. It is an array, and each element of the array has the same format as the return result of querying a single task above.count, the number of tasks in this batch query.
CURL
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.

