Suno V6 API: What Changes in Your Existing Integration

The Suno V6 API on reAPI uses the existing audio endpoint with version: "V6", "V6_MINI" or "V6_WILD". For an older integration, check both the version and the field names: reAPI's Suno surface now uses snake_case, while legacy version values can pass validation and still fail during generation.^[1]

Start with model: "suno-music" and an explicit V6 version. Keep the asynchronous submit-and-poll flow, then save the returned track identifiers for later edits. Update the request builder first, then check how the application reads completed results. Changing the model name to suno-v6 is not the documented way to select V6.

TL;DR

Send V6, V6_MINI or V6_WILD in version; keep suno-music as the song-generation model ID.^[1]
Replace old camelCase fields with documented snake_case names, including custom_mode, negative_tags and audio_id.^[1]
Stop submitting retired V4–V5.5 values. Schema acceptance does not mean the model still generates audio.^[1]
Choose V6 for a defined musical brief, Mini when evaluating faster turnaround, and Wild for exploration. These are selection criteria based on Suno's descriptions, not measured performance guarantees.^[2]
Budget $0.06 for a completed song-generation request, covering two takes. Sound FX has a separate 13-credit charge.^[3]

What changes in your Suno V6 API request

Suno announced V6 on September 9, 2026, with three variants and a transition away from its previous model generation.^[2] For a developer, the immediate distinction is between Suno's product announcement and the fields your integration can actually send.

The announcement describes broader creation and editing features. It does not make every consumer feature available through reAPI's audio request. For example, the current music-generation request documents text controls and the relevant audio workflows; do not add an image or video field just because the consumer announcement mentions those inputs. Build against the full Suno parameter reference.^[1]

The Suno V6 reference gives the current V6 request shape. model identifies the operation; version identifies the music model used for that operation. Keep those decisions separate in your application so that choosing Mini does not accidentally switch from generation to an editing operation.^[4]

This is reAPI access. Suno's own public developer-interest form still describes an exploratory program with selected partners; it does not issue a self-service production key.^[5]

V6, Suno V6 Mini and Suno V6 Wild: which value to send

Choose the variant according to what you need from the next result. Suno describes its flagship as oriented toward precision, Wild toward less predictable exploration, and Mini toward faster, more efficient creation. The following choices are editorial applications of those descriptions.^[2]

API value	Starting point	What to evaluate in your own jobs
`V6`	A clear genre, arrangement or lyrical brief	Whether the result follows the musical direction closely enough
`V6_MINI`	Iteration where turnaround matters	End-to-end waiting time and whether either take meets your quality bar
`V6_WILD`	Exploring arrangements before committing to one	Whether the variation is useful or creates more editing work

Mini is not the cheaper API tier here. The same operation costs the same across all three V6 variants, so a lower-latency result would save waiting time rather than reduce that request's listed fee.^[4] No controlled latency or listening comparison was performed for this article. Treat “faster” as Suno's product positioning until you measure your own workload.

For a fair comparison, keep the prompt, mode and other controls the same, and change only version. Evaluate both returned takes. If you also rewrite the lyrics or change the style, you will not know which change caused the difference.

Record the selected version with each job. The extension reference requires the version to match the source track, so a variant selector for new songs should not silently rewrite the version used by follow-up extension requests.^[1]

Suno V6 vs V5.5: migrate versions and field names together

For an existing integration, Suno V6 vs V5.5 comes down to whether the request can still finish. reAPI documents V4, V4_5, V4_5PLUS, V4_5ALL, V5 and V5_5 as retired. The schema retains those values, but a request using one fails during generation and is refunded.^[1]

That creates two different failure points. An unsupported field can be rejected at submission. An accepted legacy version can instead produce a task that later fails. Checking only the HTTP status of the POST will miss the second case.

Review saved presets and server defaults as well as the visible model picker. An application can display “V6” while a background worker continues submitting an older stored payload.

Old request fragment	Current fragment
`"version": "V5_5"`	`"version": "V6"` for new song generation
`"customMode": false`	`"custom_mode": false`
`"negativeTags": "metal"`	`"negative_tags": "metal"`
`"audioId": "…"`	`"audio_id": "…"` in operations that reference a track

The full Suno reference records the field-name change on September 13, 2026.^[1] Update your request object deliberately; a broad text replacement across stored results and unrelated integrations can change things you did not intend to migrate.

For new jobs, regenerate an accepted V6 source before testing dependent edits. Do not assume selecting V6 will convert every old track identifier into a compatible source for every operation.

The eight operations on the V6 page

The dedicated V6 page covers eight operations. They share POST /api/v1/audio/generations, but their required inputs differ.^[4]

Operation	`model`	`version` rule
Generate a song	`suno-music`	Required
Extend a generated track	`suno-extend`	Required; match source version
Cover uploaded audio	`suno-upload-cover`	Required
Extend uploaded audio	`suno-upload-extend`	Required; follow source-version rule
Add vocals	`suno-add-vocals`	Optional; defaults to `V6`
Add accompaniment	`suno-add-instrumental`	Optional; defaults to `V6`
Mash up uploaded audio	`suno-mashup`	Required
Generate sounds	`suno-sounds`	Required

