API Reference
Suno Lyric Writing
Suno Lyric Writing: suno/lyrics.
Preview guide
Paste into an AI assistant to help with integration. Documentation and examples only; no real credentials.
Updated · Reviewed
Endpoint and authentication
POST https://api.tu-zi.com/suno/v2/lyrics
Transport: json
Use an inference API key. Examples contain placeholders; read credentials from environment variables.
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
Minimal request example
{
"prompt": "[Verse 1]\n雨打在铁皮屋顶上"
}
Before running
Replace https://api.tu-zi.com with this site origin (do not append /v1 twice), and YOUR_MODEL with the exact marketplace model ID. Install requests for Python; use Node.js 20+ and save JavaScript as .mjs. WebSocket samples list their own dependencies.
Create an inference key on the site and set API_KEY in the environment; replace YOUR_API_KEY in cURL. Prepare local input.png/input.wav files for upload examples.
Start with a minimal request, then read the result using the response fields below. For async APIs, a returned task ID requires polling; acceptance does not mean generation has finished.
Constraints
Model suno/lyrics is selected by the action route, so the body does not need model. Resource IDs must belong to this account and be created through the gateway; do not use upstream internal IDs.
Body parameters
| Field | Type | Required | Description / constraints |
|---|---|---|---|
| prompt | string | Yes | Full lyrics, up to 5000 characters. Use markers like [Verse] and [Chorus] to shape the structure. Example: [Verse 1]<br>雨打在铁皮屋顶上 |
| lyrics_model | string | No | Which lyric writing approach to use. Form initial value (not an upstream default): "classic" Values: "classic", "remi" |
Response fields
| Field | Type | Description / constraints |
|---|---|---|
| code | string | Submission result code. |
| data.task_id | string | Public gateway task ID. |
Illustrative response; some endpoints show essential fields only. Optional fields may be absent.
{
"code": "success",
"data": {
"task_id": "task_example"
}
}
Asynchronous workflow
Save the public task ID and GET /suno/v2/fetch/{task_id} with the same key. Handle gateway states; SUCCESS and FAILURE are terminal. Read music, lyrics, download links or resource IDs according to the action.
Errors and retries
Check HTTP status and protocol-specific errors; do not mix error formats across protocols. For 401/403 check credentials and permissions, for 429 back off, and for 5xx check gateway/upstream status. Error bodies may contain error/message/code depending on the protocol.
Use bounded exponential backoff for reads. Do not blindly retry task creation, generation, or key mutations, to avoid duplicate billing or execution.
兔子API