Skip to main content
POST
/
api
/
v1
/
client
/
job
/
CreateTask
Suno music cover from uploaded audio
curl --request POST \
  --url https://api.crun.ai/api/v1/client/job/CreateTask \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '
{
  "model": "suno/music-cover",
  "callback_url": "https://your-domain.com/api/callback",
  "input": {
    "audio_url": "https://example.com/uploaded-audio.mp3",
    "mode": "custom",
    "model": "v5",
    "instrumental": false,
    "title": "Midnight Addiction (Cover)",
    "tags": "Western R&B, female vocal, dark, sensual",
    "lyrics": "[Verse 1]\nI still taste your words in the dark...",
    "vocal_gender": "f",
    "style_weight": 0.85,
    "audio_weight": 0.6,
    "weirdness_constraint": 0.2,
    "negative_tags": "metal, aggressive"
  }
}
'
{
  "code": 200,
  "message": "success",
  "data": {
    "task_id": "task_12345678"
  }
}

​
Important Notes

  • Requires an audio_url pointing to the uploaded audio file
  • For existing music, suno may fail to upload.
  • Supports two modes: simple and custom
  • In simple mode, prompt is required
  • In custom mode, title and tags are required, and lyrics is required if instrumental=false
If you want a quick cover based on the uploaded audio, start with mode=simple.

​
Music Cover (Simple Mode)

Create a cover from the uploaded music using a short prompt. 
{
    "model": "suno/music-cover",
    "callback_url": "",
    "input": {
        "audio_url": "https://example.com/uploaded-audio.mp3",
        "mode": "simple",
        "model": "v5",
        "instrumental": false,
        "prompt": "Create a cover with a softer, more intimate vocal delivery."
    }
}

​
Music Cover (Custom Mode)

Custom cover lets you control style and lyrics. Provide title, tags, and lyrics (unless instrumental). 
{
    "model": "suno/music-cover",
    "callback_url": "",
    "input": {
        "audio_url": "https://example.com/uploaded-audio.mp3",
        "mode": "custom",
        "model": "v5",
        "instrumental": false,
        "title": "Midnight Addiction (Cover)",
        "tags": "Western R&B, female vocal, dark, sensual",
        "lyrics": "[Verse 1]\nI still taste your words in the dark...",
        "vocal_gender": "f",
        "style_weight": 0.85,
        "audio_weight": 0.6,
        "weirdness_constraint": 0.2,
        "negative_tags": "metal, aggressive"
    }
}

​
Get Task Result

After submitting a task, use the unified query endpoint to check progress and retrieve results:

Get Suno Task Info

Learn how to query suno task status and retrieve generation results

Authorizations

​
x-api-key
string
header
required

All APIs require authentication via API Key.

Get API Key:

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

Usage: Add to request header:

x-api-key: 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

Body

application/json
​
model
enum<string>
required

The model name to use for generation. Required field.

  • Must be suno/music-cover for this endpoint
Available options:
suno/music-cover
​
input
object
required

Input parameters for music cover based on an uploaded audio file.

Rules:

  • audio_url is required and must point to the uploaded audio file.
  • mode=simple: prompt is required.
  • mode=custom: title and tags are required.
  • mode=custom and instrumental=false: lyrics is required.
  • model=v4: tags max length is 200 and lyrics max length is 3000.
​
callback_url
string<uri>

Optional. Callback URL for receiving task completion notifications.

  • System will POST task status and results to this URL when generation completes
  • Callback payloads structure is consistent with the data object returned by the task status query
  • Your callback endpoint should accept POST requests with JSON payload containing results
  • It returns an HTTP 200 status code upon successful receipt
Example:

"https://your-domain.com/api/callback"

Response

Request successful

​
code
enum<integer>

Response status code

  • 200: Success - Request has been processed successfully
  • 401: Unauthorized - Authentication credentials are missing or invalid
  • 402: Insufficient Credits - Account does not have enough credits to perform the operation
  • 404: Not Found - The requested resource or endpoint does not exist
  • 422: Validation Error - The request parameters failed validation checks
  • 429: Rate Limited - Request limit has been exceeded for this resource
  • 455: Service Unavailable - System is currently undergoing maintenance
  • 500: Server Error - An unexpected error occurred while processing the request
  • 501: Generation Failed - Content generation task failed
  • 505: Feature Disabled - The requested feature is currently disabled
Available options:
200,
401,
402,
404,
422,
429,
455,
500,
501,
505
​
message
string

Response message, error description when failed

Example:

"success"

​
data
object