Use case

WAV Music API

Developers who need broadcast or production-grade WAV, not just MP3, for editing suites, mastering, or delivery requirements.

The problem

MP3 is fine for preview but loses data every re-encode. Video editors, DAWs, and broadcast pipelines want WAV. Maintaining your own transcode-and-host step for that is avoidable infrastructure.

Why MusicAPI fits this

One synchronous call: POST a clip_id, get a WAV URL back in the same response. No task to poll for the export step.

Lossless: a true WAV render of the track, suitable for editing and mastering rather than a re-encoded lossy file.

The WAV is served from our own CDN, so the link is stable and the audio source stays private.

Code sample

A real request against the live API: start a job, then poll the task endpoint until the audio is ready.

curl

# Export a finished clip as a lossless WAV
curl -X POST https://api.musicapi.ai/api/v1/sonic/wav \
  -H "Authorization: Bearer $MUSICAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{"clip_id": "YOUR_CLIP_ID"}'

# -> { "message": "success", "data": { "wav_url": "https://.../track.wav" } }

Pricing

MusicAPI is pay-as-you-go with credit packs, plus predictable monthly subscriptions. The per-credit rate is the same across packs and subscriptions. See the pricing page for current rates, free credits, and volume options.

Related: Suno API · Producer AI API

FAQ

Is the WAV call synchronous?

Yes. Unlike generation, the WAV export returns the wav_url in the same response, so there is no task to poll for this step.

What quality is the WAV?

It is a true lossless WAV render of the track, appropriate for editing, mastering, and delivery, not a lossy file renamed to .wav.

Can I store the WAV URL?

Yes. The WAV is served from our own CDN with a stable URL, so you can store or hot-link it. See the pricing page for the per-export cost.

Build it in 5 minutes

Get free credits on signup and run real generations before any payment. No credit card required to start.

Start free

API details verified 2026-05-18. The API surface evolves; the pricing page always has current rates.