The whole family contains 18 asynchronous operations. The other ten sit outside this V6 page; that does not mean all ten reject a version field. suno-replace-section accepts either an existing task_id plus audio_id, or an upload_url plus version. The uploaded-audio branch requires the version; the existing-track branch must omit it. Mixing the branches is invalid.^[1]

If your software attaches a global version property to every Suno request, remove that assumption. Keep version selection in the request builders that need it. WAV conversion, lyrics generation and voice operations also have their own input and output contracts; they are not copies of the song request.

Send a first V6 request and wait for audio

You need a reAPI key, enough credits for the chosen operation and a server-side place to keep the credential. For an initial request, inspiration mode keeps the payload small: prompt describes the song, and the model supplies the lyrics.^[4]

curl https://reapi.ai/api/v1/audio/generations \
  -H "Authorization: Bearer $REAPI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "suno-music",
    "version": "V6",
    "custom_mode": false,
    "instrumental": false,
    "prompt": "A dreamy synthwave track about driving through a neon city at midnight"
  }'

Read the returned task's id, then use it in the task endpoint. TASK_ID below is a placeholder for that actual value:

curl "https://reapi.ai/api/v1/tasks/TASK_ID" \
  -H "Authorization: Bearer $REAPI_API_KEY"

A successful submission is not finished audio. Keep polling while the task is pending or processing, stop on failure, and consume the output when status is completed. Polling does not consume credits.^[4]

We ran one V6 generation through the production playground during preparation. The completed response contained two entries in output.audio_urls and two in output.tracks. That verifies this example's output count; it is not a performance or reliability benchmark.

Store each returned output.tracks[].id when present, together with its parent task ID. Do not substitute the audio URL for an audio_id. The reference guarantees a track URL, while empty metadata fields can be omitted, so handle missing lyrics, duration or identifiers explicitly before enabling a follow-up action.^[4]

For exact lyrics, switch to custom mode and supply style and title as well. The Suno V6 version parameter does not change the meaning of custom_mode: duration control is honored in custom mode, with an integer target from 10 to 360 seconds.^[4]

What a V6 call costs

The Suno V6 rate card, checked September 14, lists song generation at $0.06, or 60 credits, per completed request. Both returned takes are covered. Dividing by two gives $0.03 per returned track; that is arithmetic, not a separately purchasable per-track price.^[3]

If you use only one take, your usable song still cost $0.06. A new generation or a follow-up operation adds its own charge. There is no discount for selecting Mini or requesting a shorter song within the supported range.^[4]

Sound FX is different: its raw listed rate is $0.0125, while the whole-credit debit is 13 credits, equivalent to $0.013. Use the billed credit amount in a budget rather than rounding the raw rate down.^[3]

For credential setup, follow the Suno API key guide. The complete pricing table covers the other operations, while the official API status guide explains the separate access question.

FAQ

Is Suno V6 available through an API?

reAPI documents V6, V6 Mini and V6 Wild through its audio task endpoint. This is separate from Suno's own developer-interest application.^[4]^[5]

What is the difference between the three variants?

Suno positions V6 for precision, Mini for faster creation and Wild for exploration. Choose using your own acceptance criteria; no quantified performance difference is claimed here.^[2]

Do the variants cost the same?

Yes, for the same reAPI operation. Song generation is $0.06 per completed request for each variant.^[3]^[4]

Can I still send V5_5?

The schema accepts it, but the documented generation path fails because the version is retired. Use a current V6 value for new jobs.^[1]

Which Suno V6 features need integration changes?

Check version selection, snake_case fields and operation-specific inputs. Consumer features mentioned in a release announcement do not automatically become request parameters.^[1]

Is version optional?

Only on suno-add-vocals and suno-add-instrumental among the eight V6-page operations. Those default to V6; song generation requires an explicit value.^[4]

How long can a generated track be?

The documented custom-mode duration target is 10–360 seconds. It does not apply in inspiration mode.^[4]

Does every operation return two songs?

No. The two-take pricing example applies to song generation. Lyrics, WAV, separation and other operations have distinct output types and should be parsed accordingly.^[1]

Migrate the request, then preserve the track identity

Begin with one current-version request and follow it through completion. Check the emitted JSON, save the returned task and track IDs, and then test the next operation your application actually needs. That completed path, including failure handling, is the useful acceptance check for a Suno V6 API migration.

References

reAPI. Suno API reference. Retrieved September 14, 2026 from reapi.ai/docs/suno.
Suno. Introducing v6. Published September 9, 2026; retrieved September 14, 2026 from blog.suno.com/blog/introducing-v6.
reAPI. Suno V6 public rate card. Retrieved September 14, 2026 from reapi.ai/models/suno-v6.
reAPI. Suno V6: versions, parameters and billing. Retrieved September 14, 2026 from reapi.ai/docs/suno-v6.
Suno. Developer API intake form. Retrieved September 14, 2026 from sunomusic.typeform.com/apiform.