Audio Operations

Suno asset operations API for Extend, Cover, M4A, MP3, WAV, and Stems

Run post-generation Suno workflows including Extend with automatic Concat, Cover, M4A, MP3, WAV, Stems, clip detail, lyrics timeline, style recommendations, and public Voice creation.

View current credit pricing

Start integrationRead docs

Why teams evaluate this API

Useful for teams that already generate music and need the surrounding operational workflows that make finished assets usable in product.

Best-fit teams

  • • Music editing products
  • • Creator tools with export and remix workflows
  • • Teams building account-backed Suno automation

Core capabilities

  • • Existing-clip Extend with automatic Concat finalization and Cover
  • • Managed M4A, MP3, and WAV delivery plus twelve-track or named-stem export
  • • Managed upload + Extend/Cover with URL safety checks
  • • Public Voice creation and read flows through the same API key and task ledger

Typical implementation flow

  1. 1Generate or import a source clip
  2. 2Run derive or export operations against the clip ID
  3. 3Use task status and resources to surface completed assets
  4. 4Chain completed outputs into Voices, timelines, or downstream product flows

Example request

Set OMNAPI_KEY on your server and create REQUEST_ID once for this logical request. Reuse that ID on transport retries. A new generation can incur a charge; review current pricing first.

curl --fail-with-body --max-time 60 -X POST "https://api.omnapi.com/api/v1/suno/clips/YOUR_SUNO_CLIP_ID/derive" \
  -H "x-api-key: $OMNAPI_KEY" \
  -H "Idempotency-Key: $REQUEST_ID" \
  -H "Content-Type: application/json" \
  --data '{
  "action": "extend",
  "continueAt": 55,
  "prompt": "Continue into a larger final chorus"
}'

Replace the placeholder with a compatible Suno clip ID and use a continueAt value within the source. Extension returns a task; read the completed resource with role final. M4A, MP3, WAV, and Stems exports use the same clip export endpoint with separate request variants.

See the authentication and task quickstart and complete request schema.

FAQ

Why separate operations from song generation?

Song creation produces a root clip or combines a managed upload with Extend/Cover. Existing-clip operations then provide Extend/Cover, exports, and metadata reads without overloading the root-creation contract.

Are all operations the same price?

No. Reads, generation, M4A, MP3, WAV, and Stems have different prices. The task response shows the customer-specific `creditsRequired` before work starts.