MessageBird offers multiple tools to enable you to quickly understand any unexpected behavior between the MessageBird Voice Calling API and your application.
If you run into issues with your voice calls during their execution, the best place to start troubleshooting is the Voice Call Logs in the MessageBird Dashboard..
There you can find an overview of issues detected with your voice calls that could not directly be returned by the API as the calls were already in progress.
You can also head to the Voice Calls section to view all voice calls for the last 30 days alongside their statuses.
MessageBird uses standard HTTP status codes to indicate success or failure of an API request. Codes in the 2xx range indicate that a request was successfully processed and codes in the 4xx range indicate that there was an error that resulted from the information sent (e.g. authentication, no balance or a missing or wrong parameter).
In case of an error, the body of the response includes a json formatted response that tells you exactly what's wrong. See the reference of Errors for more details.
|HTTP status code||description|
|200 Found||The requested resource was found.|
|201 Created||A resource has been created.|
|204 No Content||The requested resource is empty.|
|400 Bad Request||The request contains invalid/missing data, or is malformed.|
|401 Unauthorized||The access key is missing or incorrect.|
|403 Forbidden||Access to the requested resource was forbidden.|
|404 Not Found||The resource could not be found.|
|405 Method Not Allowed||The HTTP method is not allowed.|
|500 Internal Server Error||Something went wrong on our end, please try again.|
If you’re still having problems troubleshooting the Voice Calling API, please don’t hesitate to contact us at firstname.lastname@example.org; we're here to help you out.