I purchased a phone number via Twilio and imported it into Vapi. I have reconfigured the setup three times, created the assistant, and mapped everything correctly. However, whenever I call the number, I receive a message stating the number cannot receive calls. Twilio support ran some tests and identified a 404 Error. I’ve double-checked the assistant and number settings in Vapi, but the issue persists. Could you help me identify why the webhook or the communication between Twilio and Vapi is failing? When Twilio makes a request to this URL to obtain instructions and proceed with the call, we get a 404 error as a result - image below. https://cdn.discordapp.com/attachments/1468022669734838421/1468022670065930395/1f4149fe-9801-4039-b3e3-2d96273cba0e.jpg?ex=69828227&is=698130a7&hm=ace0622c0aa4d64abe47e670f331249d0f2beac1795fb1f106b1c6c5bb3a3b23&

Action Required: Do not manually set the webhook URL in Twilio to

/twilio/inbound

. Instead, use the Vapi dashboard's "Import" function to add your Twilio number—this will automatically configure the correct webhook for you. - In Vapi: Go to Phone Numbers → Import, enter your Twilio number and credentials, and complete the import. This should resolve the 404 error, as Vapi manages the webhook integration internally. [See the official guide for details](https://docs.vapi.ai/phone-numbers/import-twilio). Source: - [Import number from Twilio](https://docs.vapi.ai/phone-numbers/import-twilio)

it looks like Twilio is hitting a 404 because your server doesn’t have a route at /twilio/inbound. This usually happens if the POST route is missing, the URL doesn’t match, or middleware isn’t set up correctly. I can help you get it configured so Vapi can receive calls. Are you running this locally with ngrok or on a live server, and which backend framework are you using? @Eduardo Bitar Neto

I tried Just Import using vapi route but didnt work. Them i tried to put myself and the results was the same …. Help center Twilio tried and told me the issue was in vapi platform. I accept all help you can do … how we can do?

Thanks for explaining what you tried. Since Twilio confirmed the request is leaving their side and both the Vapi import and a custom webhook still return a 404, it looks like the issue is really in how Vapi is handling the inbound call. The best way forward is to go step by step: check that Twilio is sending the request correctly, see exactly what Vapi expects, and make sure the number is fully linked to an active assistant on their backend. I’ve handled similar cases by digging into the API-level setup where the UI sometimes misses things. Let’s go over this privately so I can take a closer look at your setup and get it sorted quickly. @Eduardo Bitar Neto

The webhook URL for receiving calls to twilio numbers is https://api.vapi.ai/twilio/inbound_call