Voices
Munsit offers a variety of voices with different accents, including Fusha, Emirati, Saudi Najdi, Saudi Hijazi, and more. List them all with one call, then use the voice_id in any text-to-speech request.
List voices
Retrieve a list of all available voices for text-to-speech synthesis. Requires API key authentication via the x-api-key header. Returns an array of voice objects.
Response fields
Each voice object contains:
| Field | Type | Description |
|---|---|---|
voice_id | string | Unique identifier for the voice (used in text-to-speech requests) |
name | string | Human-readable name of the voice |
description | string | null | Detailed description of the voice characteristics |
gender | string | null | Gender of the voice (male, female, or null) |
age | string | null | Age category of the voice (middle, elderly, or null) |
languages | array[string] | List of language codes supported by the voice (e.g., ["ar", "en"]) |
dialect | array[string] | List of dialects supported by the voice (e.g., ["fusha", "emirati", "najdi"]) |
type | string | null | Voice type (neural or null) |
sample_url | string | URL to an audio sample of the voice |
voice_id as an opaque string. A few ids are readable (ar-najdi-male-2), but most of the catalogue looks like PCtWbxjoNTpVQ6gIPaVZ2Hqm. There is no guaranteed ar-{dialect}-{gender}-{n} convention, and readable ids are not enumerable — neighbouring numbers are not guaranteed to exist. Always list voices with GET /voices and use the ids it returns; never construct or pattern-match one.
null values for certain fields. These are typically custom user-created voices. The voice_id can still be used in text-to-speech requests regardless of these field values.
Voice types
Voices can be categorized by dialect, gender (male or female), age (middle or elderly) and languages (supported language codes, e.g. ar for Arabic, en for English).
fusha is Modern Standard Arabic; najdi and hijazi are the Saudi dialects.
Featured voices
Below are the featured Munsit voices available in the text-to-speech API. Each name links to an audio sample.
| Name | Dialect | Language | Sample |
|---|---|---|---|
| Fahad | Najdi | Arabic - English | Listen |
| Lama | Hijazi | Arabic - English | Listen |
| James | American | English - Arabic | Listen |
| Jake | American | Arabic - English | Listen |
| Mansour | Emirati | Arabic - English | Listen |
| Maha | Najdi | Arabic - English | Listen |
| Faisal | Najdi | English - Arabic | Listen |
| Turki | Najdi | Arabic - English | Listen |
| Reem | Najdi | Arabic - English | Listen |
| Mishari | Najdi | Arabic - English | Listen |
| Hala | Najdi | Arabic - English | Listen |
| May | British | English - Arabic | Listen |
| Latifa | Emirati | Arabic - English | Listen |
| Mishal | Najdi | Arabic - English | Listen |
| Maya | American | English - Arabic | Listen |
Using a voice
Use the voice_id from the response in text-to-speech generation endpoints: POST /text-to-speech/:model_id (include voice_id in the request body) or WS /text-to-speech (include voice_id in the WebSocket message). This example uses the faseeh-v1-preview model with the ar-najdi-male-2 voice.
Go further
Working with an AI assistant? Every page is available as Markdown: add .md to the URL, or send an Accept: text/markdown header. For the whole documentation in one request, point it at llms-full.txt; the page index is llms.txt. Or use Copy Page, top right.
