Skip to main content
GET
List voices
Pass any speaker_ids value from GET /v1/tts/speakers as the voice field in your TTS requests.
The voice catalog is live and changes over time — call /v1/tts/speakers at startup rather than hardcoding ids.

Current catalog

As of the last update to this page, GET /v1/tts/speakers returns nine voices:
The _conv suffix marks conversational variants, tuned for dialogue rather than read-aloud prose. They’re a good starting point for voice agents.
Passing a voice that isn’t in this list returns 422 with the full valid set in the body:
You can recover the live catalog from that valid_voices field without a separate call.

Listing voices

The response has exactly one key, speaker_ids. The endpoint requires authentication — an unauthenticated call returns 401.
The SDKs do not currently expose a list_voices / listVoices convenience method. Use raw HTTP as above.

Picking a voice

Different voices differ in accent, age, and energy. The best way to choose is to listen to the same line through each one.
That writes one MP3 per voice into the working directory so you can play them back-to-back.
Generation is non-deterministic — the same text and voice produce slightly different audio on each call. That’s expected and not a sign of a misconfigured request.

Authorizations

x-api-key
string
header
required

Response

200 - application/json

Successful Response