This is on our "someday" list, but not something actively in development.
The last time we were working on an API, we had virtually 0 interest. Many resellers said they wanted it, but then when it was available for testing, virtually none actually used it or provided any feedback so development on it was dropped due to lack of interest.
We have a list of proposed API functions recent sent to us by uf_shane that we're going to review soon to see how easy they would be to implement in a basic API, but that's something our developers will have to review and then we look at the cost/time related to dev and compare it with demand to see if we can fit it in.
If you'd like to put together a proposed list of functionality you'd like to see, feel free to send it over to me at tim @ voipo.com and I can discuss with our developers to see how hard it would be to implement and get a feel for the time needed if we were to do it.
We have to balance keeping service reliable and stable (behind the scenes projects) with new development and we have a huge dev backlog so we have to really look at each potential dev item carefully to determine what we can/can't do when looking at the big picture. We just don't want to invest resources into developing something that doesn't get used and taking away those resources from projects related to things that would get used.
Bookmarks