Application Process
To use the API, you need to first apply for the corresponding service on the Fish Voices Generation API page. After entering the page, click the “Acquire” button, as shown in the image below:
If you are not logged in or registered, you will be automatically redirected to the login page inviting you to register and log in. After logging in or registering, you will be automatically returned to the current page.
Upon your first application, there will be a free quota available for you to use the API for free.
Basic Usage
First, understand the basic usage method, which is to input the audio link of the voicevoice_url, and you can obtain the processed result. The specific content is as follows:

accept: the format of the response you want to receive, filled in asapplication/json, which means JSON format.authorization: the key to call the API, which can be selected directly after application.
voice_url: the uploaded audio link of the voice.title: the title information of the voice.image_urls: the cover image of the voice.description: the description information of the voice.callback_url: the URL to receive the callback result.

success, the status of the voice creation task at this time.data, the result of the music task_id, the ID of the voice generation task at this time, which will be used for cloning the voice in the future.title, the title of the voice.image_url, the cover information of the voice.description, the description information of the voice.train_mode, the mode used for the voice generation task at this time.tags, the style of the voice.default_text, the voice text information of the voice generation task at this time.
data’s _id in the result.
Additionally, if you want to generate the corresponding integration code, you can directly copy the generated code, for example, the CURL code is as follows:
Asynchronous Callback
Since the time taken by the Fish Voices Generation API to generate is relatively long, approximately 1-2 minutes, if the API does not respond for a long time, the HTTP request will keep the connection open, leading to additional system resource consumption. Therefore, this API also provides support for asynchronous callbacks. The overall process is: when the client initiates a request, an additionalcallback_url field is specified. After the client initiates the API request, the API will immediately return a result containing a task_id field, representing the current task ID. When the task is completed, the result of the generation task will be sent to the client-specified callback_url in the form of a POST JSON, which also includes the task_id field, allowing the task result to be associated by ID.
Let’s understand how to operate specifically through an example.
First, the Webhook callback is a service that can receive HTTP requests, and developers should replace it with the URL of their own HTTP server. For demonstration purposes, we will use a public Webhook sample site https://webhook.site/, where you can open the site to get a Webhook URL, as shown in the image below:
Copy this URL, and it can be used as a Webhook. The sample here is https://webhook.site/4815f79f-a40f-4078-ac85-1cc126b6bb34.
Next, we can set the callback_url field to the above Webhook URL, while filling in the corresponding parameters, as shown in the image below:

https://webhook.site/4815f79f-a40f-4078-ac85-1cc126b6bb34, as shown in the image:
The content is as follows:
task_id field in the result, and other fields are similar to the above text. This field can be used to associate tasks.
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.

