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.
Joeri B commented
A Real shame there is still no API. This has/is the main reason why we are not migrating from a regular PBX to Teams Telephony.
We need to be able to integrate with our Dynamics CRM, to detect an incoming call and show the details of the contact as a popup on screen, to assist our helpdesk team.
there is currently no shortcut for opening a meeting chat! Please it's one of the most regular activities that one manually opens.
Please, will be great to make use of using a streaming deck from elgato! Rather than relying on short cuts while keeping the MS Teams window active.
Jason Soby commented
Any update would be helpful here. Is it even planned right now?
Craig Stevens commented
This is the minimum basic functionality that we are waiting for. This is holding up our rollout of teams.
Carsten Hojgaard commented
Same as Brice. PLEASE comment on an ETA on this. Or just give a comment anyway, to let us know you are reviewing this.
When this will finally released???
Same as lot of people here. We are using Landis Technologies Attendant Console which rely on old SfB SDK to manage calls. I know they would like to update their software but without relevant Teams's API it is impossible.
Biggest issue is that we do not have any ETA and the Skype EOL is coming. Oh no it's already there! Cherry on the cake if these API going out one day, the software development will be rushed and as customers, we are probably going to face many problems (and also deploy very quickly without time to properly test the solutions and train the users)
@Alex, Can you at least provide some update ?
Do you have an update of this topic?
There are third party solutions to complement the Teams Cloud PBX shortcomings. Products like attendant consoles are a critical part of a successful PBX operation. These are dependent on the release of the Full Teams Client API including Call Control. These are not scheduled to be released yet but there is already a forced deadline to shutdown Skype for Business. This does not make much sense as the currently deployed attendant consoles will be left inoperable and businesses that depend on these solutions (like us) will be left without a tool to manage calls coming in. A coordinated release of ALL the tools to manage the cloud PBX solution including third party support before deadlines are imposed is mandatory in our opinion. This is an issue that has been in discussion for more than a year and there is not a formal release date yet. Can you provide one?
LIke many customers in Europe. wait this feature urgently !!!!! thx !
UC Technical Manager
Raffaele Colavecchi commented
Barry Porch commented
This is minimum, basic functionality. What is going on?
Adam Gilman commented
I've been following this thread for a while. I'm also disappointed there isn't any movement on this from MS. We are considering dropping our current PBX system and going to Teams w/ SIP trunks, but if this API update isn't added then we won't be switching. We are not going from from a PBX where we already have API access to one that doesn't have this ability.
Any new update
Timothy Meredith commented
It's been almost a year since MS last deflected this.. not promising
Øyvind Nilsen commented
Very interested in this, are there any news?