reAPI
Music Extractor API
From $0.200 per started minute
Audio
Vocal Remover API
Add a vocal remover API to your app. Send a public song URL, remove vocals, and return vocal plus instrumental tracks through one async task.
- Highlights
- Vocal isolation · deep or clear-cut extraction
- Best for
- Karaoke, acapellas, remixing
- Input
- Audio file URL
- Output
- Vocals + instrumental
Input
0/1 file
MP3 / WAV / AAC / OGG
vocals
Default auto
deep_extraction or clear_cut
Optional: lead_back
Optional
mp3, wav, flac, aac, or ogg
Result
What is the Vocal Remover API?
The Vocal Remover API is reAPI's async source-separation endpoint: post a public song URL and get back the isolated vocal track plus the instrumental left behind. Seven splitter engines (auto plus six named ones), two extraction levels — deep_extraction or clear_cut — an optional dereverb pass, a lead/backing vocal split, and five output formats (MP3, WAV, FLAC, AAC, OGG) control how the split is made. Jobs are billed per started minute of source audio, so a 2:30 track bills as 3 minutes.
What you can build with this model
Real-world workflows and production use cases you can build and ship with this model.
Vocal remover API for karaoke tracks
Use the vocal remover API to turn a mixed song into a backing track for karaoke apps, rehearsal tools, and creator workflows. Your product sends one audio URL and gets downloadable tracks back after the task completes. The vocal remover API keeps the user flow short: upload, wait for completion, play the instrumental.
Remove vocals
Vocal remover API for remix editors
Route isolated vocals into remix, mastering, sampling, or moderation pipelines. The vocal remover API returns labeled tracks, so your editor can place the vocal and instrumental outputs in the right lanes. That label mapping matters when users export ZIP files, timelines, or preview players. Use the same labels to keep project files, download names, and moderation records consistent. The vocal remover API also helps teams keep one source task connected to every exported track.
Production vocal remover API jobs
Client uploads fail, networks drop, and users refresh tabs. Keep your own task record before calling the vocal remover API, then poll the returned task id until output is ready. That keeps paid workflows and batch queues tied to one reAPI task. For batch jobs, store the source URL, selected format, and task id before showing the user a progress state.
Pricing
Credit-based — 1 credit = $0.001 USD. Pay only for completed generations.
First test cost
$0.2200 credits
One sample at the cheapest tier (1 started minute).
Testing budget guide
Add credits$10
≈ 50 tests
$50
≈ 250 tests
$100
≈ 500 tests
| Model | Category | Price |
|---|---|---|
| Vocal removal | Source audio | $0.2 200 credits · 1 started minute |
Why reAPI
Why this vocal remover API is pinned to vocals
This vocal remover API page submits the stem-separator model with stem fixed to vocals. Users do not have to pick from every possible instrument when the job is simply remove vocals. The playground and docs both reflect that same constraint.
Lead and backing vocals when needed
Set multivocal to lead_back when your product needs lead and backing vocals as separate outputs. If backing vocals are not detected, the task still returns the available tracks. This is useful for rehearsal products, cover tools, and editors that need to mute only the lead vocal while keeping harmonies in context.
Vocal remover API output your app can map
Completed tasks return audio URLs and track metadata when labels are available. That makes the vocal remover API easy to wire into queues, editors, and download pages. Your backend can store the task id first and attach URLs after polling finishes.
Integrate the vocal remover API in three steps
- step 01
Create an API key
Generate a reAPI key from workspace settings. The same key works across image, video, and audio endpoints, including the vocal remover API.
Open - step 02
Submit a vocal removal task
POST to /api/v1/audio/generations with model audio-stem-separator, stem vocals, and a public audio_url. Add output format or lead_back only when your workflow needs it.
Open - step 03
Poll and download
GET /api/v1/tasks/:id until the task is completed. Download output.audio_urls or read output.tracks to map vocals, no_vocals, and optional lead/back labels.
Open
docs/api/vocal-remover
curl https://reapi.ai/api/v1/audio/generations \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"audio-stem-separator","audio_url":"https://cdn.example.com/song.wav","stem":"vocals","encoder_format":"mp3"}'Parameter validation failed
Rejected synchronously with the failing field named. Check enum values, ranges, and URL fields — nothing is charged.
Authentication or balance issue
401 means a missing or invalid Bearer key; 402 means the reserve exceeds your balance. Manage keys and credits in the console.
Content or material rejected
Reference material and outputs pass automated moderation. Rejected tasks fail with a clear error and a full refund.
Task failed or timed out
A task that reaches a failed state is never charged — the reserve refunds automatically. Keep the task id and retry when ready.
Frequently asked questions
Common questions about this model.
The vocal remover API is an async source separation endpoint for removing vocals from a mixed audio file. Send a public audio_url, set model to audio-stem-separator with stem vocals, and poll until the task returns vocal and no_vocals tracks. Use the vocal remover API when your product needs karaoke, remix, or rehearsal output without a manual editor.
Related models
Explore more models in the same category.
reAPI
Multistem Splitter API
From $0.200 per selected stem minute
Audio
reAPI
Voice Changer API
From $0.200 per started minute
Audio
reAPI
Voice Cleaner API
From $0.200 per started minute
Audio
start building
Ready to ship?
Try it in the playground or grab an API key to integrate now.