Skip to main content
GET
/
api
/
v1
/
wav
/
record-info
Get WAV Conversion Details
curl --request GET \
  --url https://api.kie.ai/api/v1/wav/record-info \
  --header 'Authorization: Bearer <token>'
{
  "code": 200,
  "msg": "success",
  "data": {
    "taskId": "988e****c8d3",
    "musicId": "e231****-****-****-****-****8cadc7dc",
    "callbackUrl": "https://api.example.com/callback",
    "musicIndex": "0",
    "completeTime": "2025-01-01 00:10:00",
    "response": {
      "audioWavUrl": "https://example.com/s/04e6****e727.wav"
    },
    "successFlag": "PENDING-待执行 SUCCESS-成功 CREATE_TASK_FAILED-创建任务失败 GENERATE_AUDIO_FAILED-生成wav失败",
    "createTime": "2025-01-01 00:00:00",
    "errorCode": null,
    "errorMessage": null
  }
}

​
Usage Guide

  • Use this endpoint to check the status of a WAV conversion task
  • Access the WAV file URL once conversion is complete
  • Track conversion progress and any errors that may have occurred

​
Status Descriptions

  • PENDING: Task is waiting to be processed
  • SUCCESS: WAV conversion completed successfully
  • CREATE_TASK_FAILED: Failed to create the conversion task
  • GENERATE_WAV_FAILED: Failed during WAV file generation
  • CALLBACK_EXCEPTION: Error occurred during callback

​
Developer Notes

  • The WAV file URL is only available in the response when status is SUCCESS
  • Error codes and messages are provided for failed tasks
  • WAV files are retained for 14 days after successful conversion

Authorizations

​
Authorization
string
header
required

All APIs require authentication via Bearer Token.

Get API Key:

  1. Visit API Key Management Page to get your API Key

Usage: Add to request header: Authorization: Bearer YOUR_API_KEY

Note:

  • Keep your API Key secure and do not share it with others
  • If you suspect your API Key has been compromised, reset it immediately in the management page

Query Parameters

​
taskId
string
required

Unique identifier of the WAV conversion task to retrieve. This is the taskId returned when creating the WAV conversion task.

Response

Request successful

​
code
enum<integer>

Response status code

  • 200: Success - Request has been processed successfully
  • 401: Unauthorized - Authentication credentials are missing or invalid
  • 404: Not Found - The requested resource or endpoint does not exist
  • 422: Validation Error - The request parameters failed validation checks
  • 451: Failed to fetch the image. Kindly verify any access limits set by you or your service provider.
  • 455: Service Unavailable - System is currently undergoing maintenance
  • 500: Server Error - An unexpected error occurred while processing the request
Available options:
200,
401,
404,
422,
451,
455,
500
​
msg
string

Error message when code != 200

Example:

"success"

​
data
object
⌘I