Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Pages Menu
TwitterRssFacebook

Posted by on Apr 20, 2017 in Microsoft Teams

Microsoft “actively working” on a Teams API

Microsoft “actively working” on a Teams API

Microsoft are “actively working” on a developer API for Microsoft Teams. In a comment on UserVoice the idea was changing to “Working on it” with a note by “Suphatra”, who is the admin and main contact point at Microsoft with the Teams UserVoice community:

There’s no word on timelines, but the comment is already over a month old. There are 42 ideas currently in ‘Working on it’ status. Also, taking into account my blog post yesterday (Microsoft Teams External/Guest Access coming “in June”) this feature could very well be the “richer developer platform” which is scheduled for a June release.

An API makes a lot of sense and from what I’ve seen of the Teams client so far (see my post Under the Hood of the Microsoft Teams Desktop Application) an API already exists and is being used by the UI to get stuff done. There will be a bunch of work to be done in sanitising the API, making it suitable for public consumption, documentation etc. etc. but the building blocks mostly look like they are there. I think that if you really wanted to you could build an application today which called the API itself, though it would be a lot more work than if Microsoft supported an official API.

I’m excited to see this coming, it’ll only help with the appeal and usage of Teams and becomes an important part of the comparison between it and it’s rivals (such as Slack) in what is becoming a fiercely competitive space.

 

Written by Tom Morgan

Tom is a Microsoft Teams Platform developer and Microsoft MVP who has been blogging for over a decade. Find out more.
Buy the book: Building and Developing Apps & Bots for Microsoft Teams. Now available to purchase online with free updates.

0 Comments

Trackbacks/Pingbacks

  1. How to Manage Microsoft Teams & Send Messages using the Teams API in Microsoft Graph | The thoughtstuff Blog - […] is currently an open UserVoice thread of the issue of a Developer API for Teams, so it looks like…

Post a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Share to Microsoft Teams