Telnyx integration not working
# support
r
I have bought a new number on Telnyx and set the Vapi webhook configuration in there, similar to how I would do it in Twilio. I have my server URL and key configured in Vapi, exactly the same as Twilio. However, when I call the Telnyx number, there's a large number of errors of 400 Bad Request
Copy code
"{\"message\":[\"property data should not exist\",\"property meta should not exist\",\"AccountSid must be a string\",\"ApiVersion must be a string\",\"CallSid must be a string\",\"CallStatus must be one of the following values: ringing\",\"CallStatus must be a string\",\"Called must be a string\",\"Caller must be a string\",\"Direction must be one of the following values: inbound, outbound\",\"Direction must be a string\",\"From must be a string\",\"To must be a string\"],\"error\":\"Bad Request\",\"statusCode\":400}"
https://cdn.discordapp.com/attachments/1392824304462463016/1392824304793686056/screenshot_2025-07-10_at_12.04.41.png?ex=6870f037&is=686f9eb7&hm=41648ebe0fd20a316a7cc286c12444cf5ebd6868ae1fa53106374066ea59c354&
c
To help track down this issue, could you share one or two: \- The call ID \- When exactly this happened (the timestamp) \- What response you expected to get \- What response you actually got instead This would really help us figure out what went wrong!
r
I provided what response I got. I don't know what response I'm supposed to get because it doesn't get to my systems. There's no call ID because no call is logged. Vapi immediately throws an error.
The timestamp is in the screenshot
c
To help you resolve this issue quickly, please share your phone.number_id with us..
r
a1b85e7a-2e5c-42ae-a5b2-36dde622803f
c
Hey Rex_Zane, 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!
Hi, First off, we want to sincerely apologize for the delay in getting back to you. We understand how frustrating it is to wait - especially when you're counting on us - and we owe you a clear explanation of what’s been happening and how we’re addressing it. Over the past few weeks, we've seen a significant increase in support requests. While this reflects exciting growth, it has also stretched our small team and exposed some real challenges in scaling our support operations. To improve your experience, we’ve taken a step back to reassess our approach. Here’s what we’re implementing: - Smarter Support Through Automation: We’re investing in our AI support systems to help you resolve issues more efficiently. Soon, our support bot will offer expanded capabilities, making it easier to access accurate, instant help—particularly for common or repetitive queries. - Expanding the Support Team: To meet growing demand, we’re adding 2–3 new team members focused on managing support volume and improving response times. - Prioritized SLAs for High-Usage Accounts: We’re introducing service level improvements for users who are growing with us: - Accounts with usage over 1,000 minutes/month will receive prioritized support. - For all general inquiries, we’re establishing a standardized 48-hour response time. We’re confident these steps will lead to faster, more reliable support and help us better serve you as you grow with us. Also, in case you still need help with this ongoing ticket, do let us know, and we will help you get this resolved as soon as possible. Thank you for your continued patience and for being part of our journey. Warm regards, Vapi Team
r
Hi, I still haven't received a response on this
Actually I just fixed it. I had the wrong URL setup for the inbound_call. This can be marked as solved now.
c
Glad the issue was resolved. Please reach out to us if you have any other questions regarding this issue
2 Views