Hi team, I’ve followed all setup instructions for linking my Twilio number to my Vapi assistant, but every incoming call is returning a 404 Not Found error from the webhook endpoint. Call ID: CA65dc0fa22e859ca3d708495a8376e33 Timestamp: June 30, 2025 at 11:34:57 PM PDT (UTC: 2025-07-01 06:34:57) Expected Response: Successful call routing to my published assistant “Sedona” Actual Response: Got HTTP 404 response to https://api.vapi.ai/phone-calls Message: "Cannot POST /phone-calls" statusCode: 404 Screenshots attached show full request logs from Twilio. Let me know if there's anything else you need to resolve it — thanks in advance! https://cdn.discordapp.com/attachments/1389498040267706419/1389498040678875185/20250630_233637.jpg?ex=6864d664&is=686384e4&hm=b886568e115fb63849397cb6a8145248e69ad388e3881a4ea793b27d47b25ac5& https://cdn.discordapp.com/attachments/1389498040267706419/1389498041324539914/20250630_233650.jpg?ex=6864d664&is=686384e4&hm=310724c905948785365b54639a615543969bb4b3a08c60a5f0192582bfd7da67&

Please use the endpoint /call instead of /phone-calls. Let us know if you require additional support

"We are sorry. An application error has occurred." That's all I get when I test the # after doing your suggestion.

Could you please send the request body?

Here’s the full request body from Twilio logs: URL: https://api.vapi.ai/call HTTP Status: 401 (Unauthorized) Parameters: - Called: +15034761376 - ToState: OR - CallerCountry: US - Direction: inbound - CallerState: OR - ToZip: 97132 - CallSid: CA0ddc6696c1731cb23efd8730636dc33d - To: +15034761376 - CallerZip: 97392 - ToCountry: US - StirVerstat: TN-Validation-Passed-A - CallToken: (long encoded token string) - ApiVersion: 2010-04-01 - CalledCity: NEWBERG - CallStatus: ringing - From: +15038934160 - AccountSid: AC7dfbab1bdb29035d80db638300a63 - CalledCountry: US - CallerCity: AUMSVILLE - ToCity: NEWBERG - FromCountry: US - Caller: +15038934160 - FromCity: AUMSVILLE - CalledState: OR - FromZip: 97392 - FromState: OR Response Body: json { "message": "Missing Authorization Header", "error": "Unauthorized", "statusCode": 401 }

If you have configured your Twilio phone number to your assistant in vapi, you only need a few parameters. Below is the example request body for using the /call endpoint as a cURL request. Also include the authorization header with your VAPI API key as the bearer token:

curl -X POST https://api.vapi.ai/call \
     -H "Authorization: Bearer <VAPI_API_KEY_HERE>" \
     -H "Content-Type: application/json" \
     -d '{
  "assistantId": "<ASSISTANT_ID>",
  "customer": {
    "number": "<CUSTOMER_NUMBER>"
  },
  "phoneNumberId": "<PHONE_NUMBER_ID>"
}'

You gave an example of how to make an outbound call from Vapi using their API, but that’s not the same thing as what we’re trying to do. We’re not trying to trigger a Vapi-to-customer outbound call — we’re trying to receive inbound calls from Twilio and have them route into Vapi correctly. So ..... How is Twilio supposed to pass Vapi the authentication token in a webhook (it can’t). How to map your specific Twilio number to the correct assistant ID inside Vapi. Whether Vapi has some hidden backend connection step when you attach a Twilio number via their dashboard. Or whether you’re expected to use a Twilio Function as a proxy to inject those headers (which most devs end up doing when dealing with this kind of setup).

Sorry for the misunderstanding. Here is the proper webhook: