Due to popular demand, trunks can now have their own balances – these are ideal for assisting you with credit control of your own customer trunks. You can set these to any arbitary amount using the API (e.g. when your own customer tops up). The combined balance of your trunks can exceed your own account balance, but obviously they would be unable to utilise the full amount if your own balance is exhausted first.
The balance is decremented at the end of each call by the cost to you, e.g. the wholesale charge. We do not support billing the call at your own, custom, rates at this time but this is still a valuable tool for controlling individual customers.
You can now submit porting requests via a simple JSON API, as well as via the Beta Portal. This will be expanded in the future to also allow tracking of existing porting requests but for now we hope this will simplify porting and ensure all the information we require is provided, minimising the risk of unnecessary rejection.
This is another simple API feature that takes advantage of our unique realtime infrastructure and is useful for checking numbers are working, or providing a “1471″ type feature to your customers without the need to store the information yourself. The last call endpoint will show details about the last call to any of your numbers including the time, duration, billable duration and CLI.
New, inline response, faster CDRs
Again due to popular demand, we’ve launched a new interface to your CDRs. Although on the surface it’s almost identical to the existing reports it uses our new storage system and is much faster, negating the need for the asynchronous reporting that is used at present and returning the response inline.
This will also be expanded in the coming weeks to provide far more in-depth information about your calls, allowing you to ‘drill down’ to very detailed call records on an individual call basis.
As always you can find these, and the rest of our API functions, in our API Documentation