Add Background
to customize how
Support
- Documentation
- |
- TTS Languages & Voices
- |
- API Examples
- |
- FAQ
- |
- Community
- |
- Affiliate
- |
- Contact
- |
- About
Contents are separated into two main sections:
- Built-in Voices
- 3rd party Voices
The built-in TTS voices are available to SitePal customers with every subscription plan that supports TTS.
3rd party voices are available from leading providers which have pre-integrated with SitePal.
To use 3rd party voices you need to :
- Set up an account with the 3rd party provider of your choice.
- Add your 3rd party API key to your SitePal 'Connect' page.
See detailed instructions in the 'Adding 3rd Party API Key' section.
The voice tables list Engine IDs, Language IDs and Voice IDs to be used in SitePal API calls.
To allow our customers a wider selection of voices and languages, SitePal is pre-integrated with several leading 3rd party TTS technology platforms. To use these voices you need to enter the corresponding 3rd party API key in your account's 'Connect' page.
For example, to use Google's TTS voices (Engine ID #11), you would need to:
- Sign up with the Google Cloud Platform
- In your Google Cloud account set up an "API resource" with permissions to access TTS API.
- Copy your API Key from your Google account, and enter it in your SitePal 'Connect' page.
Detailed instructions for locating the 3rd party API Key for each provider are available here. To preview the 3rd Party voices and find out more, we provide useful links here.
Using 3rd party voices requires the Platinum plan or higher. You will also need to sign up to the 3rd party service, and will be billed by them directly for the usage in addition to your SitePal subscription.
This document provides you with Language IDs and Voice IDs that you can use with the SitePal API, for each of the Engines we provide and support.
We have noticed however that available voices for certain 3rd party providers are frequently updated, with new voices added and older voices sometimes dropped. Consequently, the information in this document may be out of date as we catch up. This specifically relates to voices from Google Cloud (Engine 11), MS-Azure (Engine 12), and Amazon Polly (Engine 13).
That is why we've introduced an alternative way of calling the SitePal API, specifically applicable to Google, Azure & Amazon voices. You may — if you prefer — call our API with Language and Voice IDs obtained directly from the TTS voice list on the respective provider's pages. Our API automatically recognizes which method you are using.
This allows you to use any voice made available by Google, Azure & AWS as soon as it is made available, even if it has not yet been configured and setup by us – and is not listed here. Supported TTS Voices for each 3rd party can be found here:
- Google Cloud Voices - https://cloud.google.com/text-to-speech/docs/voices
- Azure TTS Voices - learn.microsoft.com/en-us/azure/ai-services/speech-service/language-support?tabs=tts
- Amazon Polly Voices - https://docs.aws.amazon.com/polly/latest/dg/voicelist.html
An example should help make this clear. Let's say you want to use the Google voice...
Following the 'standard' method, you would look this voice up in the Google voice table below, and identify the voice ID as 135. You could then call any SitePal API speech function (such sayText) with the following parameter values:
LID = 1 (for English, see language table)
VID = 135
Using the direct method - you would locate the voice on Google's list of voices on their site, and use the following values:
LID = en-GB
VID = en-GB-Chirp3-HD-Achernar
Both calls would produce exactly the same result.
Note that both LID & VID parameters must match in modality, either text or numeric.
This is a list of all the available languages and their IDs.
Languages marked with an * are ONLY available via 3rd party integration.
| Language | ID | Language | ID | Language | ID |
|---|---|---|---|---|---|
| Loading languages… | |||||
The following TTS voices are built-in to the SitePal platform.
They are available with every subscription plan that supports TTS.
| Language | Lang. ID | Voice | Voice ID | Gender | Description |
|---|---|---|---|---|---|
| Loading... | |||||
| Language | Lang. ID | Voice | Voice ID | Gender | Description |
|---|---|---|---|---|---|
| Loading... | |||||
| Language | Lang. ID | Voice | Voice ID | Gender | Description |
|---|---|---|---|---|---|
| Loading... | |||||
| Language | Lang. ID | Voice | Voice ID | Gender | Description |
|---|---|---|---|---|---|
| Loading... | |||||
| Language | Lang. ID | Voice | Voice ID | Gender | Description |
|---|---|---|---|---|---|
| Loading... | |||||
| Language | Lang. ID | Voice | Voice ID | Gender | Description |
|---|---|---|---|---|---|
| Loading... | |||||
Updated July 2025.
Voices in RED are deprecated by Google, though most still work at this time.
| Language | Lang. ID | Voice | Voice ID | Gender | Description |
|---|---|---|---|---|---|
| Loading... | |||||
| Language | Lang. ID | Voice | Voice ID | Gender | Description |
|---|---|---|---|---|---|
| Loading... | |||||
| Language | Lang. ID | Voice | Voice ID | Gender | Neural | Description |
|---|---|---|---|---|---|---|
| Loading... | ||||||
Eleven Labs voices are account-specific, with users creating and naming their own custom voices. As such, there is no fixed voice table available.
To locate your available voices and Voice IDs, go to the Connect page in your SitePal account and click on Available Voices next to the Eleven Labs API key. A list of voice names and Voice IDs will be displayed.
Use the listed Voice IDs as your API Voice ID parameter for your selected voices. (Note: unlike other engines, Eleven Labs Voice IDs are alphanumeric strings.)
Eleven Labs voices can be multilingual depending on the model selected. We automatically choose the optimal model for you based on the language you specify in the SitePal API. You may override this by using the xData1 parameter — see the Client API Reference for details.
The Engine ID for Eleven Labs is 14.
The TTS voices made available by OpenAI are designated by name, which also serve as their ID.
As of this moment, available voices are:
When using any of the SitePal speech API calls, use the above names (lowercase) as the voice ID parameter. As voices may be added by OpenAI from time to time, you will be able to use a newly available voice even if it does not yet appear on the above list, by specifying its OpenAI name as the voice ID when calling any SitePal speech function.
OpenAI voices are multilingual, and they auto-recognize the language by the input text. OpenAI provides no method for language specification, and the SitePal API language ID (required) parameter is ignored. Use 1 as the language ID parameter for now.
OpenAI provides certain options that are not available within our parameter set, such as "model" and "speed". We use OpenAI's recommended default values for these options, but you may override them by using the xData1 parameter — see Client API Reference for details.
You can view currently available voices, supported languages, and other information on the OpenAI website here: https://platform.openai.com/docs/guides/text-to-speech/
The Engine ID for OpenAI is 15.
To connect your SitePal account with any of our TTS partnered services, you need to add your 3rd party API key to your SitePal account. This is done in your SitePal account on the Connect Page.
But before you can add your 3rd party key, you need to locate or create it. In each case, the API key is located in a different location, and can be a bit of a challenge to find. The following instructions will hopefully prove helpful.
Your first step would be to sign up for the service of your choice.
Then proceed to follow the instructions below:
Here's what you need to do to locate your Google API key:
- Login to your Google Cloud Console
- You must have a Project defined — if not, create one.
- Select “APIs and Services”
- You will see all Google APIs which are enabled for the current project.
- One of them must be “Cloud Text-to-Speech API” — if not, select “+ Enable APIs & Services” at top and add it.
- On the left hand menu bar, click on “Credentials” — and select “+Create Credentials” at top to create your API key.
- Click on the key name to edit your key.
- Verify that it is not IP or Website restricted
- If it is restricted to specific APIs (generally a good idea) - verify that the Cloud TTS API is included.
- We recommend creating & using a specific key — and not piggybacking on another key (which may already have existed)
- Your API Key is displayed at top right. Copy it into your SitePal “Connect” page.
Here's what you need to do to locate your Microsoft Azure API key:
- Login to your MS-Azure portal
- You must have an active subscription – if not, create one, by going to “Subscriptions” from your home page.
- On your home page, if you see “Speech Services” as one of the services listed at the top of the page, click on it. Otherwise, at the top of your home page, click on “Create a Resource” (the big + button at top left).
- Enter “Speech” in the search field, and filter by “Azure Services Only”. Locate the “Speech” resource template, and click on “Create” at bottom. Fill in the relevant fields, including your preferred 'Region', to create your Speech Service resource. We suggest you name it “SitePal”, and use it for this purpose only.
- Now back on your home page, click on your “SitePal” Speech Service. Copy either of your keys into your SitePal account “Connect” page. You will also need to enter the 'Region' field, exactly as it appears on this page (eg. 'eastus')
Here's what you need to do to locate your AWS Polly API key:
- Login to your AWS Console
- To create keys with permissions limited to TTS Polly api access, you will need to create a new user with specific access permissions. From your home page, search for the “IAM” service and select it.
- On the IAM page – click on “Create User”
- Give your user a name, e.g. AWS-TTS-API (no console access) – and click Next.
- You should now be on the “Set Permissions” page. Select the “Attach policies directly” option. Then click on “Create Policy”.
- A new tab will be opened for new policy creation. On the “Policy Editor” line, select the “JSON” option and replace the json data on the left with the following:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "polly:SynthesizeSpeech",
"Resource": "*"
}
]
}
- Click on “Next” – name your policy and provide a short description. e.g. “POLLY-APIACCESS-POLICY”. Click on “Create Policy”.
- Now return to the previous tab, where “Set Permissions” is still open. Search for “Polly” & Click on the refresh button next to the “Create Policy” button. Your newly created policy should appear.
- Select your policy & click “Next” then click on “Create User”.
- You are now back on the user list. Click your new user to open the edit page. Click “Create access key” at top right.
- Copy your access key and secret access key and save your key in a safe place.
Here's what you need to do to locate your Eleven Labs API key:
- Sign up for your Eleven Labs account here (note: this is an affiliate link that benefits SitePal but costs you nothing extra)
- Sign in to your Eleven Labs account
- At top right there's a weird looking smudge, click on it and select “Profile”
- Copy your API key to your SitePal “Connect” page.
Here's what you need to know to create your OpenAI API key:
There are two kinds of keys available to open AI developers. The "User API Key" and the "Project API Key".
The "User API Key" enables API access to your accounts entire services. It provides no option for selective or limited granular access. For this reason it has been deprecated by OpenAI - but it can still be used. User API keys can be created and managed in the "Your Profile" page, which you can access from the menu at the top right of your screen.
The "Project API Key" enables API access to services assigned to a particular Project. Naturally, before you can create a "Project" key, you must first create a project if you do not already have one. Here are the steps to follow:
- Go to openai.com and select “API Login” from the 'Products' menu.
- After logging in - select “Organization Overview” from the 'Projects' menu at top left.
- Here, you may if you like create a dedicated project for using the OpenAI API with SitePal. We recommend that option. Alternatively, you can use the existing "Default" project. Whichever option you choose, the next steps are the same.
- In your 'Organization Overview' page, select 'API keys' from the left side-menu & click on 'Create new secret key'
- Here you can first decide who the owner of the new key should be. For simplicity, we will stick with "You" as the best option for now. You may optionally name your new key, then select the project this key will belong to.
- At the bottom, you have the option to restrict this key. The intention would be to provide the key with the minimal permissions it would need for TTS audio generation. This restriction is not necessary but is a recommended practice. Click on 'Restricted' at the bottom. Then enable 'Model Capabilities. This is the minimal feature that must be enabled to allow TTS Audio Generation.
- Click on 'Create Secret Key, and copy and save your key in a safe place.
To decide which 3rd Party voice is best for your application you would likely want to try out the voices and to understand how they are priced.
To preview the voices and find out more, you may find these links useful:
| Google Cloud TTS | https://cloud.google.com/text-to-speech/#demo |
| Microsoft Azure TTS | https://speech.microsoft.com/portal/voicegallery |
| AWS Polly |
To see a list of available voices - https://docs.aws.amazon.com/polly/latest/dg/available-voices.html To try out the voices you need to log into your AWS console account, then you can experiment with different voices here: https://console.aws.amazon.com/polly/home/SynthesizeSpeech |
| Eleven Labs | https://elevenlabs.io/ |
| OpenAI |
To see list of available voices and preview each - https://platform.openai.com/docs/guides/text-to-speech/ To understand pricing, scroll until see "Audio Models" here - https://openai.com/api/pricing/ |