Text to speech

Vbee and Fish Audio

More voices and languages through the same endpoint.

Two extra voice libraries that synthesise through the same endpoint and job flow as ElevenLabs — POST /api/v1/tts. There is no separate synthesis endpoint: list the voices, then pass the returned voice_id straight to /api/v1/tts. 1 character = 1 credit, same as ElevenLabs.

ProviderVoicesFocus
vbee1,649Vietnamese-heavy (1,212 of them) but 52 languages in total — Arabic, Hindi, Japanese, French, Indonesian, Filipino …
fishaudio273Multilingual community library, 14 languages (96 English, plus Chinese, Spanish, Portuguese, Arabic, Turkish, …)

1. List the voices

cURL
curl "https://www.dubvoice.ai/api/v1/voices?provider=vbee&page_size=50" \
  -H "Authorization: Bearer sk_..."

curl "https://www.dubvoice.ai/api/v1/voices?provider=fishaudio&gender=female" \
  -H "Authorization: Bearer sk_..."

Both providers ship as bundled catalogues, so listing needs no upstream round-trip. Filters search, language, gender, page, page_size work the same as for ElevenLabs. Each voice comes back with its id already prefixed:

JSON
{
  "voices": [
    {
      "voice_id": "vbee_n_phutho_female_anbinhan_advertise_vc",
      "name": "An Bình An",
      "gender": "female",
      "language": "Vietnamese",
      "preview_url": "https://..."
    }
  ],
  "total": 1649, "page": 1, "page_size": 50, "provider": "vbee"
}
language filter — the two providers label languages differently. vbee uses full names (Vietnamese, Arabic, Bengali (India)), fishaudio uses ISO 639-1 codes (en, zh, es, tr). The filter is an exact, case-insensitive match, so ?provider=fishaudio&language=english returns nothing — use language=en. When in doubt, list without the filter and read the language field.

2. Synthesise

Pass the prefixed id to the normal TTS endpoint — do not strip the vbee_ / fishaudio_ prefix, it is what selects the provider upstream.

Shell
# Vbee (Vietnamese)
curl -X POST "https://www.dubvoice.ai/api/v1/tts" \
  -H "Authorization: Bearer sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "text": "Xin chào, đây là giọng đọc tiếng Việt.",
    "voice_id": "vbee_n_phutho_female_anbinhan_advertise_vc",
    "voice_settings": { "speed": 1.0 }
  }'

# Fish Audio (English)
curl -X POST "https://www.dubvoice.ai/api/v1/tts" \
  -H "Authorization: Bearer sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "text": "Hello, this is a Fish Audio voice.",
    "voice_id": "fishaudio_7ffbc30676794fd989cda022638314b5"
  }'

Returns a task_id immediately; poll GET /api/v1/tts?task_id=... exactly as with ElevenLabs. Statuses, webhooks, concurrency caps and the 500,000 character limit are all identical. A voice that has been removed from the catalogue returns HTTP 400 code: "VOICE_NOT_FOUND" before anything is charged.

model_id is ignored for these providers — the upstream picks the model from the voice prefix. You may send it or omit it.

Notes

  • Inline performance tags ([warm], [pause], …) are an ElevenLabs feature and are not interpreted by Vbee / Fish Audio — the text is read as written, so leave the tags out.
  • speed (0.5–1.5) is honoured. The other legacy voice_settings fields are ignored, same as on the ElevenLabs path.
  • An ElevenLabs maintenance window does not block these providers.
  • Sending a Minimax voice id here returns MINIMAX_NOT_SUPPORTED_HERE — use POST /api/minimax-tts for those.

Search docs

Find a page or an endpoint