Skip to main content
POST
Suno Music Generation
Suno is an action-based model: one model: "suno", and the action field decides what this call does. Start a song from scratch with generate, then keep going — extend it, cover it, restyle it, split the stems, export WAV, make a music video. 31 actions in all. Async: the request returns a task_id; poll task status until completed, then read the artifacts from result.

Actions

Each action is priced separately; the version (v3.5 – v5.5) does not change the price. Live prices live in the console’s Model Market, and every response carries the actual cost.

Create from scratch

Build on an existing track

All of these take task_id (the task that produced the source track) plus optional audio_index (which track from that result, 1-based).

Vocals and stems

Audio editing

Export and analysis

Quick start

Keep going from there

Once you have a task_id, the later actions chain off it.

Parameters

Common

Creative actions

style and tags are the same thing under two names — an upstream quirk: the base generation endpoint calls it style, every other endpoint calls it tags. Sending the wrong one is not an error; it is silently ignored, and you are left wondering why the style did nothing.

Referencing a source track

Action-specific

Parameters are validated per action — sending stem_type to generate is rejected outright rather than ignored. That is deliberate: a parameter that does not belong usually means the wrong action was chosen, and failing early beats failing quietly.

A typical workflow

How one song usually runs from idea to delivery:
  1. generate the song → keep the task_id
  2. Not happy? cover it in another style, or extend it longer
  3. Happy? Run remaster over it
  4. Need an instrumental? stems the lead_vocal and use the rest, or stems_all to split everything
  5. wav for lossless, generate_video for the MV, aligned_lyrics for timestamped words
Every step produces its own task_id, so you can keep chaining.