| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| platform | API References | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/apps-in-teams-meetings/API-references.md | Title: Meeting apps API references -description: Learn to identify the meeting apps API references with examples and Code samples, Teams apps meetings user role api user context notification signal query. +description: In this article, learn meeting apps API references that are available for Teams client and Bot Framework SDK's with examples, code samples, and response codes. ms.localizationpriority: medium The following code provides an example of meeting end event payload: The `getIncomingClientAudioState` API allows an app to get the incoming audio speaker setting for the meeting user. The API is available through the Teams client SDK. > [!NOTE]-> The `getIncomingClientAudioState` API for mobile is currently available only in [Public Developer Preview](../resources/dev-preview/developer-preview-intro.md). +> +> * The `getIncomingClientAudioState` API for mobile is currently available in [Public Developer Preview](../resources/dev-preview/developer-preview-intro.md). +> * Resource specific consent is available for manifest version 1.12 and later versions, hence this API doesn't work for manifest version 1.11 and earlier versions. ### Query parameter The following table provides the response codes: The `toggleIncomingClientAudio` API allows an app to toggle the incoming audio speaker setting for the meeting user from mute to unmute or vice-versa. The API is available through the Teams client SDK. > [!NOTE]-> The `toggleIncomingClientAudio` API for mobile is currently available only in [Public Developer Preview](../resources/dev-preview/developer-preview-intro.md). +> +> * The `toggleIncomingClientAudio` API for mobile is currently available in [Public Developer Preview](../resources/dev-preview/developer-preview-intro.md). +> * Resource specific consent is available for manifest version 1.12 and later versions, hence this API doesn't work for manifest version 1.11 and earlier versions. ### Query parameter |
| platform | Deep Links | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/build-and-test/deep-links.md | Title: Create deep links -description: Learn how to create deep links and how to use and navigate them in your Microsoft Teams apps with tabs. +description: In this article, you'll learn how to create deep links and navigate them in your Microsoft Teams apps with tabs. ms.localizationpriority: high groupId: "ae063b79-5315-4ddb-ba70-27328ba6c31e" ### Deep linking to an app Create a deep link for the app after the app is listed in the Teams store. To create a link to launch Teams, append the app ID to the following URL: `https://teams.microsoft.com/l/app/<your-app-id>`. A dialog box appears to install the app.- ++> [!NOTE] +> Currently, the deep linking to an app isn't supported on mobile platform. + ### Deep linking for SharePoint Framework tabs The following deep link format can be used in a bot, connector or message extension card: |
| platform | In App Purchase Flow | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/deploy-and-publish/appsource/prepare/in-app-purchase-flow.md | ms.localizationpriority: high # In-app purchases -Microsoft Teams provide APIs that you can use to implement the in-app purchases to upgrade from free to paid Teams apps. In-app purchase allows you to convert users from free to paid plans directly from within your app. +Microsoft Teams provides APIs that you can use to implement the in-app purchases to upgrade from free to paid Teams apps. In-app purchase allows you to convert users from free to paid plans directly from within your app. ## Implement in-app purchases To enable in-app purchase experience, update your Teams app `manifest.json` file To trigger in-app purchase for the app, invoke the `openPurchaseExperience` API from your web app. -Following is an example of calling the API from the app: +Following code snippet is an example of calling the API from the Teams app built using Teams JavaScript client SDK: ++# [TeamsJS v1](#tab/jsonV11) ```json-<body> <div> -<div class="sectionTitle">openPurchaseExperience</div> -<button onclick="openPurchaseExperience()">openPurchaseExperience</button> -</div> -</body> -<script> - function openPurchaseExperience() { +<div class="sectionTitle">openPurchaseExperience</div> +<button onclick="openPurchaseExperience()">openPurchaseExperience</button> +</div> +</body> +<script> + function openPurchaseExperience() microsoftTeams.initialize(); let callbackcalled = false; microsoftTeams.monetization.openPurchaseExperience((e) => {- console.log("callback is being called"); - callbackcalled = true; - if (!!e && typeof e !== "string") { - e = JSON.stringify(e); - alert(e); - } - return; - }); + console.log("callback is being called"); + console.log(e); + if (!!e && typeof e !== "string") { + alert(JSON.stringify(e)); + } + return; + }); console.log("after callback: ",callbackcalled);- } -</script> + } +</script> +``` ++# [TeamsJS V2](#tab/jsonV2) ++```json +<div> +<div class="sectionTitle">openPurchaseExperience</div> +<button onclick="openPurchaseExperience()">openPurchaseExperience</button> +</div> +</body> +<script> + function openPurchaseExperience() { + app.initialize(); + var planInfo = { + planId: "<Plan id>", // Plan Id of the published SAAS Offer + term: "<Plan Term>" // Term of the plan. + } + monetization.openPurchaseExperience(planInfo); + } +</script> ``` ++ ## End-user in-app purchasing experience The following example shows the users to purchase subscription plans for a fictional Teams app called *Contoso Tasks for Teams*: |
| platform | Deploy Teams App | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/toolkit/deploy-teams-app.md | After your project is successfully deployed to Azure, there are different ways t :::image type="content" source="../assets/images/deploy-teams-app-cloud-vs/vs-deploy-ZipApp-package.png" alt-text="Generate teams app package"::: -**To preview your app in Teams client** + **To preview your app in Teams client** -1. Select **Project** -1. Select **Teams Toolkit**. -1. Select **Preview in Teams**. +3. Select **Project**. +4. Select **Teams Toolkit**. +5. Select **Preview in Teams**. :::image type="content" source="../assets/images/deploy-teams-app-cloud-vs/vs-deploy-preview-teams1.png" alt-text="Preview Teams app in teams client"::: |
| platform | Teams Toolkit Overview Visual Studio | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/toolkit/teams-toolkit-overview-visual-studio.md | Last updated 05/24/2022 Teams Toolkit for Visual Studio helps you to create, debug and deploy Microsoft Teams apps. Teams Toolkit for Visual Studio is GA in Visual Studio 2022 version 17.3. App development with Teams Toolkit has the advantages of: -* Integrated identity. -* Access to cloud storage. -* Data from Microsoft Graph. -* Azure and Microsoft 365 services with zero-configuration approach. +* Integrated identity +* Access to cloud storage +* Data from Microsoft Graph +* Azure and Microsoft 365 services with zero-configuration approach For Teams app development, you can also use [CLI tool](https://github.com/OfficeDev/TeamsFx/blob/dev/docs/cli/user-manual.md), similar to Teams Toolkit for Microsoft Visual Studio code that includes Toolkit `teamsfx`. |