The alpha release of the BlueVia Voice API’s is, as the name suggests, an alpha! Although there are no usage limitations of the service, there are some functional limitations, that we are addressing and rolling out soon. Please see the BlueVia Voice roadmap for an overview of when our release 1.0 will be available and detail of the further functionality we will be offering soon!
The following provides an overview of immediate limitations that you should be aware of. It’s probably a good idea to give these an initial skim read so you can refer back to them when you start playing with the functionality.
If there is something further, not listed here that is causing you issues, please contact us immediately, so we can see if there is an immediate solution for you, or alternatively so we can turn around a solution for you. As always please send any issues to support@bluevia.com, or alternatively murray@bluevia.com. Also follow, and contact us at twitter @BlueVia.
For the alpha release of the platform it is not possible to purchase numbers. For the alpha we are giving you numbers in each of our launch countries:
These numbers are free for your use during the alpha period. Once the alpha has completed these numbers will be charged for, against the balance in your account. Please see the BlueVia Voice API Costs to see the monthly fees for keeping BlueVia Voice Numbers
SMS from your BlueVia Numbers is coming soon. To see when this will be available, and in which countries, please see the BlueVia Voice Roadmap
Currently there is no service usage reporting. We are working on it! This is coming soon.
This also includes error notifications. This poses an issue for inbound calls to your numbers as it is not possible to see errors generated as a result of inbound calls. We are working on providing error reporting on the portal, for debugging purposes. This will greatly aid in the analysis of issues. In the meantime, in the event that an error is due to the JSON or XML being incorrectly defined there is a way to test this:
If you create a call using the calls resource, you can then modify that call and pass in either XML or JSON commands. See the Modifying an existing call quick start guide. If there is an issue with your XML or JSON then this will be seen when you make an API call to the calls resource and pass in commands using the setcommands feature, allowing you to modify a call.
We are working to expose a report on the BlueVia portal that will highlight all errors that occur on your numbers
We are also working to expose an error notification event, see call notifications such that it is possible to be notified to your callback URL when an error occurs on your numbers
Full resource access within the BlueVia RESTful API is not available in the alpha release. The limitations within the API are highlighted within the RESTful API reference.
When using the GetDigits command any keypad input made while the Speak command or Play command are being executed will NOT interrupt the playback, and the user input will be ignored. A user can only provide IVR inpout when the embedded speak or play commands has completed. This means IVR playback cannot be bypassed by the caller.