Skip to main content

Overview

Suno generates complete music tracks from a text description or structured lyrics. Use this page when you are ready to call the API after trying Suno in the APIXO playground.

Endpoint and authentication

Base URL:
All requests require your APIXO API key:
Submit requests also require:

Copy-paste async quickstart

This minimal request submits a simple text-to-music task and returns a taskId.
Successful response:
Save the taskId; you need it to poll for the final result.

Poll for result

Processing response:
Success response:
Failed response:
Parse resultJson after state becomes success:
Suno resultJson contains resultUrls as an array of objects. Each item can include audio_url for the generated MP3 and image_url for the cover image. Do not parse it as a plain string URL array.

Request body

Simple mode

Use customMode: false when you want Suno to create the song from a short description.

Custom lyrics mode

Use customMode: true when you want to provide lyrics, style, and title.

Instrumental mode

Set instrumental: true when you want music without vocals.

Parameters

string
default:"async"
Result delivery mode. Use async for polling with statusTask, or callback for webhook delivery.
string
Required when request_type is callback. Must be a public HTTPS URL that can receive task payloads. See Webhooks.
object
required
Suno input parameters.

Response format

Submit task response

POST /generateTask/suno returns a task ID when the task is accepted:
integer
API status code. 200 means the task was accepted.
string
Human-readable status message.
string
Unique task identifier used with the status endpoint.

Status response fields

string
Unique task identifier.
string
Current task state: pending, processing, success, or failed.
string
JSON string containing generated track objects. Present when state is success.
string
Lyrics or prompt text returned by the upstream result. Present only when available.
string
Machine-readable failure code. Present when state is failed.
string
Human-readable failure message. Present when state is failed.
integer
Task creation timestamp in Unix milliseconds.
integer
Task completion timestamp in Unix milliseconds. Present after completion.
integer
Processing duration in milliseconds. Present after completion when available.
Parsed resultJson structure:

Webhook callback mode

Use callback mode when your backend should receive task payloads automatically instead of polling.
Only parse resultJson when the callback payload has state: "success". See Webhooks for delivery requirements and retry behavior.

Billing

Suno is billed per generation request. The current public APIXO catalog lists Suno at $0.12 / use. For current pricing, see Pricing.

Latency and polling

Actual latency may vary by prompt complexity, selected mode, provider queue, and current load.
For production workloads, use callback mode to reduce polling traffic. Result URLs are stored for 15 days by default; account-level storage settings may change the retention period.
If you receive 429, slow down requests and retry with backoff. For account-level details, see System APIs.

Errors and troubleshooting

HTTP errors

Task failure fields

When a task reaches state: "failed", inspect failCode and failMsg in the status response. See Error Codes for the full error reference.