API Reference

Legacy Suno music

Legacy Suno music; requires a configured legacy Suno channel.

POST https://api.tu-zi.com/suno/submit/music
Preview guide

Paste into an AI assistant to help with integration. Documentation and examples only; no real credentials.

Preview guide

Legacy Suno music

Updated · Reviewed

Endpoint and authentication

POST https://api.tu-zi.com/suno/submit/music

Transport: json

Use an inference API key. Examples contain placeholders; read credentials from environment variables.

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Before calling

  • Examples use this site's address. For another gateway, replace only the site address and keep the full endpoint path.
  • Replace resource placeholders YOUR_PROVIDER_VERSION: obtain task/request IDs from the same account's real responses and use provider versions/buttons documented by the linked protocol. Do not send placeholders.
  • Use an inference key created on this site's token page. Set the API_KEY environment variable or replace YOUR_API_KEY, as shown in the selected example.

Constraints

Protocol differences

  • Legacy submission data is a string; v2 data is an object with task_id.
  • Changing only the URL is insufficient.

Channels and parameters

  • Verify action, mv version, clip IDs and channel capabilities.
  • The table describes DTO fields, not universal provider support.
  • Prefer matching /suno/v2 actions when a v2 channel is available; legacy clip IDs are not automatically v2 public asset IDs.

Clips and accounts

task_id and continue_clip_id are forwarded unchanged without automatic source-channel/account binding; follow-ups require a compatible channel that owns the clip.

Minimal request example

{
  "gpt_description_prompt": "A calm piano melody",
  "mv": "YOUR_PROVIDER_VERSION",
  "make_instrumental": true
}

Confirming success

Check HTTP status, the business status in the body and the required result fields. Do not rely only on HTTP 200 or the script exit code.

  1. Legacy Suno first requires code=success.
  2. Submission data is a task ID string; after retrieval reaches data.status=SUCCESS inspect media in data.data. Stop on FAILURE.

Body parameters

FieldTypeRequiredDescription / constraints
modelstringNoOptional model routing override; defaults to the action model.
promptstringNoLyrics or prompt; required for the lyrics action.
gpt_description_promptstringNoDescription-mode prompt where supported.
mvstringNoProvider-confirmed version identifier; required on some channels. Do not infer from a model name.
titlestringNoSong title.
tagsstringNoStyle tags.
make_instrumentalbooleanNoInstrumental flag; explicit false is preserved.
task_idstringNoProvider-defined task identifier, forwarded unchanged. Gateway task IDs are not translated to upstream IDs and do not bind the source channel.
continue_clip_idstringNoClip ID from source results; different from a task ID.
continue_atnumberNoContinuation time in seconds; explicit zero is preserved.
cover_clip_idstringNoSource cover clip ID where supported.
generation_typestringNoProvider-specific generation mode, not portable across channels.
negative_tagsstringNoNegative style tags.
taskstringNoProvider-specific task mode.
continued_aligned_promptstringNoAligned continuation prompt.
infill_start_snumberNoInfill start in seconds where supported.
infill_end_snumberNoInfill end in seconds where supported.

Response fields

FieldTypeDescription / constraints
codestringsuccess on acceptance.
datastringPublic gateway task ID; unlike v2 data.task_id.

Illustrative response; some endpoints show essential fields only. Optional fields may be absent.

{
  "code": "success",
  "data": "task_example"
}

Asynchronous workflow

  1. Persist the data string task ID and GET /suno/fetch/{task_id} with the same credential.
  2. Stop at data.status SUCCESS / FAILURE and read songs, lyrics or assets from data.data.
  3. Check task records after creation timeouts before resubmitting.

Errors and retries

Check HTTP status and protocol-specific errors; do not mix error formats across protocols.

  • 401/403: check credentials and permissions.
  • 429: classify temporary throttling, exhausted quota, or service capacity failure; only transient failures merit bounded backoff.
  • 5xx: inspect the gateway, upstream, and model/channel configuration.

Error bodies may contain error/message/code depending on the protocol.

  • Use bounded exponential backoff for reads encountering transient errors; fix parameter, authentication, quota, or configuration failures first.
  • Do not blindly retry task creation, generation, or key mutations, to avoid duplicate billing or execution.