System will call this callback when WAV format audio generation is complete. When you submit a WAV format conversion task to the Suno API, you can use the callBackUrl parameter to set a callback URL. The system will automatically push the results to your specified address when the task is completed. Callback Mechanism Overview# The callback mechanism eliminates the need to poll the API for task status. The system will proactively push task completion results to your server.
To ensure the authenticity and integrity of callback requests, we strongly recommend implementing webhook signature verification. See our Webhook Verification Guide for detailed implementation steps. Callback Timing# The system will send callback notifications in the following situations: WAV format conversion task completed successfully
WAV format conversion task failed
Errors occurred during task processing
Callback Method# Content Type : application/json
Timeout Setting : 15 seconds
When the task is completed, the system will send a POST request to your callBackUrl in the following format: {
"code" : 200 ,
"msg" : "success" ,
"data" : {
"audioWavUrl" : "https://example.com/s/04e6****e727.wav" ,
"task_id" : "988e****c8d3"
}
} Status Code Description# code (integer, required)# Callback status code indicating task processing result: Status Code Description 200 Success - Request has been processed successfully 500 Internal Error - Please try again later
msg (string, required)# Status message providing detailed status description data.task_id (string, required)# Task ID, consistent with the task_id returned when you submitted the task data.audioWavUrl (string)# WAV format audio file URL, returned on success with accessible download link Callback Reception Examples# Here are example codes for receiving callbacks in popular programming languages: Best Practices# Callback URL Configuration Recommendations
1.
Use HTTPS : Ensure your callback URL uses HTTPS protocol for secure data transmission
2.
Verify Source : Verify the legitimacy of the request source in callback processing
3.
Idempotent Processing : The same task_id may receive multiple callbacks, ensure processing logic is idempotent
4.
Quick Response : Callback processing should return a 200 status code as quickly as possible to avoid timeout
5.
Asynchronous Processing : Complex business logic should be processed asynchronously to avoid blocking callback response
6.
File Processing : WAV file download and processing should be done in asynchronous tasks to avoid blocking callback response
Callback URL must be a publicly accessible address
Server must respond within 15 seconds, otherwise it will be considered a timeout
If 3 consecutive retries fail, the system will stop sending callbacks
Please ensure the stability of callback processing logic to avoid callback failures due to exceptions
WAV file URLs may have time limits, recommend downloading and saving promptly
Troubleshooting# If you do not receive callback notifications, please check the following: Network Connection Issues Confirm that the callback URL is accessible from the public network
Check firewall settings to ensure inbound requests are not blocked
Verify that domain name resolution is correct
Server Response Issues Ensure the server returns HTTP 200 status code within 15 seconds
Check server logs for error messages
Verify that the interface path and HTTP method are correct
Content Format Issues Confirm that the received POST request body is in JSON format
Check that Content-Type is application/json
Verify that JSON parsing is correct
File Processing Issues Confirm that the WAV file URL is accessible
Check file download permissions and network connections
Verify file save paths and permissions
Alternative Solution# If you cannot use the callback mechanism, you can also use polling:
Poll Query Results
Use the get WAV details endpoint to regularly query task status. We recommend querying every 30 seconds. 