{"id":3422,"date":"2019-09-13T11:46:10","date_gmt":"2019-09-13T18:46:10","guid":{"rendered":"https:\/\/developer.microsoft.com\/en-us\/office\/blogs\/?p=3422"},"modified":"2019-09-13T11:46:10","modified_gmt":"2019-09-13T18:46:10","slug":"breaking-changes-calls-and-online-meetings-api-updates-in-microsoft-graph-beta-2","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/breaking-changes-calls-and-online-meetings-api-updates-in-microsoft-graph-beta-2\/","title":{"rendered":"Breaking changes: Calls and online meetings API updates in Microsoft Graph beta"},"content":{"rendered":"<p>We\u2019re announcing several changes to the calls and online meetings APIs in Microsoft Graph beta, including a few breaking changes. Changes might affect existing applications that use the\u00a0<code>\/beta<\/code>\u00a0calls and online meetings APIs. We expect the breaking changes to be fully deployed by the middle of September 2019.<\/p>\n<h2>API updates: adding \/communications support for calls and online meetings<\/h2>\n<p>We were supporting <code>\/app\/calls &amp; \/app\/onlinemeetings<\/code> in beta. To make the API naming more clear and specific, we are going to add new APIs: <code>\/communications\/calls<\/code> &amp; <code>\/communications\/onlinemeetings<\/code>. The previous APIs, <code>\/app\/calls<\/code> and <code>\/app\/onlinemeetings<\/code> are still supported in beta for backward compatibility.<\/p>\n<p>&nbsp;<\/p>\n<h2>API updates: adding \/user\/onlinemeetings<\/h2>\n<p>We currently support creating online meetings with app token only. Now, we will support creating online meetings with both user token and app token.<\/p>\n<h2 id=\"user-content-changes-to-entity-types\">Changes to entity types<\/h2>\n<p>We&#8217;re removing two unused properties from the <strong>commsOperation<\/strong> entity type: <strong>createdDateTime<\/strong> and <strong>lastActionDateTime<\/strong>.<\/p>\n<p id=\"user-content-adding-new-property-isbroadcast\">We&#8217;re adding a new property <strong>isBroadcast<\/strong> to the <strong>onlineMeeting<\/strong> entity type, and removing the <strong>meetingType<\/strong> property.<\/p>\n<table>\n<thead>\n<tr>\n<th>Property<\/th>\n<th>Type<\/th>\n<th>Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>isBroadcast<\/code><\/td>\n<td><code>Boolean<\/code><\/td>\n<td>Is the meeting a broadcast meeting or not.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This propertmeetingType is an enum we used to support. Because there are only two types of meetings &#8211; broadcast and non-broadcast &#8211; you can use the <strong>isBroadcast<\/strong> flag instead of <strong>meetingType<\/strong>.<\/p>\n<h2 id=\"user-content-changes-to-complex-type\">Changes to complex type<\/h2>\n<p>The <strong>resource<\/strong> property of the <strong>commsNotification<\/strong> complex type will be renamed to <strong>resourceUrl<\/strong>.<\/p>\n<p>In order to support both the\u00a0<code>\/app<\/code> and <code>\/communications<\/code>paths, we need to return two resource paths, one with <code>\/app<\/code> and one with <code>\/communications<\/code>. In the future, when our APIs are in the Microsoft Graph v1.0 endpoint, we will support only <code>\/communications<\/code>. At the moment, the path for the\u00a0<strong>resource<\/strong> property will be <code>\/app<\/code>, and the path for the new\u00a0<strong>resourceUrl<\/strong>\u00a0property will be <code>\/commmunications<\/code>.<\/p>\n<p>In the resultInfo complex type, we&#8217;re renaming <strong>subCode<\/strong> to <strong>subcode<\/strong>, and changing the <strong>code<\/strong> and <strong>subcode<\/strong>\u00a0properties from type string to type int.<code class=\"xml\">\n<\/code><\/p>\n<h2 id=\"user-content-changes-to-enums\">Changes to enums<\/h2>\n<p>We&#8217;re adding a new value <code>sameEnterpriseAndFederated<\/code>to the <strong>accessLevel<\/strong> enum type.<\/p>\n<div>\n<div>\n<pre class=\"lang:xhtml decode:true\">&lt;EnumTypeName=\"accessLevel\"&gt;\n\u00a0 &lt;MemberName=\"everyone\"Value=\"0\"\/&gt;\n\u00a0 &lt;MemberName=\"invited\"Value=\"1\"\/&gt;\n\u00a0 &lt;MemberName=\"locked\"Value=\"2\"\/&gt;\n\u00a0 &lt;MemberName=\"sameEnterprise\"Value=\"3\"\/&gt;\n\u00a0 &lt;MemberName=\"sameEnterpriseAndFederated\"Value=\"4\"\/&gt;\n&lt;\/EnumType&gt;\n<\/pre>\n<\/div>\n<\/div>\n<p>We updated the <strong>routingPolicy<\/strong> enum type. For backward compatibility, we need to keep `preferSfb` with Value=4. <code>preferSfb<\/code> is not in the beta, but is in the SDK.<\/p>\n<h4 id=\"user-content-new-csdl\">New routingPolicy values<\/h4>\n<div>\n<div>\n<div>\n<pre class=\"lang:xhtml decode:true\">&lt;EnumTypeName=\"routingPolicy\"&gt;\n\u00a0 &lt;MemberName=\"none\"Value=\"0\"\/&gt;\n\u00a0 &lt;MemberName=\"noMissedCall\"Value=\"1\"\/&gt;\n\u00a0 &lt;MemberName=\"disableForwardingExceptPhone\"Value=\"2\"\/&gt;\n\u00a0 &lt;MemberName=\"disableForwarding\"Value=\"3\"\/&gt;\n\u00a0 &lt;MemberName=\"preferSkypeForBusiness\"Value=\"5\"\/&gt;\n\u00a0 &lt;MemberName=\"unknownFutureValue\"Value=\"6\"\/&gt;\n&lt;\/EnumType&gt;\n<\/pre>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>We\u2019re announcing several changes to the calls and online meetings APIs in Microsoft Graph beta, including a few breaking changes.<\/p>\n","protected":false},"author":69077,"featured_media":25159,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3],"tags":[],"class_list":["post-3422","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-graph"],"acf":[],"blog_post_summary":"<p>We\u2019re announcing several changes to the calls and online meetings APIs in Microsoft Graph beta, including a few breaking changes.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/3422","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/users\/69077"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=3422"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/3422\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/25159"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=3422"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=3422"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=3422"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}