API Assistant Creation with PlayHT
# support
b
Hey Vapi support team, I'm attempting to create an assistant through your api that uses a cloned voice from PlayHT. I'm running into a 400 json response code when creating my assistant: message: "Voice s3...manifest.json not found for provider PlayHT". However, I know this is a correct voice ID from PlayHT as I've checked through their api. I've also definitely verified my PlayHT credentials in your dashboard. What am I doing wrong here?
v
message has been deleted
@bertiefa Hello! I'm here to help you with your issue. It sounds like you've done the right steps by verifying your PlayHT credentials and checking the voice ID. The error message you're receiving indicates that there might be an issue with the way the voice ID is being referenced or accessed in the request you're making to our API. To assist you better, could you please provide me with the exact request you're sending to our API? This will help me understand if there's a formatting issue or if there's something else we need to look into. If you're not comfortable sharing the full request, just the structure or the part where you're specifying the voice ID would be helpful.
You can continue this conversation by mentioning me in the message.
b
I'm wondering if there's support for using a cloned voice ID in the api because it works in the dashboard
c
You need to put the ID most likely.
Not the name.
b
I did
Copy code
{
  "name": "Test",
  "voice": {
    "provider": "playht",
    "voiceId": "s3://voice-cloning-zero-shot/bb9fd093-dd6f-4e01-8744-59bea5d20328/original/manifest.json"
  },
  "firstMessageMode": "assistant-speaks-first",
  "firstMessage": "Hello, I'm Bertie. How can I assist you today?",
  "model": {
    "provider": "openai",
    "model": "gpt-3.5-turbo"
  }
}
c
That looks like its from AWS no?
b
This is the response from playht: { "id": "s3://voice-cloning-zero-shot/bb9fd093-dd6f-4e01-8744-59bea5d20328/original/manifest.json", "name": "Test", "type": "instant", "gender": "male", "voice_engine": "PlayHT2.0" },
when I retrieve my voices
The ID is definitely correct
c
The voice id is prob just the name
b
Copy code
{
  "message": "Voice Test not found for provider playht",
  "error": "Bad Request",
  "statusCode": 400
}
Also doesn't work
c
Hmm weird. I do see all the ID's return that way with S3. Something we missing @Sahil
s
Most probably my guess is that you are not using the correct manifest.json file
b
I figured it out. For future readers who need support you need to update your credentials everytime you make a new clone so that Vapi can see the new voice
So there essentially needs to be a layer of credential updating before the assistant is created