Skip to main content
The main function of the Suno Tasks API is to query the execution status of a task by entering the task ID generated by the Suno Audios Generation API or Suno Lyrics Generation API. This document will introduce the integration instructions for the Suno Tasks API in detail, helping you easily integrate and fully leverage the powerful features of this API. Through the Suno Tasks API, you can easily query the task execution status of the Suno Lyrics Generation API or Suno Audios Generation API.

​
Application Process

To use the Suno Audios Generation API, first go to the Ace Data Cloud Console to obtain your API Token and keep it for later use. If you have not yet logged in or registered, you will be automatically redirected to the login page to be invited to register and log in. After completion, you will automatically return to the current page. One API Token can call all platform services, without needing to apply separately for each service. Your first application will be given free credits for a free trial; when credits are insufficient, you can recharge your general balance in the Console.
📘 Full documentation: Suno Audios Generation API →

​
Request Example

The Suno Tasks API can be used to query the results of both the Suno Audios Generation API and the Suno Lyrics Generation API. For how to use the Suno Audios Generation API, please refer to the documentation Suno Audios Generation API . For how to use the Suno Lyrics Generation API, please refer to Suno Lyrics Generation API . We take one task ID returned by the Suno Audios Generation API service as an example to demonstrate how to use this API. Suppose we have a task ID: eae26f89-b64b-404d-a80c-761996660b1c, next we demonstrate how to by passing in a task ID.

​
Task Example Image

​
Set Request Headers and Request Body

Request Headers include:
  • accept: Specifies that the response result is received in JSON format. Enter application/json here.
  • authorization: The key for calling the API, which can be directly selected from the dropdown after application.
Request Body includes:
  • id: The uploaded task ID.
  • action: The method of operation on the task.
Set as shown in the figure below:

​
Code Example

It can be seen that code in various languages has already been automatically generated on the right side of the page, as shown in the figure:

Some code examples are as follows:

​
CURL

​
Python

​
Response Example

After the request succeeds, the API will return detailed information about the song task here. For example:
The returned result contains multiple fields. The request field is the request body when initiating the task, while the response field is the response body returned after the task is completed. The fields are described as follows.
  • id, the ID of the task that generates this song, used to uniquely identify this song generation task.
  • request, the request information in the song task query.
  • response, the response information in the song task query.
  • created_at, task creation time, Unix timestamp (seconds, floating point).
  • started_at, task execution start time, Unix timestamp (seconds, floating point).
  • finished_at, task completion time, Unix timestamp (seconds, floating point). This field is not returned when the task is not completed.
  • elapsed, task execution duration, in seconds (floating point, rounded to 3 decimal places). This field is not returned when the task is not completed.

​
Batch Query Operation

This is for querying song task details for multiple task IDs. Unlike above, you need to select the action as retrieve_batch Request Body includes:
  • ids: Array of uploaded task IDs.
  • action: The operation method for the task.
Set it as shown in the figure below:

​
Code Example

You can find that code in various languages has already been automatically generated on the right side of the page, as shown in the figure:

Some code examples are as follows:

​
Response Example

After the request succeeds, the API will return detailed information for all batch song tasks this time. For example:
The returned result contains multiple fields, among which items contains the specific detailed information of batch song tasks. The specific information of each song task is the same as the fields above, and the field information is as follows.
  • items, all specific detailed information of batch song tasks. It is an array, and each element of the array has the same format as the return result for querying a single task above.
  • count, the number of song tasks queried in batch here.

​
CURL

​
Python

​
Error Handling

When calling the API, if an error is encountered, the API will return the corresponding error code and information. 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

​
Conclusion

Through this document, you have learned how to use the Suno Tasks API to query all specific detailed information of single or batch song 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.