babblevoice and it's evolving API

It’s been 5 years since the introduction of the babblevoice API. The API was introduced right from the start of babblevoice. We felt that the data we generate and store on your behalf was your data, so providing access was paramount. More importantly not only providing access, but doing it with style – so that your applications can use it – not just the likes of MS Excel.

For the uninitiated an API (Application Programming Interface), is simply a defined way that you can retrieve information from our system. We publish the specification for the API to make it relatively simple for you. We conform to a bunch of standards so that you can use the programming language of your choice to to connect to us. Since publishing our first API, we have introduced 3 further APIs. All centred around babblevoice, but they all perform slightly different functions. So this blog entry is simply an introduction to help you start finding your way around.

babblevoice API

Ok, this was the first one. If you have used our netvibes gadgets (, then this is the main API they use. If we store information in babblevoice (such as call records) then you can use this interface to access them. It also has a few functions like make call, transfer call.

babblevoice Presence API

This uses a little bit of the babblevoice API, but extends it to allow you access to the real-time information regarding things like phone’s status (available, on the phone etc). It was designed to be used in applications, but most importantly built into Web (HTML5) applications. Our very own babblevoice Desktop product is a good example of this in use.

baaXML (babblevoice Auto Attendant XML)

Now this one is completely different! This is a method of handling a call by building it into your very own system. By the way, the difference between an auto attendant and IVR is an IVR connects to another system, whereas auto attendant is simply please press one for this etc (perhaps we should have called it bivrXML!). baaXML can be configured to call your own web application to issue instructions on how to handle the call. We have a great YouTube video on writing a simple PHP script to access the Sugar CRM contact database to add functionality to your phone system. This is the area you might want to look at if you want to build applications to allow callers to, for example, check expected delivery schedule, book appointments – your imagination is the limit.

babblevoice Desktop Javascript API

This is our newest API, it allows our babblevoice Desktop product to be extended. If you are extending your Web CRM system to be integrated with babblevoice you have 2 options. The presence API (see above) and now this API. If you use the Javascript API, you immediately get all of the dashboarding functionality built into babblevoice Desktop, it really does save a lot of leg work.

Our aim is to give Web developers the ability to extend their applications without any experience of telephony applications. We would love to hear if we have achieved this and hear about the applications you develop.

The babblevoice team

By Nick Knight, Jul 13, 2015