Compared with its predecessor, Suno V4 officially emphasizes clearer audio, lyric expression, and more dynamic song structures, making it suitable for organizing complete creations around verses, choruses, and transitions. The platform invocation ID is chirp-v4. You can start from a theme description or custom lyrics, and manage selections through work audio and status. Capabilities such as Remaster and Covers in the official product should be distinguished according to the corresponding operations on this platform.
Submit requests to the public API at api.acedata.cloud using the documented parameters, then use the results in your application.
Input parameters and result formats vary by service. Use the public API for this model and follow its guide for generation, task retrieval and editing operations.
Clarify capacity, inputs and outputs, and invocation methods before selecting a model.
The figures above are this platform's V4 usage specifications. Creation parameters and finished output should be distinguished according to the corresponding model and operation.
Learn what chirp-v4 can bring to your work.
V4's official upgrade directions include audio clarity and dynamic song structures. Describing the restraint of the verse, the expansion of the chorus, and the resolution of the outro makes auditioning and revision easier than simply listing genre names; these directions still need to be verified through actual works.
Custom mode is suitable for projects that already have verses, choruses, or campaign copy. Set custom=true, submit lyric, title, and style, and express lyric content separately from the musical direction. V4's style space is relatively compact, so prioritize the core genre, main instruments, and mood, and avoid using lengthy descriptions that consume input space.
Generation results center on the audio URL, while also carrying the song ID, title, lyrics, status, and actual duration, making it easier for applications to build auditioning and archiving workflows. When backend processing is needed, use async=true to obtain task_id, or configure callback_url to receive results, separating music tasks from frontend interactions.
Start with specific tasks to find where the model can be effective.
Enter the event theme, audience, and the emotion you want to convey, then use Inspiration Mode to create a draft for listening; if you have a specific slogan or chorus, switch to custom lyrics. Deliver the audio and corresponding text for the planning team to discuss the musical direction. Brand names, key slogans, and sung content should be confirmed item by item after listening.
Organize written lyrics into sections such as verses and choruses, add a brief style description, and generate a sung version for discussion. This is suitable for checking the sense of rhythm, section length, and emotional progression after words are set to music. The finished piece can serve as a reference for revising lyrics, rather than treating the returned lyrics field as a word-for-word transcription of the audio.
Describe musical moods such as upbeat, soothing, or tense around the video imagery, select instrumental music, and create candidate tracks for rough-cut listening. Save the audio and its actual duration, then match it to visual cues in editing software. This is suitable for exploring music directions, but precise cueing, fixed durations, and final editing still need to be completed in post-production.
Choose based on task complexity, input materials, and expected results.
If your existing application already organizes inputs around chirp-v4's lyric and style limits, or if the task mainly involves short songs and music drafts, you can continue choosing V4. Compared with V3.5's 120-second tier, V4's 150-second tier provides more length; this difference is for planning content length, does not mean every generation reaches the limit, and is not a comparison of audio quality or speed.
When lyrics exceed 3000 characters, style descriptions need more space, or male and female vocal preference control is needed, chirp-v4-5 is more suitable. V4.5 has lyric and style limits of 5000 and 1000 characters respectively, with a duration tier of 4 minutes. Do not simply add new-version parameters to V4 as a substitute for switching models; fields in a shared interface do not mean that every version produces the same results.
Prepare the inputs first, then connect them to the appropriate application workflow.
Prepare lyrics containing verses, choruses, and transition sections, and choose a familiar musical direction.
Explicitly select chirp-v4. Use prompt for theme creation; for custom creation, organize lyric, style, and title according to this model's limits. Save task_id, obtain audio_url after waiting for the completed result, and archive it together with the work ID and creation settings.
Design tasks directly based on the following inputs and acceptance criteria.
Explicitly specify chirp-v4 and describe the dynamic changes of the sections, for example, “restrained verse, expanded chorus, smoothly resolved ending.”
Listen for section transitions, vocal clarity, and the ending, then compare with the previous version using the same lyrics; improvement in the official version does not mean every work achieves the same result.
Before formal use, understand the output quality and capability scope.
Answers to common questions about using chirp-v4.
Submit model=chirp-v4, action=generate, and custom=false to POST /suno/audios, describe the theme and musical direction in prompt, and keep it under 500 characters. If you want to create an instrumental track without vocals, set instrumental=true, then retrieve the completed audio result.
Use custom=true, put the lyrics in lyric, the title in title, and the musical direction in style. V4 has limits of 3000, 80, and 200 characters for these three fields respectively. It is recommended to distinguish lyric content from style instructions and keep clear sections, making it easier to listen to and revise each section after generation.
You cannot treat the desired duration as an exact guarantee. The platform lists a maximum V4 duration of 150 seconds, but actual works may be shorter. Custom generation (custom=true, action=generate) can submit duration as a desired duration hint, but it may be ignored and does not guarantee the target length. Read duration in the result and listen to it; deliveries requiring a fixed number of seconds can be trimmed after generation.
Do not rely on vocal_gender to achieve this control on V4; this parameter applies starting from V4.5. If male or female vocal preference is an important selection criterion, choose chirp-v4-5 or an applicable later model; even on supported models, it is preference guidance rather than a guarantee of strict compliance.
After setting async=true, first save the returned task_id, then query the task to obtain its status and result; you can also configure callback_url to receive completion notifications. Once the song is complete, read audio_url, id, and duration from data, download the audio, and save the metadata for later listening and archiving.
Choose a development approach or application suited to this model and follow its setup guide.
↗Python SDK Integration Guide
SDK installation, authentication and examples↗TypeScript SDK Integration Guide
SDK installation, authentication and examples
↗
↗
↗This is only a basic call example. See the full docs for more parameters and advanced usage.
View Docs