Suno API endpoints: generation, editing and read-only
An integration plan starts with what exists and what it costs. Every endpoint falls into one of three families, and the billing line runs between them.
Generation
Creating music returns two tracks per call and is asynchronous: you submit, then poll until the status is complete. Both the simple prompt path and the custom (lyrics plus style) path live here.
Editing
Editing actions work on an existing song and each returns a new version: extend, replace a section, cover, crop, remove a range, fade, reverse, change speed, add instrumental or vocal parts, split stems, mashup, sample. These are charged, and the original is never modified.
Read-only
Checking status, listing songs, reading the parameters a song was generated with, account balance, media URLs, file downloads, lyric timelines and MIDI. None of these are billed - they read assets that already exist.
| Family | Returns | Billed |
|---|---|---|
| Generation | Two tracks per call | Yes |
| Editing | One new version | Yes |
| Read-only | Status, URLs, files, lyrics, MIDI | No |
How to plan an integration
- Poll every 3-5 seconds; never treat a slow render as a failure and resubmit.
- Store the song id, not the audio URL - URLs are temporary pickup tokens.
- Budget per generation, not per call: one call gives two songs.
- Keep the key server-side and give each environment its own.
常见问题 / FAQ
Is there a webhook?
Most providers expose polling rather than webhooks; poll the task status and stop when it reports complete.
Do downloads count against my quota?
No. Downloads are read-only operations and are not billed on per-generation platforms.
Can I edit without regenerating the whole song?
Yes. Section-level edits keep the rest intact, which is both cheaper and more consistent.
注册只需要邮箱，一次生成 0.6 元出 2 首，MP3 与 WAV 下载不限次。