previously functional phone number creation now fa...
# support
c
I was testing my code just now and a minute ago the creation of phone numbers stopped working with 400 bad request I am sending this request { "provider": "twilio", "twilioAccountSid":"ACcd3d0e00bb295755aaae214bbba17236", "twilioAuthToken":"********************************", "name": "Sally smith", "assistantId": "62e83fda-08f0-4e93-b6a1-41ec80d2470d", "number": "+1628*******" } I checked both the api docs and swagger and the request complies with the format and rechecked the accountsid, authtoken,assistantID and number to make sure everything is correct and they all are Also the token works because it still works for other requests to other endpoints
Also the code creating the requests hasn’t been changed for the past week, so im confused on the reason of why it stopped
v
@Cowboy I'm glad to hear that you've already checked the API documentation and verified your credentials. Since you're receiving a 400 Bad Request error, it typically indicates that there's something wrong with the request you're sending. Here are a few things you can check: 1. **Required Fields**: Ensure that all required fields are included in your request and that they are correctly formatted. 2. **Parameter Values**: Double-check the values for each parameter, especially those that require a specific format, such as phone numbers. 3. **API Endpoint**: Confirm that you're sending the request to the correct API endpoint. 4. **HTTP Method**: Make sure you're using the correct HTTP method (POST, GET, etc.) for creating phone numbers. 5. **Rate Limits**: Check if you've hit any rate limits that might prevent the creation of new phone numbers. 6. **API Changes**: Sometimes, APIs are updated, and the documentation might not reflect those changes immediately. Verify if there have been any recent changes to the API that affect phone number creation. If everything seems correct on your end, it might be helpful to see the exact error message returned by the API. This can provide more insight into what's going wrong. If you can provide me with the error message, I might be able to offer more specific advice. If you're unable to resolve the issue with this information, please reach out to support for more detailed assistance.
You can continue this conversation by mentioning me in the message.
Got it. Tagging @User for additional help.
c
According to the docs the required fields are provider, sid, auth and number and i have provided correct values for all and the endpoint is correct i even tried it through swagger to make sure
@Vapi
v
@Cowboy It's good to know that you've verified the required fields and the endpoint. Since you've also tried it through Swagger and are still encountering the issue, it might be a temporary problem with the API service or an issue that's not immediately apparent from the request itself. Here are a few additional steps you can take: 1. **Error Logs**: Check if there are any logs available that might give more details about the error. 2. **API Service Status**: Look for any status updates from the API provider that might indicate a service disruption or known issue. 3. **Contact Support**: Since the problem persists and isn't clear from the request, it might be best to contact the API provider's support team. They can provide more detailed insights into the issue. If you have access to the error message or logs that the API is returning, please share them with me, and I'll do my best to assist you further. If not, reaching out to the API provider's support team is the recommended next step.
c
All the logs show currently is 400 bad request
@Vapi
v
@Cowboy I understand that receiving a generic 400 Bad Request error without additional details can be frustrating. Since the logs aren't providing more information, and you've confirmed that the request is structured correctly according to the documentation, it's possible that there's an issue on the API provider's side or a subtle issue with the request that isn't immediately obvious. At this point, I recommend reaching out to the API provider's support team for further assistance. They should be able to look into their internal logs and give you more specific information about why the request is failing. Would you like me to assist you with contacting support or provide you with guidance on how to reach out to them?
c
Yes contact support please
@Vapi
v
@Cowboy Sweet. Have a great day!
2 Views