vapi.calls.create
# support
l
I have a very simple test program which was working before and now is not: import { VapiClient } from "@vapi-ai/server-sdk"; const VAPI_API_KEY = "VAPI_API_KEY"; const vapi = new VapiClient({ token: VAPI_API_KEY, }); const assistant_id = "ASSISTANT_ID"; const phone_number_id = "PHONE_NUMBER_ID"; const phone_number = '+1xxxxxxxxxx'; async function makeOutboundCall(assistant_id, phone_number_id, phone_number, selected_specialist, referring_practice) { try { const call = await vapi.calls.create({ assistant: { assistantId: assistant_id, }, phoneNumberId: phone_number_id, customer: { number: phone_number, }, assistantOverrides: { variableValues: { selected_specialist: selected_specialist, referring_practice: referring_practice, }, }, }); console.log("Call initiated:", call.id); return call; } catch (error) { console.error("Error initiating call:", error); } } const call = makeOutboundCall(assistant_id, phone_number_id, phone_number); console.log(call); This is almost directly taken from examples, and was working up until very recently. Now it gives a 400 error with the following message: 'assistant.property assistantId should not exist' Which makes no sense looking at the documentation because assistantId is clearly required. I've tried it multiple times but one timestamp is 'Tue, 15 Jul 2025 14:09:14 GMT' I am not getting a call id back because it isn't getting queued.
I also tried copying the json for the assistant in using just assistant: instead of assistantId: and then it complains if phoneNumberId is missing, but complains it is not allowed if it is there.
c
Hey Leeland Heins, I wanted to let you know that we're managing a high volume of support requests at the moment, so our response time might be a bit slower than usual. I truly appreciate your understanding and will get back to you as soon as possible!  Thanks again for your patience!
The Vapi API no longer accepts `assistant: { assistantId: ... }`; instead, pass
assistantId
as a top-level field in the
create
call..
l
I figured that out yesterday and was just coming back to mark this as resolved.
c
Hey Leeland Heins, I sincerely apologize for the delay in our responses this week. We experimented with some process adjustments that didn’t work as intended, and unfortunately, this caused some disruptions. That’s entirely my responsibility. Just a quick note—our team is unavailable on weekends. However, if something urgent or critical comes up, feel free to reach out to me directly, and I’ll assist you. The support issues will be resolved in the coming weeks, and starting Monday, you can expect more consistent and improved support. Thank you so much for your patience and for continuing to stick with us!
l
This issue can be marked as solved. It isn't letting me do that.
Never mind, I figured out how to change the tag to solved.
c
Sounds, good.
3 Views