/api/extend_audio with its parent clip, producing one continuous audio file.
Typical workflow
- Generate a base clip with
/api/generateor/api/custom_generate. - Extend the clip one or more times with
/api/extend_audio, noting theidof each new clip. - Call
/api/concatwith the final extension clip’s ID to stitch all segments together into a single song.
Concatenation is handled by Suno’s backend. The returned object represents the fully assembled song; its
audio_url points to the merged file.Request body
The ID of the extension clip to concatenate. Suno traces the clip’s lineage and merges it with all parent segments automatically.
Response
A singleAudioInfo object representing the fully concatenated song — not an array.
Unique identifier for the concatenated audio clip.
Title of the concatenated song.
URL of the cover art image.
Full lyrics of the concatenated song.
URL of the complete merged audio file.
URL of the complete merged video file.
ISO 8601 timestamp of when the concatenated clip was created.
The model used to generate the original clip.
GPT description prompt from the original generation.
The lyrics prompt from the clip metadata.
Status of the concatenated clip:
submitted, queued, streaming, complete, or error.Internal clip type as reported by Suno.
Style tags associated with the clip.
Negative style tags associated with the clip.
Total duration of the concatenated audio in seconds.
Error description when
status is error.Error responses
| Status | Meaning |
|---|---|
400 | clip_id is missing |
402 | Out of Suno credits — payment required |
500 | Internal server error |
503 | Network error connecting to Suno |
