VAPI Integration
There is a ready-made TTS endpoint for use with VAPI custom TTS feature.
Add your Respeecher API key to VAPI
Go to https://dashboard.vapi.ai/settings/integrations/custom-credential and create a new custom credential with the following values:
- Authentication Type: Bearer Token
- Credential Name: Arbitrary, for example Respeecher API
- Token: <Your Respeecher API Key> (create one here)
- Header Name: X-Api-Key
- Include Bearer Prefix: No
Prepare a JSON request body
Create a text file vapi-custom-tts.json with the following content,
substituting <CREDENTIAL_ID> with the ID
(not the name, an ID is displayed after creation)
of the custom credential from the previous step:
Make a request to VAPI
Run the following command, substituting <ASSISTANT_ID> with the ID of your assistant
and <VAPI_API_KEY> with your private VAPI API key from https://dashboard.vapi.ai/org/api-keys (not the Respeecher API key):
Test and customize
At this point your VAPI assistant should have a low-latency Respeecher TTS voice.
If the integration works, you can repeat steps 2 and 3 with another model
(for example, substituting en-rt with ua-rt, see
Models & Languages for more details)
or another voice
(the value of X-Voice-JSON is a JSON string that describes an object
of the same format
that is used in the other TTS endpoints).
The graphical VAPI assistant builder may display the custom voice configuration incorrectly. It does not impact the actual functionality of the assistant—calls and demo pages should still work. You can temporarily revert to one of the VAPI built-in voices to use the graphical builder and then rerun the second and third steps to switch back to Respeecher TTS.
Assistant’s firstMessageMode value of assistant-speaks-first
may work incorrectly with custom TTS. Try
assistant-speaks-first-with-model-generated-message
or assistant-waits-for-user in that case.