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:
• call answer
• hold/off hold
• call transfer (all types: blind, consult, safe)
• add participant
• 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
• 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.
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.
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.
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.
any update MS?
any update on this ?
WOW, how long!!!
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.
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
Timothy Meredith commented
Seems like virtually every call request feature isnt important to microsoft, almost all of them in uservoice are "on the backlog" or "Exploring possibilities" :( :( :(
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.
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.
Paul Healy commented
We're a global company and we've already moved one of our regions to Teams Calling, but without this API we're not able to move our entire organisation over. We use Dynamics 365 as our CRM and need to be able to get the Caller ID and do things like popping a contact window and tracking call activity which worked fine with SfB. Obviously having a reception console is also a major requirement. Our whole company uses M365, Teams and Dynamics and it's extremely disappointing that this basic functionality is not yet available. We want to be 100% Microsoft Cloud but until this is released most of our business (several thousand users) will have to remain on RingCentral, Mitel and other 3rd-party platforms for Voice, which is a real shame because apart from this the Teams solution ticks all our boxes, especially in the current remote working/Covid environment. Can you please prioritise this and release timeframes for availability of an API? I guarantee MS is currently missing out on a lot of revenue because of this.
Would like to go the Teams route but have to go to Nextiva because there is no API for third parties to make a Salesforce screen pop when a caller calls. Landis Technology has this in there call center but it has other features that drive the price beyond what we are looking for.
Well i tried to put it off, going to ringcentral, they have a great and well thought out API, shame microsoft that this wasn't considered sooner
A solution already exists. Run one system for attendant and reception and MS Teams for internal communication.
Wim Allegaert commented
We had to block our migration to Teams-Only just because of this. Our reception staff is using Landis Attendant PRO. We can't take this tool away from them.
Don't say things like 'we are reviewing possibilities'. Say: we will fix this right away.
Please give an update on this, this should have already been developed by now, not under review.