Custom Inworld voice ID fails with 400
# support
l
I’m trying to update an assistant to use a custom Inworld voice, but Vapi returns 400 Bad Request Assistant ID: 13fcc1ad-858e-4582-a68b-ba684dfe46a6 Inworld confirms the voice exists. Payload sent: { "voice": { "provider": "inworld", "voiceId": "voiceidstring", "model": "inworld-tts-1.5-max" } } I also tried adding "languageCode": "en", but it still returned 400. Built-in Inworld voices like Alex work in the same Vapi account, so this seems specific to custom Inworld voice IDs. Can you confirm the correct payload, or check if custom Inworld voice IDs are currently being rejected?
c
Hi there, Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST). We’ll get back to you as soon as possible during our normal business hours. If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly. Warm regards, Vapi Customer Support Team