Alpha Feature: API Access

[mrkarron]

The geek factor is impressive. But I wouldn't be surprised if I am in the minority by saying, I would have preferred to see a more flexible, updated 'Forwarding' feature rather than another way to activate a Basic Forwarding feature with limited options. Ma Bell Forwarding from the seventies had greater flexibility.

As I stated on other threads, I feel a basic no answer or a busy call forward are options that would be very useful.

[Xponder1]

I thought I would clean this thread up and post the current suggestions all in one post.

1.

I feel a basic no answer or a busy call forward are options that would be very useful.

2.

I could see several uses for Voicemail:

• Enable/disable
• Return number of unread messages
• Return message details (Message ID, Caller Name & Number, Date/Time, Duration, etc.)
• File/delete messages using Message ID above

I would think the first two are pretty basic and the last two a little more complicated. I could see this tying into something cool like a Firefox voice mail plug in or something along those lines...

and

I second this for the VM interaction. Would be great to integrate with my home web page so I can get a quick idea of what my messages are without having to login to the vPanel.

and

Could add a option to clear message waiting on voicemail.

and

Now if we could have an api call that would delete all messages from our voicemail (since we *usually* listen to them via email).
Perhaps also a "last X callers" where X is a number you could send to the api. The data returned should be customer caller ID aware.

and

I would also add my support for Voicemail commands via API. Is there any way Voicemail queries for sub-voicemail boxes (e.g. for virtual numbers) could be supported?

I'd be interested in seeing a mechanism for manipulating the Contacts database for a user account, as well. Add/delete/display/rename? Import and export would be cool, too, but that could probably be done via the add and display commands on the client side...

3.

How about a option for simul ring.

4.

What about a new option for DND called "status" which would report if it was enabled, and if so, which type of DND is enabled. This would be handy for a web page I want to put together for my wife that'll tell her what the status is and give her buttons to enable/disable from her iPhone so she can do so while dealing with our little one.

This feature was implemented and I think it should be added to the first page

http://api.voipo.com/?username=USER&password=PASS&action=dnd&arguments[]=status

There you go, enjoy!

5.

How about a message that says "Success!" on the API pages if successful for confirmation.

and

And I agree with Xponder, a confirmation message for each service if it was successful would be nice.

6.

It would be great if all features were available with each access method.

7.

New suggestion. Currently if you enter a invalid command it says "Your not authorized to do this". How about making it say "Invalid command!".

[fisamo]

I need to add a question: I noticed that the API is also available for Express accounts. Was that done in error, or are some commands available to Express users? (If so, which ones?) Once you integrate voicemail, it makes good sense to include the API. OTOH, with Express accounts, since one API password could control multiple different numbers (each of which have different routing instructions), that difference would need to be considered.