Full Teams Client API including Call Control
Microsoft Teams should have completed Client APIs so that third party apps can be created to fill specific needs.
This API should allow call control of the Microsoft Teams application. Necessary call control features include:
• dial/call
• call answer
• hang-up
• hold/off hold
• call transfer (all types: blind, consult, safe)
• add participant
• mute/unmute
• park/unpark
• call as a delegate
Some general features include:
• search contacts
• get contact presence
• get contact list folders/contacts
• setup contact list folders/contacts
• get/set my presence
• get/set my note
• get/set my delegates
• get/set my Calling Groups
• Get/set my call forwarding
• get/set audio device
• get/set voicemail settings
Messaging
• get/send chat messages
• get/send voice/audio message
The above lists are not comprehensive but are to give an idea of the necessary features.
Also
The Teams Client API should be able to be used inside the Microsoft Teams client canvas or from a standalone application. Ideally, the application developer could decide if they want to access the above functionality by controlling the Microsoft Teams application, with the Teams app running alongside, or as a standalone application, without the Microsoft Teams application running.
We see this as part of achieving Skype for Business parity so ISV's can write applications like Attendant Consoles so organizations can move to Microsoft Teams.
Matt Landis
shared this idea
The team is reviewing possibilities in this space but does not yet have a date on this. We will update when there is news to share.
177 comments
-
Christian Zentgraf
commented
an official update on this topic would be very much appreciated!
-
Anonymous
commented
is there any progress Microsoft? This is currently a show stopper....... the barrier to entry for lots of opportunities!
-
Andre Hagmann
commented
is there any progress from Microsoft for the Call Control API, as this is a key deployment blocker for customer, migrating from Cisco with Customer Date Integration.
-
Anonymous
commented
We also use Attendant Console from Landis and they can't integrate the attendant console with Teams client until you release the client API.
-
Timothy Meredith commented
Similar to this request, please vote on this one if you use Teams/Dynamics, at least they could make a native teams/dynamics call integration if they're going to drag their feet on a workable API: https://experience.dynamics.com/ideas/idea/?ideaid=9e39442c-5a33-eb11-8441-0003ff68e4a1
-
Rory Donnelly
commented
Please can we have an update on this??? We use Attendant Console from Landis and they can't integrate the attendant console with Teams client until you release the client API.
This is critical!
-
Thomas Walter
commented
Is there any update on this?
We are using Teams and SfB in parallel and I would like to sync the status of both tools by my own scripts, but this is not possible without an interface to Teams.
The MS Graph API is no option here, because I would need an admin consent to even read or write my own status and I don't think that this will be possible.
As the Teams client is talking to Outlook for example, there is obviously an interface but there is no documentation and it seams that no one at MS wants to share information about this. -
Anonymous
commented
any update MS?
-
Anonymous
commented
any update on this ?
-
Anonymous
commented
WOW, how long!!!
-
Anonymous
commented
Is there any update on this? It's odd that something that is so important to so many enterprise customers is being strung along without resolution.
-
Alex Brunner
commented
Please bring this API asap. We are in need of Landis Attendant Pro which currently only supports Skype for Business but doesn't support Teams.
-
Andrew
commented
Hi Alex - can we get ab update on this ? its critical to our business - the lack of progress is harming the adoption of Team for voice calling
-
Paul Healy
commented
Can we please, please have an update on this? No news for about 4 months.. Given SFB Online is EOL 31 July 2021, I'd expect Teams should reach parity with SFB around this API functionality well before then. It beggars belief that this feature seems not to be a high priority when it is so critical to making Teams a viable enterprise calling solution. Thanks
-
Seems like virtually every call request feature isnt important to microsoft, almost all of them in uservoice are "on the backlog" or "Exploring possibilities" :( :( :(
-
Allan
commented
This is urgently needed in order to make a usable client.
-
Francis Leclerc
commented
Any progress on an API for call management on Teams and Teams Room? Would be very usefull to be able to monitor the status of the peripherals used by the Teams Room devices from third party applications.
-
tle
commented
You can't be serious. If Exchange doesn't already use shared contacts, we need at least a API to enable teams to enterprise call system...
wtf is wrong with ms?
-
Hugh Ogilvy
commented
Yes, this is absolutely a requirement in my world. Look at the direct competition - Zoom - Zoom has an API (called Zoom Rooms CLI), as does Cisco, and Polycom - all of which we use from application integration, and also Crestron and AMX automation / control systems all the time. However Teams does not have this! Seems like a major down side, and is why on a professional integration level we pretty much have to avoid Teams currently.
It seems, at least to me, that without this, it is not a solid competitor in the business Video Conferencing world.
-
Markus Bollhalder
commented
At this time we are using Skype for Business and some users use a lync attandent from landis technology. We are working out to migrate to Microsoft Teams. One Point on our List is to use the Lync Attendantent in the future. But for this it's important, that the API is provided for this Lync Attendant. That will be really helpful to manage our 100 users. Please release the API immediately we can assure a complete Teams migration. Without this API we have to stop our migration.