From the user’s perspective, this is a standard request. In the response, we include specific headers: ‘Transfer-Encoding’ is set to ‘chunked’ to enable streaming, ‘Connection’ is set to ‘keep-alive’ to maintain the connection, and ‘Content-Type’ is set to ‘audio/wav’ to indicate the media type. These headers allow the client to stream audio data from the server in real time. Important Note: after collecting the chunks, you need to add the wav header manually to the data. If you wish to get a wav header, please use the Generate TTS File Data API
Pass the API key in the Authorization header, You need to put Token keyword before the API key. e.g. 'Authorization: Token
The text to be generated as an aduio file.
"مرحباً بكم في جميعاً في همسة!"
The speaker name, Suggestions: Amjad, Lyali, Salma, Mariam, Dalal, Lana, Jasem, Samir, Carla, Nada, or you can provide another values from the voice agents dashboard. You can also provide your own cloned voice's id here in the speaker field, but you need to preload that voice into the system first from here
"Majd"
The dialect of each country by its country code. Recommended voices per dialect are: pls (Palestinian): Amjad, Layan, Talin, Rema, Ali; leb (Lebanese): Carla, Majd; jor (Jordanian): Lana, Jasem, Nada, Sarah; syr (Syrian): Dalal, Mais; ksa (Saudi): Hiba, Khadija, Fahd, Jasem; bah (Bahraini): Mazen, Ruba; uae (Emirati): Salma, Dima; egy (Egyptian): Mariam, Samir, Nada, Ali, Ahmed; irq (Iraqi): Lyali, Fatma.
pls, egy, syr, irq, jor, leb, ksa, uae, bah, qat, msa "pls"
Whether to use 'Mu-Law' algorithm in voice signal processing or not.
false
Streamed Successful Response - Chunked
The response is of type file.
"00000000: 52 49 46 46 FF FF FF FF 57 41 56 45 66 6D 74 20 "