Voice Changer API
Convert source vocals with a configured voice pack. The voice changer API supports accent strength, tonality reference, and async output delivery.
MP3 / WAV / AAC / OGG
Required
Any number from 0 to 1; default 1
source_file or voice_pack
Optional
mp3, wav, flac, aac, or ogg
What you can build
Real workflows powered by this model.
Voice changer API for voice pack conversion
Use the voice changer API when your product already has a target voice pack id and needs to convert source vocals through an async backend call. The user chooses a pack, your backend sends voice_pack_id, and the task returns converted_mix output. That fits apps where voice selection happens in your own product before audio processing starts. The voice changer API keeps the audio task focused on conversion while your app owns pack browsing and permissions.
Change a voice
Voice changer API controls for accent and tonality
Set accent from 0 to 1 and choose source_file or voice_pack tonality. The voice changer API gives product teams clear controls without a complicated audio editor. That keeps the conversion form understandable for non-engineering users. Your UI can expose simple defaults first, then let advanced users tune only the fields they understand. The voice changer API works well when the product needs a guided voice-pack flow rather than a full editing surface.
Voice changer API output for publishing flows
Completed voice changer API tasks return the converted voice as a downloadable track. Store it, preview it, or send it into moderation and publishing flows. output.tracks can identify converted_mix when labels are available.
Pricing
Credit-based — 1 credit = $0.001 USD. Pay only for completed generations.
| Mode | Category | Unit | Price |
|---|---|---|---|
| Voice conversion | |||
| Source voice | 1 started minute | $0.2 200 credits | |
Why reAPI
Why this voice changer API requires a voice pack
The voice changer API requires voice_pack_id, so each task targets the configured voice asset your product selected. That keeps conversion behavior tied to a known pack. It also keeps pack selection outside the audio upload itself.
Small controls, useful range
Accent uses a real 0 to 1 value, and tonality_reference accepts source_file or voice_pack. Those fields cover the common style choices without burying users in audio terms. Save the submitted values with each task so support and moderation teams can reproduce a result later.
Voice changer API with the same polling contract
Submit a task and poll /api/v1/tasks/:id until completion. The voice changer API fits the same async model as the other reAPI audio pages. Backend teams can reuse task storage, retries, and result handling. The voice changer API works best when the UI shows queued, processing, completed, and failed states clearly.
Integrate the voice changer API in three steps
- step 01
Create an API key
Generate a reAPI key from workspace settings. Keep the voice changer API call on your backend so voice pack ids and keys stay server-side.
Open - step 02
Submit a conversion task
POST model audio-voice-change with audio_url and voice_pack_id. Add accent, tonality_reference, dereverb_enabled, or encoder_format when your flow needs them.
Open - step 03
Poll and play the result
GET /api/v1/tasks/:id until completed. Download output.audio_urls or use output.tracks to find the converted_mix track.
Open
Frequently asked questions
Common questions about this model.
curl https://reapi.ai/api/v1/audio/generations \
-H "Authorization: Bearer $REAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"audio-voice-change","audio_url":"https://cdn.example.com/source-vocal.wav","voice_pack_id":"voice_pack_id_here","accent":1,"encoder_format":"mp3"}'Ready to ship?
Try it in the playground or grab an API key to integrate now.