The API is intended for developers who wish to develop client applications to extend the core functionality of babblevoice. This is the same API we develop our own Netvibes Gadgets (amongst other things). The API feed is all delivered through a REST methodology found at https://www.babblevoice.com/api. Authentication is all done through OAuth and results are returned as JSON.
This standard has been historically our main method. We are now moving towards Oauth 2 so this is being depreciated. For now we are now retiring off some parts of 1a. The following URIs are the auth URIs supported:
We also support API requests which have signed the request using Oauth1a.
The follow has been removed.
OAuth is the only method for getting authorized access to a user’s babblevoice data. OAuth is an open standard for authorizing the use of data on the web. OAuth is very popular in web services and is driven by large providers such as Google and Facebook. It is considered a very secure method of authenticating against a service. babblevoice has the following methods to work with tokens:
To access the service you will require a developer key and secret. To obtain your own developer key and secret please contact your babblevoice representative who will arrange it for you.
This is now the supported method. We have decided not to automate the issuing of tokens as this process was overly complex. Most of our integrators’ did not need this and it added additional complexity in the development process.
Users can now issue an Oauth2 token by logging into babblevoice, go to the User screen and select ‘My Tokens’. Tokens can bee issued from here.
Once obtained, they can either be used in the URL as a GET query or in a HTTP Auth header. The prefered method is via the Auth header as this will not log security tokens in proxy servers and the like.
As a http header
Authorization: Bearer <my token>
As a Cookie. The token is issued via a cookie when a user logs in via the Authentication flow. If this cookie is maintained by the client our API will check for it here.
As a query token, this should be last resort as the authentication token could be logged in Proxy server logs or in other places.
The API is broken down into the following areas
Each area is appended to the api url, for example, the CDR API has the URL https://www.babblevoice.com/api/cdr. Each API may have its own further sub queries.
The Presence API provides real time information to calls as they happen. Useful for building dashboard applications - or integrating with CRM applications.
BAAXML is our way to enable you to create advanced Auto attendants (in this case IVR). Baaxml contains more information.